gtpm4m0y | Messages (System Error and Offline) |
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A request to the file address compute program (FACE) to supply the address of the recoup working keypoint retrieved an error indicator.
System Action: The ECB is exited and the requested function is not formed.
User Response: Your system programmer should review the dump as well as the allocation of the recoup working keypoint board.
Program: Displayed on the console and in the dump.
Error Message: RECOUP IS ABORTING
Explanation: Recoup is aborted either internally because of an error during processing or because of a command.
System Action: Recoup is exited from the system.
User Response: Do one of the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The ID of the directory ordinal record is incorrect.
System Action: The ECB is ended.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: RECOUP ABORTING DUE TO TIME-OUT
Explanation: An item timed out during recoup phase I processing.
System Action: If recoup phase I is completed, processing is continued.
If recoup phase I is still in progress, recoup is aborted.
User Response: Your system programmer should review the dump to determine the cause of the timeout error and to correct it.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error was returned from the file address compute program (FACE) that calculated the address of the directory ordinal record.
System Action: The ECB is ended.
User Response: Your system programmer should review the dump and check the @BRCPB global for the correct ordinal number of the recoup master keypoint record.
If this is valid, review the FACE error.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a FIND error on the directory ordinal record. On an attempted retrieval of the directory ordinal record (recoup master keypoint) there was an error.
System Action: The entry control block (ECB) is ended.
User Response: Do the following:
Use an alternate retrieval method, such as issuing the ZDFIL command, to verify the retrievability of the record, the correctness of the record ID and so forth, as well as the file address returned from FACE.
Program: BJ04
Error Message: TPFCS TIMEOUT ON DATA STORE dsname
Where:
Explanation: At least one entry control block (ECB) did not end normally when the timeout threshold was reached after the last ECB for a TPF collection support (TPFCS) data store or selective persistent identifier (PID) was generated. This dump is accompanied by online message that indicate the PIDs that timed out.
System Action: Processing ends for the associated data store or selective PID and recoup processing continues.
User Response: Have your system programmer review the dump to determine the cause of the timeout error and to correct it.
See TPF Database Reference for more information about recoup functions and procedures.
Program: Displayed on the console and in the dump.
Error Message: FACE/FIND ERROR #SONSV - REST CONTINUING
Explanation: The ZRDIR START RESTORE command was entered, but an error condition was detected by a FACE-type or a FIND-type call while trying to retrieve a recoup SONRI save area (#SONSV) record.
System Action: The record is not restored, but restore processing continues with the next record ordinal.
User Response: Do the following:
See TPF Operations for more information about the ZRDIR START RESTORE command.
Program: BRTD
Error Message: FACE/FIND/FILE ERROR #SONRI - REST CONTINUING
Explanation: The ZRDIR START RESTORE command was entered, but an error condition was detected by a FACE-type, FIND-type, or a FILE-type call while trying to retrieve or file a pool rollin directory (#SONRI) record.
System Action: The record is not restored, but restore processing continues with the next record ordinal.
User Response: Do the following:
See TPF Operations for more information about the ZRECP START RESTORE command.
Program: BRTD
Error Message: #SONSV/#SONRI DO NOT MATCH
Explanation: The ZRDIR START RESTORE command was entered, but the ID or record code check (RCC) of the recoup SONRI save area (#SONSV) record did not match the ID or RCC of the pool rollin directory (#SONRI) record.
System Action: The record is not restored, but restore processing continues with the next record ordinal.
User Response: Do the following:
See TPF Operations for more information about the ZRECP START RESTORE command.
Program: BOF2
Error Message: BOF2 -- FACE ERROR
Explanation: The ZRECP DISPLAY command was entered, but an error condition was detected by a FACS-type call while trying to resolve the file address for #IBMM4 ordinal #LTDRT.
System Action: The command fails.
User Response: Do the following:
See TPF Operations for more information about the ZRECP DISPLAY command. See TPF System Macros and TPF Application Programming for more information about the FACE program and the FACE interface.
Error Message: BOF2 -- FIND ERROR
Explanation: The ZRECP DISPLAY command was entered, but an error condition was detected while trying to find the file address for #IBMM4 ordinal #LTDRT.
System Action: The command fails.
User Response: Do the following:
See TPF Operations for more information about the ZRECP DISPLAY command. See TPF System Macros and TPF Application Programming for more information about the FACE program and the FACE interface.
Program: BRYU
Error Message: None.
Explanation: During recoup processing, an error occurred while processing in-core directories for one of the following reasons:
System Action: The ECB ends.
User Response: Do the following:
Program: BRYU
Error Message: None.
Explanation: During recoup processing, an error occurred while processing in-core directories for one of the following reasons:
System Action: Recoup processing continues, but in-core directory capture is incomplete. There may be some erroneously available addresses reported in recoup phase 3, but that should not cause any database harm.
User Response: Do the following:
Program: BPDH
Error Message: PSEUDO DIRECTORY FACE ERROR - RUN ABORTED
Explanation: During recoup processing, an error condition was detected by a FACE-type call while trying to retrieve a recoup merged directory (#SONRPM) record.
System Action: Recoup directory rollin ends without completing.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures. See TPF System Macros and TPF Application Programming for more information about the FACE program and the FACE interface.
Program: BPDH
Error Message: PSEUDO DIRECTORY FIND ERROR - RUN ABORTED
Explanation: A FIND-type error occurred while trying to retrieve the recoup merged directory (#SONRPM) record.
System Action: Recoup directory rollin ends without completing.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures.
Program: BPDH
Error Message: PSEUDO DIRECTORY FILE ERROR - RUN ABORTED
Explanation: During recoup processing, an error condition was detected while trying to file a recoup merged directory (#SONRPM) record.
System Action: Recoup directory rollin ends without completing.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures. See TPF System Macros and TPF Application Programming for more information about the FACE program and the FACE interface.
Program: BPDH
Error Message: DIRECTORY ORDINAL OUT OF RANGE - RUN ABORTED
Explanation: During recoup processing, the calculated directory ordinal number is out of the range for the pool type.
System Action: Recoup directory rollin ends without completing.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures.
Program: BRTD
Error Message: FIND ERROR #KY9CPY - RESTORE ABORTED
Explanation: The ZRDIR START RESTORE command was entered, but an error occurred while attempting to find the saved copy of keypoint 9 in the #IBMM4 fixed file record type at #KP9CPY.
System Action: The ECB exits. Keypoint 9, the pool section keypoint tables (CY2KT), and the pool directories were not restored.
User Response: Do the following:
Error Message: FIND ERROR KEYPOINT 9 - RESTORE ABORTED
Explanation: The ZRDIR START RESTORE command was entered, but an error occurred while attempting to find keypoint 9.
System Action: The ECB exits. Keypoint 9, the pool section keypoint tables (CY2KT), and the pool directories were not restored.
User Response: Do the following:
Error Message: FILE ERROR KEYPOINT 9 - RESTORE ABORTED
Explanation: The ZRDIR START RESTORE command was entered, but an error occurred while attempting to file the saved copy of keypoint 9 (#KP9CPY) to the working copy of keypoint 9.
System Action: The ECB exits. The pool directories have already been restored with some or all of the pool section keypoint tables (CY2KT), but keypoint 9 is not restored.
User Response: Do the following:
See TPF Operations for more information about the ZRDIR START RESTORE command.
Program: BRTD
Error Message: FIND ERROR #CY2CPY - RESTORE ABORTED
Explanation: The ZRDIR START RESTORE command was entered, but an error occurred while attempting to find the saved copy of a pool section keypoint table (CY2KT) from the #CY2CPY fixed file record type.
System Action: The ECB exits. Some pool section keypoint tables (CY2KT) and pool directories may have been restored, but keypoint 9 has not been restored.
User Response: Do the following:
Error Message: FIND ERROR CY2KT - RESTORE ABORTED
Explanation: The ZRDIR START RESTORE command was entered, but an error occurred while attempting to find the working copy of the pool section keypoint tables (CY2KT).
System Action: The ECB exits. The pool section keypoint tables (CY2KT) and some pool directories may have been restored, but keypoint 9 has not been restored.
User Response: Do the following:
Error Message: FILE ERROR CY2KT - RESTORE ABORTED
Explanation: The ZRDIR START RESTORE command was entered, but an error occurred while attempting to file the saved copy of a pool section keypoint table (CY2KT) to the working copy of the CY2KT.
System Action: The ECB exits. The pool directories have been restored with some or all of the pool section keypoint tables (CY2KT), but keypoint 9 is not restored.
User Response: Do the following:
See TPF Operations for more information about the ZRDIR START RESTORE command.
Program: Displayed on the console and in the dump.
Error Message: RECP -- INVALID RCC FOR SON DIRECTORY RECORD
Explanation: The BRYG segment was given an ID that is not valid for the specific pool record or the ordinal number used to calculate the directory record address was exceeded the range for the given record ID.
System Action: Processing is continued.
User Response: Your system programmer should review the dump to determine the cause of the error and to correct it.
See the record ID in the directory rerun table of the BRYG segment.
Program: Displayed on the console and in the dump.
Error Message: RECP BAD RPE TAPE
Explanation: The following errors may have occurred:
System Action: A message is sent to the operator to resume or to abort.
User Response: Do the following:
Error Message: RECP PSEUDO DIRECTORY RECORD
Explanation: During recoup processing, an error condition was detected by a FACS-type call or FIND-type macro while trying to retrieve a recoup merged directory (#SONRPM) record.
System Action: Recoup directory rollin processing ends without completing.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures. See TPF System Macros and TPF Application Programming for more information about the FACE program and the FACE interface.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: Recoup was unable to calculate a general file address within the Phase 1 capture area. In addition, the ordinal number or record ID was not valid.
System Action: A message is sent to the operator to resume or to abort.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: Recoup was unable to calculate a general file address within the Phase 3 capture area. In addition, the ordinal number or record ID was not valid.
System Action: A message is sent to the operator to resume or to abort.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: Recoup was unable to calculate a general file address within the Phase 2 result area. In addition, the ordinal number or record ID was not valid.
System Action: A message is sent to the operator to resume or to abort.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The program is unable to read either Phase 1 or Phase captured directory.
Any of the following errors may have occurred:
System Action: A message is sent to the operator to resume or to abort.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error was returned from the FILNC macro because the system is unable to write to the Phase 2 result area on the general file.
System Action: A message is sent to the operator to resume or to abort.
User Response: Your system programmer should review the dump to determine the cause of the error, correct it, and then resume recoup. Otherwise, recoup should be aborted.
It may also be helpful to obtain copies of the Phase 1 and Phase 3 directories for comparison with the RPE record.
Program: BCP6
Error Message: RECP BAD DIRECTORY RECORD - GFS IS NEGATIVE
Explanation: During recoup processing, a comparison of the first and second directory captures indicated negative get file storage (GFS) activity, which cannot occur.
System Action: Recoup processing ends.
User Response: Determine the reason for the directory mismatch.
Program: Displayed on the console and in the dump.
Error Message: RECP - RPE TIME STAMP NOT CORRECT
Explanation: The time stamp on the RPE tape is not matched with the current recoup run.
System Action: A message is sent to the operator to resume or to abort.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: RECP - BAD DIRECTORY RECORD
Explanation: The captured directory and the RPE directory for an ordinal do not match in one of the following areas:
System Action: A message is sent to the operator to resume or to abort.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: RECP INCORRECT NUMBER OF DIRECTORY RECORDS ON RPE.
Explanation: The number of directory records read from the RPE tape does not match the number of directories according to the counts from the online file keypoint records.
System Action: Recoup is aborted internally.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: RECOUP TIME-OUT ID-record
Where:
Explanation: The record identified in the message ran longer than the time estimated in the group macro.
System Action: One of the following occurs:
User Response: If this record type times out a second time, the group is marked as complete and processing begins for the next record type. Phase 2 counts are suspect and should be treated as incomplete.
Your system programmer should review the dump to determine whether the problem is in excessively long chains or too low a time setting in the group macro.
Program: Displayed on the console and in the dump.
Error Message: SEQUENCE ERRORS ON DIRECTORY ORDINALS: ordnum
Where:
Explanation: While sequence checking the directory ordinals during directory capture, the ordinals were found to be out of sequence.
System Action: Processing is deferred while waiting for a retry or an abort input message.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: DIRECTORY AVAILABLE IN ERROR: ordnum
Where:
Explanation: The BRYE program (file pool directory roll-in) encountered a SONRI directory that is not found in an active or standby set and therefore should not be owned by a processor. However, this directory is indicated as being owned by a processor.
System Action: A system error is issued, the directory is rolled in, and processing is continued.
User Response: Correlate the processor ID of the directory with keypoint 9 (CTK9) to determine the cause of the error. Use console logs to recreate the directory history.
See TPF Database Reference for more information about recoup functions and procedures.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: During recoup processing, there was an error processing in-core directories for one of the following reasons:
System Action: Recoup processing fails.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error retrieving the file address of the global area record from the file address compute program (FACE).
System Action: This ECB is ended.
User Response: Your system programmer should review the dump to determine the cause of the error and to correct it. In addition, the system programmer should verify that the error was not created by a faulty-built descriptor record group.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a FIND/FILE error on the application global area record.
System Action: This ECB is ended.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was an error in the application global area item on return from the file address compute program (FACE).
System Action: This particular application global area item is skipped but processing is continued.
User Response: Your system programmer should review the dump to determine whether the application global area item that is not being processed will affect the Phase 2 and Phase 3 roll in. If so, then recoup should be aborted and run again once the error is corrected.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An internal error occurred during TPF collection support recoup because a non-valid branch vector was passed to the called program.
System Action: TPF collection support recoup is bypassed or ends without completing.
User Response: See your IBM service representative.
Program: BRYM - ERROR RETRIEVING #SONROLL DIR.
Error Message: None
Explanation: During recoup directory capture processing, an error occurred while retrieving the pseudo directories.
System Action: The TPF system sends a SNAPC dump and recoup processing pauses.
User Response: Enter ZRECP ABORT or ZRECP RESUME.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The program was entered indicating an embedded pool address exists at a fixed location within the data record. However, parameters in the appropriate INDEX macro of the descriptor record indicate a displacement to the embedded file address of zero bytes or a record ID of X'0000' -- both conditions are not valid.
System Action: Processing is continued.
User Response: Your system programmer should review the dump to correct the index.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: A FACE/FIND error occurred on the recoup master keypoint. The program was unable to retrieve the master recoup keypoint.
System Action: This ECB is ended.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There is insufficient information available at the INDEX macro of the descriptor record regarding the number of items within the record that requires processing.
System Action: Processing is continued.
User Response: Your system programmer should review the dump to correct the index.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: The length of the ordinal number in the INDEX macro is not valid.
System Action: Processing is continued.
User Response: Your system programmer should review the dump to correct the index.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a FIND error on a fixed-file record pointed to by an ordinal number within an item in the record structure.
System Action: A system error dump is issued and processing is continued with the next item.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: There was a file address compute program (FACE) error while converting an ordinal number to a file address.
System Action: Processing is continued with the next item.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred because on restart the retrieved descriptor did not contain a matching group displacement to that which was saved in the 06RCPK (working keypoint).
System Action: The chain-chase of this descriptor is started again.
User Response: Allow to run from the beginning of the chain-chase.
Your system programmer should review the dump to determine which descriptor ordinal and group displacement were being restarted and why a match could not be found.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred because the system was unable to retrieve the message container record.
System Action: This ECB is exited.
User Response: The operator should IPL the TPF system again and start recoup again, as required.
Your system programmer should review the dump to determine why a message container record cannot be retrieved.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred because the system was unable to retrieve keypoint I.
System Action: The internal recoup is aborted.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred because the system was unable to retrieve keypoint 009.
System Action: This ECB is ended.
User Response: Do the following:
Program: BRV0
Error Message: ERROR DURING PSEUDO DIRECTORY INITIALIZATION
Explanation: During recoup processing, an error occurred while initializing the recoup pseudo directory records.
System Action: The ECB exits.
User Response: Do the following:
Program: BCC2
Error Message: POSSIBLE DESCRIPTOR OR DATA RECORD CORRUPTION
Explanation: The ZRECP RECALL command was entered, but an error occurred while trying to find a record during chain chase processing.
System Action: Recoup processing fails for this record, but continues chain chasing the next record.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: Recoup processing failed because of errors that are described in accompanying online messages.
System Action: Recoup processing fails.
User Response: Do the following:
Program: BOFF
Error Message: EVENT TIMEOUT DURING RECOUP FLUSH OF PSEUDO DIRS
Explanation: Recoup was unable to flush recoup pseudo directory records from virtual file access (VFA) within the allowed time and the records remain in VFA.
System Action: Recoup processing continues.
User Response: Do the following:
Program: BCC5
Error Message: None.
Explanation: Chain chase processing of a TPFDF data structure from a TPF recoup descriptor could not occur because the database definition table (DBTAB) being chain chased could be not located within the DBTAB.
System Action: Recoup processing continues.
User Response: Do the following:
See TPF Operations for more information about the ZRECP ADD and ZRECP REBUILD commands.
Program: BCC5
Error Message: None.
Explanation: Chain chase processing of a TPFDF data structure from within a TPF recoup descriptor could not occur because the record ID in the database definition table (DBTAB) did not match the descriptor record ID.
System Action: Recoup processing continues.
User Response: Do the following:
See TPF Operations for more information about the ZRECP ADD and ZRECP REBUILD commands.
Program: BCC5
Error Message: None.
Explanation: A descriptor was loaded to chain chase a TPFDF data structure, but TPFDF is not genned in the system.
System Action: Recoup processing continues.
User Response: Determine the cause of the descriptor error.
Program: BS0C
Error Message: FACE ERROR WHEN RETRIEVING DESCRIPTOR
Explanation: During recoup processing, a record ID could not be read.
System Action: Recoup processing continues with the next record.
User Response: Do the following:
Program: BLOD
Error Message: None.
Explanation: A ZRECP ONEL command was entered which called segment BLOD with incorrect parameters.
System Action: The ZRECP ONEL command fails.
User Response: Do the following:
Program: B1A0
Error Message: None.
Explanation: During recoup processing, an error condition was detected while trying to file the #IBMMS record (ordinal #RCPGLB) or the #IBMM4 record (ordinal #RCPSYNC).
System Action: The ECB exits.
User Response: Do the following:
Program: B1A0
Error Message: None.
Explanation: During recoup processing, a record ID check error condition was detected while trying to find the #IBMMS record (ordinal #RCPGLB) or the #IBMM4 record (ordinal #RCPSYNC).
System Action: The ECB exits.
User Response: Do the following:
Program: B1A0
Error Message: None.
Explanation: During recoup processing, a nonrecord ID check error condition was detected while trying to file the #IBMMS record (ordinal #RCPGLB) or the #IBMM4 record (ordinal #RCPSYNC).
System Action: The ECB exits.
User Response: Do the following:
Program: B1A4
Error Message: None.
Explanation: During recoup processing, an error condition was detected by a FACE-type call while trying to retrieve the #IBMMS record (ordinal #RCPGLB) or the #IBMM4 record (ordinal #RCPSYNC).
System Action: The ECB exits.
User Response: Do the following:
Program: B1A4
Error Message: None.
Explanation: During recoup processing, an error condition was detected by a FACE-type call while trying to retrieve the #IBMMS record (ordinal #RCPGLB) or the #IBMM4 record (ordinal #RCPSYNC).
System Action: The ECB exits.
User Response: Do the following:
Program: B1A4
Error Message: None.
Explanation: During recoup or pool directory update (PDU) processing, an error condition was detected while trying to find the #IBMMS record (ordinal #RCPGLB) or the #IBMM4 record (ordinal #RCPSYNC).
System Action: The ECB exits.
User Response: Do the following:
Program: BRIE
Error Message: None.
Explanation: The ZRECP RECALL command was entered, but the BGAQ segment was unable to initialize the TPFDF recoup statistics record (#SRM41A8). This could be caused by an error with a DBDEF macro statement for the SRM41A file or with the TPFDF product.
System Action: Recoup processing ends without completing.
User Response: Determine why SRM41A database initialization failed.
See TPF Operations for more information about the ZRECP RECALL command. See the TPFDF library for more information about the TPFDF product and the #SRM41A8 recoup statistics record.
Program: BKB0
Error Message: RECOUP STATS COPY ERROR
Explanation: During phase 1 of recoup, an attempt to access and update the recoup statistics record failed.
System Action: The recoup statistics record is not updated and recoup processing continues.
User Response: Do the following:
Program: BS0C
Error Message: None.
Explanation: The ZRECP STOP command was entered specifying the PROC parameter, but the record that was being chain chased on the specified processor cannot be restarted on another processor in the subsystem user (SSU) in which it was being processed.
System Action: Recoup processing continues, but the record will be chain chased in the first SSU.
User Response: Do the following:
Program: B0P5
Error Message: None.
Explanation: The ZRECP EXIT command was entered with the PROC parameter specified, but the SRM51A8 statistics record was not copied to the TPFDF recoup statistics record (#SRM41A8) because an error condition was detected by a FACE-type call or while trying to find or file one of the files.
System Action: Recoup processing continues. The ID counts for the TPFDF files will be larger because the counts from the exited processor will not be deleted.
User Response: When chain chase processing has ends, enter the ZRECP DISPLAY command specifying the PROC parameter for the exited processor to obtain all of the TPFDF file counts and subtract them from the total at the end of recoup phase 2 processing to get an accurate representation of the record ID counts.
See TPF Operations for more information about the ZRECP EXIT and ZRECP DISPLAY commands. See the TPFDF library for more information about the TPFDF product and the #SRM41A8 recoup statistics record.
Program: BRSI
Error Message: RECOUP DIR INTEGRITY CHECKS FAILED
Explanation: During recoup phase 2 processing, or after the ZRECP RESTART command was entered, the in-use counts in the recoup pseudo directories or in the recoup RCI directories (#SONCP, #SONSV, #SONROLL, or #SONUP) do not match the actual chain chase counts that are recorded internally by recoup. The cause is most likely because of the re-initialization of VFA (destroying the VFA-resident pseudo directories), a hard IPL with storage cleared, or the corruption of VFA.
PSDR0 - count of bits=0 in pseudo dirs PSDR1 - count of bits=1 in pseudo dirs SONRCI0 - count of bits turned off by recoup SONRCI1 - count of bits left on by recoup
System Action: Recoup processing ends without completing.
User Response: Determine why the recoup pseudo directories did not match. Most likely, a hard IPL or some other clearing of VFA occurred. Because recoup keeps critical information in VFA, start recoup processing again.
Program: BGAQ
Error Message: None.
Explanation: An incorrect parameter in register 6 (R6) was passed to program BGAQ.
System Action: The ECB exits.
User Response: Do the following:
Program: BKA1, BRV2
Error Message: None.
Explanation: The ZPOOL INIT command was entered, but an error condition was detected by a FACE-type call or a FIND-type or FILE-type macro.
System Action: ZPOOL INIT command processing ends without completing.
User Response: Do the following:
See TPF Operations for more information about the ZPOOL INIT command. See TPF System Macros and TPF Application Programming for more information about the FACE program and the FACE interface.
Program: BKA1
Error Message: TPFDF ERROR ON RECORD SRHH1P
Explanation: The ZRECP SEL command was entered with a record ID and file address specified, but TPF recoup processing failed while accessing the online error log (SRHH1P) file.
System Action: Selective recoup processing ends.
User Response: Do the following:
See TPF Operations for more information about the ZRECP SEL command.
Program: BKA1
Error Message: TPFDF ERROR ON RECORD SRCK1P
Explanation: The ZRECP SEL command was entered with a record ID and file address specified, but TPF recoup processing failed while accessing the SRCK1P file.
System Action: Selective recoup processing ends.
User Response: Do the following:
See TPF Operations for more information about the ZRECP SEL command.
Program: BCPY
Error Message: BCPY - FACE ERROR - DIR COPY ABORTED
Explanation: During recoup processing, an error condition was detected by a FACE-type call while trying to copy pseudo directories.
System Action: Directory copy ends without completing.
User Response: Do the following:
Program: BCPY
Error Message: BCPY - FILE ERROR - DIR COPY ABORTED
Explanation: During recoup processing, an error condition was detected while trying to file pseudo directories.
System Action: Directory copy ends without completing.
User Response: Do the following:
Program: BCPY
Error Message: BCPY - FIND ERROR - DIR COPY ABORTED
Explanation: During recoup processing, an error condition was detected while trying to find pseudo directories.
System Action: Directory copy ends without completing.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures.
Program: BCPY
Error Message: BCPY - INVALID OPTION - DIR COPY ABORTED
Explanation: Program BCPY detected a FACE error.
System Action: Directory copy ends without completing.
User Response: Do the following:
Program: BCPY
Error Message: BCPY - TIMEOUT ERROR - DIR COPY ABORTED
Explanation: Directory capture exceeded the timeout value.
System Action: Directory copy ends without completing.
User Response: Determine the reason for the timeout.
Program: BLOG
Error Message: FACE ERROR ON FC33 RECORD
Explanation: During a TPF system cycle up or cycle down, or while processing the ZRREC RESET command, a FACE-type error occurred while trying to access a FC33 record.
System Action: The TPF system fails to reset the FC33 record.
User Response: Do the following:
See TPF Database Reference for more information about the ZRREC RESET command.
Program: BLOG
Error Message: FACE OR FIND OR FILE ERROR ON 1052 STATE FC33 RECORD
Explanation: During a TPF system cycle up or cycle down, or while processing the ZRREC RESET command, a FACS-, FIND, or FILE-type error occurred while trying to access the 1052-state FC33 record.
System Action: The TPF system fails to reset the 1052-state FC33 record.
User Response: Do the following:
See TPF Database Reference for more information about the ZRREC RESET command.
Program: BRCQ
Error Message: FACS OR FIND ERROR ON 1052 STATE FC33 RECORD
Explanation: During recoup processing, a FACS- or FIND-type error occurred while trying to access an FC33 record.
System Action: Recoup processing ends without completing.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures.
Program: BRV6
Error Message: None.
Explanation: During recoup verify processing, a FIND-type error occurred while trying to access an SRM41A8 record.
System Action: The ECB exits.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures.
Program: BRV6
Error Message: None.
Explanation: During recoup verify processing, a FACE-type error occurred while trying to access an SRM41A8 record.
System Action: The ECB exits.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures.
Program: BS0C
Error Message: DESCRIPTOR NOT FOUND, POSSIBLE ERROR IN MPRECP TABLE
Explanation: During recoup processing, an internal error occurred because a record ID could not be found in the recoup scheduling control table (IRSCT).
System Action: Recoup processing continues with the next record.
User Response: See your IBM service representative.
Program: BS0C
Error Message: UNABLE TO PROCESS IDNEXT=recid, PARAMETER DISREGARDED
Where:
Explanation: Recoup processing was unable to process a record ID that was specified by the IDNEXT parameter on a GROUP macro statement.
System Action: Recoup processing fails for this record, but continues chain chasing the next record.
User Response: Do the following:
Program: BS0C
Error Message: UNABLE TO MARK ID AS COMPLETED, RECOUP IS PAUSED
Explanation: During recoup processing, an error occurred because the recoup scheduling control table (IRSCT) could not be updated to mark a record ID as completed.
System Action: Recoup processing is paused.
User Response: Do the following:
See TPF Operations for more information about the ZRECP ABORT and ZRECP LEVEL commands.
Program: BS0C
Error Message: UNABLE TO MARK DATA STORE COMPLETED, RECOUP IS PAUSED
Explanation: During recoup processing, an error occurred because the recoup scheduling control table (IRSCT) could not be updated to mark a TPF collection support (TPFCS) data store as completed.
System Action: Recoup processing is paused.
User Response: Do the following:
See TPF Operations for more information about the ZRECP ABORT and ZRECP LEVEL commands.
Program: BS0C
Error Message: ERROR ON MPRECP TBL, ITEM NOT FOUND, RECOUP ABORTED
Explanation: During recoup processing, an internal error occurred because the BS0C segment could not find an item in the recoup scheduling control table (IRSCT).
System Action: Recoup processing ends without being successfully completed.
User Response: See your IBM service representative.
Program: BS0C
Error Message: INVALID CASE CODE FOR BS0C
Explanation: During recoup processing, an internal error occurred because the BS0C segment was passed a case code that was not from 0 to 5.
System Action: Recoup processing continues.
User Response: See your IBM service representative.
Program: BS0C
Error Message: UNEXPECTED CORE BLOCK FOUND ON LEVEL 8
Explanation: During recoup processing, the BS0C segment tried to use data level 8, but this data level was already being used.
System Action: Recoup processing ends without being successfully completed.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred while processing a BSTAK macro. This error can be caused by several conditions, including the following:
System Action: The entry control block (ECB) exits.
User Response: Do the following:
See TPF System Macros for more information about the BSTAK macro. See TPF Database Reference for more information about recoup functions and procedures.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred while processing a BSAVE macro. This error can be caused by several conditions, including the following:
System Action: The ECB exits.
User Response: Do the following:
See TPF System Macros for more information about the BSAVE macro. See TPF Database Reference for more information about recoup functions and procedures.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred while processing a BRSTR macro. This error can be caused by several conditions, including the following:
System Action: The entry control block (ECB) exits.
User Response: Do the following:
See TPF System Macros for more information about the BRSTR and BSAVE macros. See TPF Database Reference for more information about recoup functions and procedures.
Program: BJ01
Error Message: UNABLE TO FIND RECOUP DESCRIPTOR CONTROL RECORD
Explanation: A ZRECP command was entered, but an error occurred while trying to find the descriptor control record (#BKDCTL).
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZRECP commands.
Program: BRR1, BRR3, BJ00
Error Message: None.
Explanation: The BRR1 segment received a FIWHC error while trying to find the recoup keypoint.
System Action: Recoup processing exits.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures.
Program: BRR1, BRR3, BJ00
Error Message: None.
Explanation: The BRR1 segment received a FACZ error while trying to retrieve the recoup keypoint.
System Action: Recoup processing exits.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures.
Program: BJ01
Error Message: ERROR ACCESSING SCHEDULER
Explanation: This dump occurs when recoup processing cannot access the IBM recoup scheduling control table (IRSCT). This dump is accompanied by a more specific online message.
System Action: Recoup processing ends abnormally.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures. See TPF Operations for more information about the ZRECP SETUP command.
Program: BJ03
Error Message: ERROR ACCESSING ROOT TABLE
Explanation: This dump occurs when recoup processing cannot access one of the IBM recoup active root tables (IRARTs). This dump is accompanied by a more specific online message.
System Action: Recoup processing ends abnormally.
User Response: Do the following:
See TPF Database Reference for more information about recoup functions and procedures. See TPF Operations for more information about the ZRECP SETUP command.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred because the system interprocessor communications (SIPC) ordinals do not match. An item to be SIPC to another process does not have an ordinal number in the PIDT table.
System Action: This ECB is ended.
User Response: Do the following:
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred because no active processor was found. Another processor was expected to still be active when this processor completed chain-chasing.
System Action: This ECB is ended.
User Response: Do the following:
In addition, your system programmer should consider reviewing the recoup working keypoint to determine which processor should be active.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: An error occurred because recoup received a returned message for system interprocessor communications (SIPC), which has no corresponding SIPC send.
System Action: This ECB is ended.
User Response: Do the following:
In addition, your system programmer should:
Program: Displayed on the console and in the dump.
Error Message:
Explanation: An ID that is not valid was found in the in-core copy of the capture and restore utility keypoint (BXAX) or the disk device control table (Bxx2). This condition is detected when a request to update the keypoint record to file is being serviced and is indicative of questionable main storage conditions.
When this error is found with no attached message, it is usually followed by other messages from the capture and restore utility.
System Action: The keypoint update request is not honored.
User Response: Do the following:
If the problems continue, see your system programmer for more information.
See the capture and restore utility information in TPF Database Reference for a complete description of the problem and action required.
Program: Displayed on the console and in the dump.
Error Message: None.
Explanation: This dump is associated with other messages from the capture and restore utility.
System Action: None.
User Response: None.
See the capture and restore utility information in TPF Database Reference for a complete description of the problem and action required.
Program: Displayed on the console and in the dump.
Error Message: INSUFFICIENT HEAP SPACE FOR EXTENT TABLE
Explanation: While trying to build the do not restore extent table for the module being restored, the Restore function was unable to allocate enough heap storage to hold the table.
System Action: A dump is issued and the ECB is exited.
User Response: Determine why there was not enough heap storage available. This is usually due to a software error or too many non-restorable extents being defined.
Program: Displayed on the console and in the dump.
Error Message: RTCUC EXTENTS RETURNED AN ERROR OR INVALID DATA
Explanation: While trying to build the non-restorable extent table for the module being restored, the restore function received an error return on the RTCUC EXTENTS macro or data in the returned extent table that is not valid.
System Action: A dump is issued and the ECB is exited.
User Response: Determine why there was an error returned from the RTCUC macro or why the data was not valid. This error may be caused by a logic error in the processing of the returned extent information.
Program: Displayed on the console and in the dump.
Error Message: EVENT ERROR DURING CAPTURE RESTART
Explanation: An error occurred during file capture restart while processing an EVNTC macro or an EVNWC macro for one of the following reasons:
With this error, there is the possibility that more modules may be started than allowed by the channel and control unit utilization parameters.
System Action: Capture file restart continues.
User Response: Do the following: