gtpm5m0a | Messages (Online) |
BKA00010E | SELECTIVE RECOUP ALREADY ACTIVE |
Explanation: The ZRECP SEL command was entered, but selective recoup is already active.
System Action: The command is rejected.
User Response: Wait until this selective chain chase is completed before running another one.
See TPF Operations for more information about the ZRECP SEL command.
BKA10001E | ERROR RETRIEVING ERROR INFO FROM RECOUP ONEL, RE-ENTER SAME ZRECP SEL COMMAND TO OVERRIDE THIS ERROR |
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.
BKA10002A | FIXED/TIMEOUT ERROR NOT FOUND - CHECK INPUT, OR RE-ENTER SAME ZRECP SEL COMMAND TO OVERRIDE THIS WARNING |
Explanation: The ZRECP SEL command was entered specifying a record ID that chain chased without any fixed or timeout errors.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZRECP SEL command.
BKA10003A | NO ERRORS WITH THAT ID - CHECK INPUT, OR RE-ENTER SAME ZRECP SEL COMMAND TO OVERRIDE THIS WARNING |
Explanation: The ZRECP SEL command was entered specifying a record ID that chain chased without errors.
System Action: The command is rejected.
User Response: Do the following:
See TPF Operations for more information about the ZRECP SEL command.
BKA10004W | 1052 STATE - ONLINE LOG NOT CHANGED |
Explanation: The ZRECP SEL command was entered with a record ID and file address specified, but TPF recoup processing was unable to remove the record ID from the SRCK1P file because the TPF system was in 1052 state.
System Action: Selective recoup processing ends.
User Response: Do the following:
See TPF Operations for more information about the ZRECP SEL command.
BKC10013W | MOUNT ADR TAPE FOR INPUT |
Explanation: The TPF system is processing a function that requires an ADR tape, but an ADR tape is not mounted.
System Action: None.
User Response: Mount the ADR tape.
BKC10014E | RECP SELD RESTART NOT ALLOWED FOR ONLINE OPTION |
Explanation: The ZRECP DUMP command was entered specifying the RESTART parameter but recoup runtime options were not set to use the ADR tape.
System Action: The command is rejected.
User Response: Enter ZRECP DUMP without specifying the RESTART parameter to start recoup phase 5 from the beginning.
See TPF Operations for more information about the ZRECP DUMP command.
BKP60001I | FC33 LOGGING RECORDS SWITCHED |
Explanation: This is a normal response to the ZRECP RECALL command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZRECP RECALL command.
BKP60002E | UNABLE TO SWITCH @BLOG ORDINAL |
Explanation: The ZRECP RECALL command was entered, but recoup processing was unable to switch the @BLOG ordinal.
System Action: None.
User Response: Do the following:
See TPF Operations for more information about the ZRECP RECALL, ZRECP ABORT, ZRPDU CREATE, ZDUPD, and ZRREC RESET commands.
BKP60003E | ***** RECOUP MUST BE ABORTED ***** |
Explanation: The ZRECP RECALL command was entered, but processing was unable to switch the released pool address (FC33) and RTA tapes on the active secondary processor.
System Action: Recoup processing is stopped internally.
User Response: Do the following:
See TPF Operations for more information about the ZRECP RECALL, ZRPDU CREATE, ZDUPD, and ZRREC RESET commands.
BKP60004E | TIMEOUT OCCURRED TRYING TO SWITCH @BLOG ORDINALS ON ACTIVE SECONDARY PROCESSOR |
Explanation: The ZRECP RECALL command was entered, but no response was received within the 3-minute time limit from an active secondary processor while trying to switch @BLOG ordinals on that processor.
System Action: Recoup processing is stopped internally.
User Response: Do the following:
See TPF Operations for more information about the ZRECP RECALL, ZRECP ABORT, ZRPDU CREATE, ZDUPD, and ZRREC RESET commands.
BKP60005E | UNABLE TO SWITCH @BLOG ORDINALS ON CPU-cpuid |
Where:
Explanation: The ZRECP RECALL command was entered, but all @BLOG ordinals on the processor shown in the message are in use and could not be switched.
System Action: Recoup processing is stopped internally.
User Response: Do the following:
See TPF Operations for more information about the ZRECP RECALL, ZRPDU CREATE, ZDUPD, and ZRREC RESET commands.
BKP60006E | UNDEFINED ERROR RETURNED FROM POSTC WHILE SWITCHING @BLOG ORDINALS ON ACTIVE SECONDARY PROCESSOR |
Explanation: The ZRECP RECALL command was entered, but an error code was returned from an active secondary processor that was not recognized by the primary processor. This occurred while trying to switch @BLOG ordinals on the active secondary processor.
System Action: Recoup processing is stopped internally.
User Response: Do the following:
See TPF Operations for more information about the
ZRECP RECALL, ZRPDU CREATE, ZDUPD, and ZRREC RESET commands.
Explanation: The ZRECP RECALL command was entered, but a timeout
or other error occurred while waiting for another active processor in the
complex to successfully clear the TPF collection support (TPFCS) pool reuse
table.
System Action: Message RECP0668E may have been issued on another processor in the
complex. Recoup processing is stopped internally.
User Response: Do the following:
See TPF Operations for more information about the
ZRECP RECALL command. See Messages (Online) for more information about message
RECP0668E.BKP60007E ERROR OCCURRED WAITING FOR TPFCS POOL REUSE TABLE TO BE CLEARED ON
ALL ACTIVE PROCESSORS
BLOG0001W | ALL FC33 ORDINALS IN USE - RUN ZRPDU WITH NO SWITCH |
Explanation: The ZRPDU CREATE, ZRREC SWITCH, or ZRECP RECALL command was entered, but all released pool address (FC33) ordinals are in use.
System Action: The command fails.
User Response: Enter the following:
See TPF Operations for more information about the ZRPDU CREATE, ZRREC SWITCH, ZDUPD, ZRREC RESET, and ZRECP RECALLcommands.
BLOG0002I | UNABLE TO SWITCH FC33 ORDINAL NUMBERS |
Explanation: The ZRPDU CREATE command was entered, but processing cannot switch the released pool address (FC33) ordinal numbers.
System Action: The command fails.
User Response: Do the following:
See TPF Operations for more information about the ZRPDU CREATE command.
BLOG0003E | FC33 RECORDS SWITCHED DURING CYCLE UP - FIND ERROR ON PREVIOUS RECORD. |
Explanation: During a TPF system cycle up or restart, an error condition was detected by the FINWC macro while trying to retrieve the last keypointed released pool address (FC33) record.
System Action: None.
User Response: Enter the ZRPDU CREATE command again, specifying any parameters that were previously specified before the TPF system cycled up, because FC33 records do not contain correct data.
See TPF Operations for more information about the ZRPDU CREATE command. See TPF General Macros for more information about the FINWC macro.
BLOG0004W | GFS NOT ACTIVE AT THIS TIME |
Explanation: During a TPF system cycle up or restart, get file storage (GFS) is not active.
System Action: The TPF system files the released pool address (FC33) record but does not complete any ZRPDU CREATE processing that was in progress.
User Response: Enter the ZRPDU CREATE command again, specifying any parameters that were previously specified before the TPF system cycled up.
See TPF Operations for more information about the ZRPDU CREATE command.
BLOG0005W | ERROR FILING POOL CONTROL AREA |
Explanation: During a TPF system cycle up or restart, an error condition was detected by the FILNC macro while trying to file the recoup global.
System Action: None.
User Response: Enter the ZRPDU CREATE command again, specifying any parameters that were previously specified before the TPF system cycled up because the recoup global does not contain correct information.
See TPF Operations for more information about the ZRPDU CREATE command. See TPF General Macros for more information about the FILNC macro.
BLOG0006I | FC33 ORDINALS HAVE BEEN MADE AVAILABLE TO THIS PROCESSOR, MOST POOLS PREVIOUSLY RELEASED MAY NOW BE LOST |
Explanation: This is a normal response to the ZRREC RESET command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZRREC RESET command.
BLOG0007I | AN FC33 ORDINAL HAS BEEN MADE AVAILABLE TO THIS PROCESSOR; SOME POOLS PREVIOUSLY RELEASED MAY NOW BE LOST |
Explanation: This is a normal response to the ZRREC BACKUP command.
System Action: None.
User Response: None.
See TPF Operations for more information about the ZRREC BACKUP command.
BLOG0008W | ERROR ON FC33 FILE DOWN, FC33 WILL BE RE-CHAINED |
Explanation: During a TPF system cycle up or restart, an error condition was detected by the FILNC macro while trying to file the released pool address (FC33) record.
System Action: None.
User Response: None.
See TPF General Macros for more information about the FILNC macro.
BLOH0001W | ALL FC33 ORDINALS IN USE - TO CONTINUE RUN ZRPDU CREATE NOSWITCH, ZDUPD S, ZDUPD C AND ZRREC RESET |
Explanation: The ZRECP RECALL, ZRPDU CREATE, or ZRREC SWITCH command was entered, but all FC33 (index into the CA records) ordinals are in use.
System Action: The command fails.
User Response: Do the following:
See TPF Operations for more information about the ZRECP RECALL, ZRPDU CREATE, ZRREC SWITCH, ZDUPD, and ZRREC RESET commands.
BMD10002E | TAPE WRITE ERROR |
Explanation: The ZRECP DUMP command was entered, but was unable to write a TRACE or SELD record to the RTL tape.
System Action: The command fails to write this record, but continues on to the next.
User Response: Do the following:
See TPF Operations for more information about the ZRECP DUMP command.
BMS20001E | BLOCK xxx NOT FOUND |
Where:
Explanation: The block number specified in the ZSTVS START command was not found.
System Action: None.
User Response: Check that proper TUT was mounted.
BMS20001I | RUNID PROCESSING RESUMED AFTER PAUSE/STOP REQUEST |
Explanation: None.
System Action: None.
User Response: None.
BMS20001I | RUNID PROCESSING RESUMED FROM CURRENT BLOCK AFTER PAUSE REQUEST |
Explanation: None.
System Action: None.
User Response: None.
BMS20003E | NINES RECORD MISSING ON TUT |
Explanation: An error occurred because the test unit tape (TUT) is not formatted correctly so the program test vehicle (PTV) cannot run currently.
System Action: The TUT is dismounted and is closed.
User Response: Check the tape.
BMS20004E |
Explanation: An error occurred because the test unit tape (TUT) is not formatted correctly so the program test vehicle (PTV) cannot run currently.
System Action: The TUT is dismounted and is closed.
User Response: Check the tape.
BMS80000E | TUT TAPE NOT RESERVED |
Explanation: The ZSTVS message processor tried to assign a test unit tape (TUT) but the TUT was not reserved.
System Action: None.
User Response: Do the following:
BMS80004E | TUT TAPE NOT ASSIGNED -- PROCESSING STOPPED |
Explanation: The ZSTVS message processor tried to read the test unit tape (TUT) but the TUT was not assigned.
System Action: None.
User Response: Do the following:
BMS80008E | INVALID FORMAT -- MESSAGE IGNORED |
Explanation: A ZSTVS command was entered incorrectly.
System Action: None.
User Response: Do the following:
BMS80012E | INVALID MODE PARAMETER |
Explanation: The Mode parameter was specified incorrectly on the ZSTVS START command. The value specified on the Mode parameter must be A or B.
System Action: None.
User Response: Do the following:
BMS80016E | STV NOT ACTIVE |
Explanation: A ZSTVS command that is valid only in the system test vehicle (STV) was entered, but STV is not active.
System Action: None.
User Response: Do the following:
BMS80020E | STV CURRENTLY ACTIVE |
Explanation: There was an attempt to start the program test vehicle (PTV) when the system test vehicle (STV) was already active.
System Action: None.
User Response: Do the following:
BMS80024E | COMMANDS OUT OF SEQUENCE -- RESET PTV |
Explanation: A ZSTVS command was entered at the wrong time.
System Action: None.
User Response: Enter the ZSTVS TEST RESET command to reset the program test vehicle (PTV).
BMS80028E | INVALID REQUEST -- NOT IN NORM STATE -- MESSAGE IGNORED |
Explanation: An attempt was made to start the system test vehicle (STV) when the TPF system was not in NORM state.
System Action: None.
User Response: Do the following:
BMS80032E | LIVE TEST ACTIVE -- INVALID REQUEST -- RESET ONLY VALID |
Explanation: A ZSTVS command was entered when the TPF system was in live mode rather than test mode.
System Action: None.
User Response: Reset the program test vehicle (PTV) by entering the ZSTVS TEST RESET command.
BMS80036E | PTV ALREADY ACTIVE |
Explanation: An attempt was made to start the program test vehicle (PTV) when PTV was already active.
System Action: None.
User Response: None.
BMS80040E | UNABLE TO RETRIEVE PTVA |
Explanation: The program test vehicle (PTV) keypoint could not be read.
System Action: None.
User Response: See your system programmer to determine the cause of the error and to correct it.
BMS80044E | SYSTEM NOT IN UNI MODE -- PTV REQUEST IGNORED |
Explanation: The program test vehicle (PTV) runs only in a one I-stream single processor mode.
System Action: None.
User Response: Enter the ZCNIS UP command to make the TPF system a single I-stream.
BMS80048E | INVALID REQUEST -- TEST NOT PAUSED -- MESSAGE IGNORED |
Explanation: A ZSTVS START POSIT command was entered and the program test vehicle (PTV) was not paused.
System Action: None.
User Response: None.
BMS80052E | ZSTVS TEST MESSAGE ONLY VALID IN RESTART -- ENTER ZRIPL |
Explanation: A ZSTVS TEST STV, ZSTVS TEST YES, or ZSTVS TEST LIVE command was entered, but the TPF system is not in restart.
System Action: None.
User Response: Enter the ZRIPL command to set the program test vehicle (PTV) phase. A ZSTVS TEST RESET command may be required to be prompted for the PTV phase.