gtpm5m2aMessages (Online)

RECP0000A-RECP00BEI

RECP0000ASIPC TIMEOUT ON THE FOLLOWING MESSAGE/FUNCTION function procid PROCESSOR CHAIN CHASE NOT STARTED addlinfo

Where:

function
The function is one of the following:

BKP6RTAS2 or BKP6BJ05
The calling program is BKP6.

BKP3RTAS2 or BKP3BJ05
The calling program is BKP3.

procid
The processor ID.

addlinfo
One of the following:

Explanation: One of the following occurred:

System Action: Recoup processing stops.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Start recoup processing again. If you cannot start recoup processing again, enter ZRECP ABORT or ZRECP ABORT BP and then start recoup processing.

See TPF Operations for more information about the recoup function, and the ZRECP ABORT command. See TPF Database Reference for more information about recoup functions and procedures.

RECP0000ASIPC TIMEOUT ON THE FOLLOWING MESSAGE/FUNCTION function procid PROCESSOR RTA NOT SWITCHED addlinfo

Where:

function
The function is one of the following:

BKP6RTA
Captures the long-term file pool directory records onto the phase 1 captured SONRI directory (#STPKP).

BKP6RTAP3
Captures the long-term file pool directory records onto the phase 3 captured SONRI directory (#SONCP).

procid
The processor ID.

addlinfo
One of the following:

Explanation: An attempt to switch RTA tapes at the start of recoup phase 1 processing failed because SIPCC macro return processing cannot communicate with the intended processor. Additionally, virtual file access (VFA) files or processor globals are not cleared.

System Action: Recoup processing stops on the indicated processor and can end abnormally.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. If recoup processing ends abnormally, start recoup processing again.
  4. If recoup processing does not end abnormally and does not continue, enter ZRECP ABORT or ZRECP ABORT BP and then start recoup processing again.

See TPF Operations for more information about the recoup function, and the ZRECP ABORT command. See TPF Database Reference for more information about recoup functions and procedures.

RECP0000ESIPC TIMEOUT ON THE FOLLOWING FUNCTION: ZRECP PROC cpuid START

Where:

cpuid
One of the following:

Explanation:

Explanation: The ZRECP START command was entered specifying the PROC parameter but a timeout has occurred in SIPCC processing.

System Action: The command fails and takes a system error.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP START command specifying the PROC parameter again.

See TPF Operations for more information about the ZRECP START command.

RECP0000ESIPC TIMEOUT ON THE FOLLOWING FUNCTION: ZRECP PROC cpuid STOP

Where:

cpuid
One of the following:

Explanation: The ZRECP STOP command was entered specifying the PROC parameter but a timeout has occurred in SIPCC processing.

System Action: The command fails and takes a system error.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP STOP command specifying the PROC parameter again.

See TPF Operations for more information about the ZRECP STOP command.

RECP0000ESIPC TIMEOUT ON THE FOLLOWING FUNCTION: ZRECP PROC cpuid EXIT

Where:

cpuid
One of the following:

Explanation: The ZRECP EXIT command was entered specifying the PROC parameter but a timeout has occurred in SIPCC processing.

System Action: The command fails and takes a system error.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP EXIT command specifying the PROC parameter again.

See TPF Operations for more information about the ZRECP EXIT command.

RECP0000ESIPC TIMEOUT ON THE FOLLOWING FUNCTION: ZRECP PROC cpuid RESTART

Where:

cpuid
One of the following:

Explanation: The ZRECP RESTART command was entered specifying the PROC parameter but a timeout has occurred in SIPCC processing.

System Action: The command fails and takes a system error.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP RESTART command specifying the PROC parameter again.

See TPF Operations for more information about the ZRECP RESTART command.

RECP0000ESIPC TIMEOUT ON THE FOLLOWING FUNCTION: ZRECP PROC cpuid LEVEL-ecblevel

Where:

cpuid
One of the following:

ecblevel
The number of entry control blocks (ECBs).

Explanation: The ZRECP LEVEL command was entered specifying the PROC parameter but a timeout has occurred in SIPCC processing.

System Action: The command fails and takes a system error.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP LEVEL command specifying the PROC parameter again.

See TPF Operations for more information about the ZRECP LEVEL command.

RECP0000ESIPC TIMEOUT ON THE FOLLOWING FUNCTION: ZRECP PROC cpuid STATUS

Where:

cpuid
One of the following:

Explanation: The ZRECP STATUS command was entered specifying the PROC parameter but a timeout has occurred in SIPCC processing.

System Action: The command fails and takes a system error.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP STATUS command specifying the PROC parameter again.

See TPF Operations for more information about the ZRECP STATUS command.

RECP0000ESIPC TIMEOUT ON THE FOLLOWING FUNCTION: ZRECP PROC cpuid REPORT

Where:

cpuid
One of the following:

Explanation: The ZRECP REPORT command was entered specifying the PROC parameter but a timeout has occurred in SIPCC processing.

System Action: The command fails and takes a system error.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP REPORT command specifying the PROC parameter again.

See TPF Operations for more information about the ZRECP REPORT command.

RECP0000ESIPC TIMEOUT ON THE FOLLOWING FUNCTION: ZRECP PROC cpuid FLUSH

Where:

cpuid
One of the following:

Explanation: The ZRECP FLUSH command was entered specifying the PROC parameter but a timeout has occurred in SIPCC processing.

System Action: The command fails and takes a system error.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP FLUSH command specifying the PROC parameter again.

See TPF Operations for more information about the ZRECP FLUSH command.

RECP0000IBEGIN GROUP ID - charid,'hexid' VSN - version

Where:

charid
The 2-character representation of the record ID that is being processed.

hexid
The 4-character hexadecimal representation of the record ID that is being processed.

version
The version of the record ID.

Explanation: This is a normal message during recoup processing, indicating that the specific group has just begun chain chase processing.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0000IDIRECTORY CAPTURE IN PROGRESS - ORD# ordnum

Where:

ordnum
The ordinal number of a released pool address (FC33) record.

Explanation: This is a normal response to the ZRECP STATUS command, or the ZRECP LEVEL command was entered while recoup processing is in the directory capture portion of phase 1.

System Action: None.

User Response: Do one of the following:

See TPF Operations for more information about the ZRECP STATUS and ZRECP LEVEL commands.

RECP0000IPSEUDO DIRECTORY/ID TABLE INIT IN PROGRESS

Explanation: The ZRECP STATUS or ZRECP LEVEL command was entered, but recoup phase 1 is initializing the recoup pseudo directory (#SONRPE) or ID table.

System Action: The command is rejected.

User Response: Do the following:

  1. Wait until recoup phase 1 ends initializing the recoup pseudo directory (#SONRPE) or ID table.
  2. Enter the ZRECP STATUS or ZRECP LEVEL command again.

See TPF Operations for more information about the ZRECP STATUS and ZRECP LEVEL commands.

RECP0000ILEVEL ENTRY INCORRECT AT THIS TIME AUTO PAUSE IN PROGRESS

Explanation: The ZRECP LEVEL command was entered, but the BRMK segment has detected from the recoup keypoint (BK0TBL) that an internal pause is in progress. An internal pause occurs when the number of active recoup entry control blocks (ECBs) equals the number of ECBs that are looping in the BPM1 segment.

System Action: The command is rejected.

User Response: Do the following:

  1. Wait until recoup resumes processing after all ECBs have completed processing.
  2. Enter the ZRECP LEVEL command again.

See TPF Operations for more information about the ZRECP LEVEL command.

RECP0000IWAITING FOR SECONDARY PROCESSORS TO COMPLETE, CHECKING ONCE A MINUTE

Explanation: The ZRECP STATUS command was entered specifying the PROC parameter or an internal status request was processed, but the primary processor is waiting to receive responses from the secondary processors.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP STATUS command.

RECP0000ITOTAL NUMBER OF FIXED ERRORS errnum

Where:

errnum
The number of fixed errors.

Explanation: This is a normal response to the ZRECP STATUS command indicating the number of fixed errors that have occurred during phase 1 chain chase.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP STATUS command.

RECP0000IRECP LEVEL COMPLETE

Explanation: This is a normal response to the ZRECP LEVEL command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP LEVEL command.

RECP0000IADR READ ERROR - INPUT BLOCK LOST

Explanation: There is only one possible error during recoup phase 5. This occurs when there is a problem reading the input ADR tape.

System Action: The program tries to keep reading the ADR to continue processing.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0000IPHASE1 TIME -- hours HRS. minutes MINS.

Where:

hours
The hours.

minutes
The minutes.

Explanation: This is the normal response to the ZRECP RERUN and ZRECP RESUME commands.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP RERUN and ZRECP RESUME commands.

RECP0000IRECP LEVEL COMPLETE

Explanation: This is the normal response to the ZRECP LEVEL command. It is followed by the recoup status message.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP LEVEL command.

RECP0000ISTART OF RECOUP SELD - LOST ADDRESSES FIRST

Explanation: This is a normal response to the ZRECP DUMP command indicating that lost address processing has begun.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP DUMP command.

RECP0000IRECP SELD - START OF ERRONEOUSLY AVAILABLE ADDRS

Explanation: This is a normal response to the ZRECP DUMP command indicating that erroneously available address processing has begun.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP DUMP command.

RECP0000IRECP SELD COMPLETED

Explanation: This is the normal response to the ZRECP DUMP command indicating that erroneously available address processing has completed.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP DUMP command.

RECP0000Irecords1 RECORDS READ / records2 RECORDS WRITTEN

Where:

records1
The records read.

records2
The records written.

Explanation: This is the normal response to the ZRECP LOAD command with the ALL parameter specified.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP LOAD command.

RECP0000TRECP SELD ABORTED

Explanation: This is the normal response to the ZRECP DUMP ABORT command.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0000TRECP SELD ALREADY ACTIVE

Explanation: The ZRECP DUMP command was entered, but a selective dump is already active.

System Action: Recoup processing ends.

User Response: Determine why the ZRECP DUMP command was entered twice.

See TPF Operations for more information about the ZRECP DUMP command.

RECP0000TIN CORE DIRECTORY CAPTURE TIME-OUT ON PROCESSOR cpuid

Where:

cpuid
The name of the processor.

Explanation: The directory capture did not complete in the allowed time. The time allowed for the directory capture is set by the DIRTIM parameter in the ZRECP PROFILE command.

System Action: Begin abort processing.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.

See TPF Operations for more information about the ZRECP PROFILE command. See TPF Database Reference for more information about recoup functions and procedures.

RECP0000TRECP DUMP OPTION ERROR RETRY ENTRY

Explanation:

Explanation: The ZRECP DUMP command was entered, but an error condition was detected by a FACS-type call or the FINWC macro while trying to retrieve the recoup master keypoint (BK0RP).

System Action: None.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP DUMP command again.

See TPF Operations for more information about the ZRECP DUMP command. See TPF System Macros and TPF Application Programming for more information about the FACS program and the FACS interface.

RECP0000TRECP TAPE READ ERROR - INPUT BLOCK LOST.

Explanation: The ZRECP DUMP command was entered, but recoup processing found an ADR tape read error.

System Action: None.

User Response: Determine the cause of the problem.

See TPF Operations for more information about the ZRECP DUMP command.

RECP0000TRECP SELD -- TAPE READ ERROR -- MAX 209 RECS LOST

Explanation: The ZRECP DUMP command was entered, but there was a problem reading the input ADR tape.

System Action: Recoup processing continues.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP DUMP command.

RECP0000TUNABLE TO READ KEYPOINT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup phase 1 or recoup phase 3 is unable to read the recoup keypoint (RCPK) record.

System Action: The recoup function will either abort or need to be aborted manually.

User Response: Do the following:

  1. Correct the RCPK record.
  2. Start the recoup function again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0000TRECP L8E8 READ ERROR - INPUT BLOCK LOST.

Explanation: The ZRECP DUMP command was entered specifying the RESTART parameter but an error condition was detected by a FACE-type call while trying to retrieve or the FINWC macro while trying to find the L8 (lost addresses) record or the E8 (erroneously available addresses) record.

System Action: The command fails.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the ZRECP DUMP command specifying the RESTART parameter again.

See TPF Operations for more information about the ZRECP DUMP command. See TPF System Macros and TPF Application Programming for more information about the file address compute (FACE) program and the FACE interface.

RECP0001ESONRPE RECORD INITIALISATION INCOMPLETE

Explanation: During recoup restart processing, a status check fails.

System Action: Recoup processing fails.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Start recoup processing again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0001IRESTART

Explanation: This is the normal response to the ZRECP RESTART command.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP RESTART command.

RECP0001IBEGIN GROUP ID - charid,'hexid' VSN - version

Where:

charid
The 2-character representation of the record ID that is being processed.

hexid
The 4-character hexadecimal representation of the record ID that is being processed.

version
The version of the record ID.

Explanation: This is a normal message during recoup processing, indicating that the specific group has just begun chain chase processing.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0001ISTARTING GROUP ID - charid,'hexid' VSN - version FOR SSU - ssun , PROC - cpuid , ISTREAM - istreamnum

Where:

charid
The 2-character representation of the record ID that is being processed.

hexid
The 4-character hexadecimal representation of the record ID that is being processed.

version
The version of the descriptor group.

ssun
The four-character subsystem user (SSU) name.

cpuid
The name of the processor.

istreamnum
The I-stream, which is displayed as a decimal number.

Explanation: This is a normal message during recoup processing, indicating that a unique instance of the specific group has just begun chain chase processing.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0002IT-records1 C-records2 MAX ENT-entry1 DIFF-ecb SE-errors1 I-xx charid,'hexid' VSN version status

Where:

records1
The total number of fixed record types and data stores to be processed during chain chase processing.

records2
The total number of fixed record types and data stores completed.

entry1
The maximum number of entry control blocks (ECBs) currently allowed.

ecb
The number of created ECBs that are currently active.

errors1
The number of timeout errors issued up to this point.

xx
The I-stream, which is displayed as a decimal number, that is the I-stream owner of the records currently being chain chased.

charid
The 2-character representation of the record ID that is being processed.

hexid
The 4-character hexadecimal representation of the record ID that is being processed.

version
The version of the record ID that is being processed.

status
The status of chain chase processing (COMPLETED or PROCESSING).

Explanation: This is the standard message that is displayed automatically:

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP STATUS command.

RECP0002TUNABLE TO WRITE KEYPOINT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A recoup program was not able to file the recoup keypoint (RCPK) record successfully.

System Action: None.

User Response: Do the following:

  1. Determine the cause of the error.
  2. End the recoup function.
  3. Start the recoup function again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0003IPSEUDO DIRECTORY INITIALIZATION STARTED

Explanation: This is a normal message during recoup phase 1 processing indicating that pseudo directory initialization has begun.

System Action: Recoup processing continues.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0004IRECP PRIM COMPLETE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is the normal response to the ZRECP PRIM command. It is followed by the recoup status message.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0005WINIT OF PROCESSOR - cpuid'S PSEUDO DIRECTORIES TAKING LONGER THAN EXPECTED.

Where:

cpuid
The name of the processor.

Explanation: The time it has taken for recoup processing to initialize pseudo directories has exceeded the time that was set using the ZRECP PROFILE command.

System Action: Recoup processing continues.

User Response: None.

See TPF Operations for more information about the ZRECP PROFILE command. See TPF Database Reference for more information about recoup functions and procedures

RECP0006TILLEGAL ACTION originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The format of the command is not valid or an attempt was made to run recoup while the TPF system is not in the correct state.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Enter the command again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0008ISWITCHING RTA originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Switching the primary RTA tape from the active to the standby.

System Action: The TPF system switches the RTA tapes.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0009WVFA ERROR FLUSHING OUT PROC - cpuid PSEUDO DIRECTORY (dirname), ORD NBR - ordnum, ADDRESS - faddr

Where:

cpuid
The name of the processor.

dirname
The name of the pseudo directory.

ordnum
The hexadecimal ordinal number of the pseudo directory record.

faddr
The file address of the pseudo directory record.

Explanation: During recoup processing, the FLVFC macro has taken more than 10 significant errors on the pseudo directory. This value is set in the BRV0 segment.

System Action: None.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Start recoup processing again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP000CAENSURE THE RGF DATA SET IS MOUNTED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is an informational message to remind you to have the recoup general file data set mounted prior to inputting any more messages.

System Action: None.

User Response: Ensure that the general file is mounted.

See TPF Operations for more information about the recoup function.

RECP000EACYCLE-DOWN SYSTEM originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: None.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0010AENTER RECALL MESSAGE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This message is the response to the ZRECP RESTART command, which is used when the recoup function was started previously and processing needs to be redone.

System Action: None.

User Response: Enter the ZRECP RECALL command.

See TPF Operations for more information about the ZRECP RECALL command.

RECP0010ETAPE DATA CHECK ENCOUNTERED. ATTEMPTING INTERNAL RECOUP RESTART

Explanation: During recoup phase 1 processing, a data check error occurred while trying to write to the RCP tape.

System Action: Recoup processing tries to do an internal restart to continue.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0010ETAPE CHECK ENCOUNTERED. INTERNAL RESTART FAILED - MANUAL RESTART REQUIRED.

Explanation: During recoup phase 1 processing, a data check error occurred while trying to write to the RCP tape.

System Action: Recoup processing fails.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Start recoup processing again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0012AFIXED ERROR -- RESPOND originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: None.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0013WMOUNT RCP TAPE FOR OUTPUT

Explanation: Recoup phase 1 requires that the RCP tape be mounted for output on that subsystem.

System Action: Recoup phase 1 does not continue to run.

User Response: Mount an RCP tape for output.

RECP0014ADEFERRING UNTIL SEL RECOUP COMPLETE OR CONTINUE RESPOND originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: During recoup phase 1 processing, one or more fixed records were found to be in error.

System Action: The recoup function pauses until you respond.

User Response: Do one of the following:

See TPF Database Reference for more information about recoup functions and procedures.

RECP0016IPHASE I COMPLETED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal message indicating that recoup phase 1 processing has finished.

System Action: Recoup processing continues with phase 2.

User Response: See TPF Database Reference for more information about recoup functions and procedures.

RECP0018IPHASE III COMPLETED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal message indicating that recoup phase 3 processing has finished.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP001ATRECOUP ABORTED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The recoup function is unable to continue and it is exited from the TPF system.

System Action: The recoup function is exited.

User Response: Do the following:

  1. Correct the problem that is causing the abort. Use the messages that appear prior to the ABORT message and the 041001 system error to determine the problem.
  2. Start the recoup function again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP001CWSEQUENCE ERROR originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The message is out of sequence for this point in recoup processing.

System Action: None.

User Response: Enter the correct command.

See TPF Database Reference for more information about recoup functions and procedures.

RECP001EADESTRUCTIVE SEGMENT-RESPOND originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup phase 3 is waiting to roll-in updated file pool directories or to skip to the end of recoup phase 3.

System Action: None.

User Response: Respond with either the recoup SKIP or PROCEED message.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0020AENSURE RCP TAPE MOUNTED FOR OUTPUT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal message during recoup processing to remind you to have the RCP tape mounted.

System Action: None.

User Response: Ensure that the RCP tape is mounted.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0022TCANNOT WRITE RCP originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The recoup output writer segment was not able to write to the RCP tape.

System Action: The recoup function is stopped because of a tape problem.

User Response: Do the following:

  1. Correct the tape problem.
  2. Enter ZRECP RESTART to start the recoup function again.

See TPF Operations for more information about the recoup function and the ZRECP RESTART command.

RECP0026ICAPTURE FINISHED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal message during recoup processing indicating that recoup phase 1 has finished capturing the pool rollin directory (#SONRI) to the phase 1 captured SONRI directory (#STPKP) or to the phase 3 captured SONRI directory (#SONCP).

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0028ASYSTEM MAY BE CYCLED-UP originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: During a recoup phase 1 start in 1052 state, the TPF system is now ready to be cycled to NORM state.

System Action: None.

User Response: Cycle the TPF system to NORM state, or not, as desired.

See TPF Database Reference for more information about recoup functions and procedures.

RECP002AAERROR -- RETRY OR ABORT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A problem was encountered trying to read the recoup phase 3 input RPE tape.

System Action: The recoup function is paused and waiting for a response.

User Response: Do the following:

  1. Determine the cause of the problem. You can use the recoup system error dump that immediately preceded this message to help with problem resolution.
  2. Correct the problem.
  3. Enter the ZRECP RETRY or the ZRECP ABORT command.

See TPF Operations for more information about the recoup function, and the ZRECP RETRY and ZRECP ABORT commands.

RECP002CIDIRECTORY ROLL-IN COMPLETED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup phase 3 finished writing the new file pool directories to file.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP002EAENTER RETRY OR ABORT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: During recoup processing, there was a sequence error during file pool directory reading.

System Action: Recoup processing is paused and waiting for a response.

User Response: Enter one of the following:

See TPF Operations for more information about the recoup function, and the ZRECP RETRY and ZRECP ABORT commands.

RECP0034AUNABLE TO FIND DESCRIPTOR -- CHECK INPUT -- originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP SEL command was entered or the ZRECP RECALL command was entered with the SEL parameter specified, but recoup processing was unable to find the record to be processed.

System Action: Recoup processing does one of the following:

User Response: Enter the command correctly.

See TPF Operations for more information about the ZRECP SEL and ZRECP RECALL commands.

RECP0036ISELECTIVE RECOUP OF ID FILE/ADR FIN originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Selective processing for the specified record is complete.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0038ISON DIR CAPT STARTED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal message during recoup processing indicating that recoup phase 1 has started capturing the pool rollin directory (#SONRI) to the phase 1 captured SONRI directory (#STPKP) or to the phase 3 captured SONRI directory (#SONCP).

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP003AISON DIR ROLLIN STARTED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup phase 3 has started to file the new file pool directory records.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP003CAENTER ZRECP RECALL WHEN READY originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal response to the ZRECP RESUME command if ADR-YES was previously specified with the ZRECP PROFILE command. This message follows RECP0048A, which requests you to mount an ADR tape.

System Action: Recoup processing is paused and waiting for a response.

User Response: Once you have mounted the ADR tape, enter ZRECP RECALL.

See TPF Operations for more information about the ZRECP RECALL command.

RECP003EAIPL SYSTEM AND REENTER RERUN REQUEST originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP RERUN command was entered, but recoup processing is unable to rerun recoup phase 3 without a system IPL.

System Action: The command fails.

User Response: Do the following:

  1. IPL the TPF system if the recoup phase 3 run is to be rerun.
  2. Enter the ZRECP RERUN command again.

See TPF Operations for more information about the ZRECP RERUN command.

RECP0040IRETRY originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is the normal response to the ZRECP RETRY command.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0042TABORT DUE TO RCI ERROR originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup phase 1 was unable to read or process information on the RCI input tape.

System Action: The recoup function is ended and is exited from the TPF system.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Run recoup phase 1 again from the start.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0044AMOUNT THE FIRST RCI TAPE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup phase 1 was restarted at the point where it needs to read the RCI input tape.

System Action: The recoup function is waiting for the RCI tape to be mounted.

User Response: Mount the first RCI tape.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0046TERROR FILING SAT/SRT RECORDS originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup phase 1 tried to file the subarea address table (SAT) and the system recovery table (SRT) records in core. During this process, one of the following errors occurred:

System Action: The filing of the SAT and SRT records is stopped immediately. Recoup phase 1 is aborted.

User Response: Do one of the following:

RECP0048AMOUNT ADR TAPE FOR LOST/EA POOL ADDRESS ANALYSIS originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal response to the ZRECP RESUME command if ADR-YES was previously specified with the ZRECP PROFILE command.

System Action: None.

User Response: Mount the ADR tape.

See TPF Operations for more information about the ZRECP RESUME and ZRECP PROFILE commands.

RECP004ATPROGRAM progname NOT ACTIVE - RECOUP ABORTED originid

Where:

progname
The program name.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: An INDEX macro statement was entered with the MET=(PROG,method) parameter specified, but an active version of the user-defined method (a program used for recoup chain chase processing) was not found.

Note:
All programs that were allocated will automatically have at least one active version online. Programs that have not been allocated can still receive control provided that they were loaded and activated through the E-type loader. This message, therefore, can only occur when the program is not allocated and has not been activated by the E-type loader.

System Action: Recoup phase 1 is ended abnormally.

User Response: Do one of the following:

See TPF Operations for more information about the recoup function and the ZOLDR ACTIVATE command.

RECP004CAENSURE STANDBY RTA AND ALT TAPE MOUNTED FOR PHASE 1 originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal response to the ZRECP START command.

System Action: None.

User Response: If not already mounted, mount the RTA and ALT tapes.

See TPF Operations for more information about the ZRECP START command.

RECP004EIRECOUP ABORT IN PROGRESS originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is the normal response to the ZRECP ABORT command. This message is also displayed if recoup ends internally.

System Action: Recoup is aborting.

User Response: None.

See TPF Operations for more information about the ZRECP ABORT command.

RECP0050WSSU ssu NOT ACTIVE originid

Where:

ssu
The subsystem user (SSU).

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In an MDBF environment.) The SSU referenced in the message is not available for recoup phase 1 processing. On a RECALL SEL ID process, the RECP0052W message is not given.

System Action: On a RECALL SEL ID process, recoup phase 1 is ended.

User Response: If this is not a RECALL SEL ID process, then this is just an informational message. It is up to you or the system programmer to determine whether this SSU must be activated prior to the RECALL message.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0051EIL recordid -- recordaddr -- originid

Where:

recordid
The ID of the record.

recordaddr
The address of the record.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Trying to find an illegal address (that is not valid in this TPF system).

System Action: Recoup phase 1 is continued.

User Response: Do the following:

  1. Determine the cause of this error.
  2. Ignore the error or correct it and selectively recoup this record at the end of recoup phase 1.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0052WACTIVATE PRIOR TO RECALL originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In an MDBF environment). The subsystem user (SSU) that is referenced in the message is not available for recoup phase 1 processing.

This is an informational message.

System Action: Recoup phase 1 is continued.

User Response: Your system programmer should determine whether this SSU must be activated prior to the RECALL message.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0053ECL recordid -- recordaddr -- originid

Where:

recordid
The ID of the record.

recordaddr
The address of the record.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: An index that is not valid was encountered in this record.

System Action: Recoup phase 1 is continued.

User Response: Do the following:

  1. Determine the cause of this error.
  2. Ignore the error or correct it and selectively recoup this record at the end of recoup phase 1.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0054WPHASE 1 RESULTS MAY BE INVALID originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In an MDBF environment). One or more subsystem users (SSUs) were not available to recoup for phase 1 processing.

System Action: Recoup phase 1 is continued.

User Response: Do the following:

  1. Determine whether the unavailable SSUs will cause the recoup phase 1 run to be invalidated.
  2. Continue with the recoup phase 1 or start recoup phase 1 over with the missing SSUs activated.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0055EID recordid -- recordaddr -- id, ssu originid

Where:

recordid
The ID of the record.

recordaddr.
The address of the record.

id
The ID actually found.

ssu
The name of the subsystem user (SSU) where the target record resides.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup phase 1 was trying to find this record and it did not have the ID expected.

System Action: Recoup phase 1 is continued.

User Response: Do the following:

  1. Determine the cause of this error.
  2. Ignore the error or correct it and selectively recoup this record at the end of recoup phase 1.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0056IONE OR MORE SSUS WERE NOT ACTIVE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: None.

System Action: None.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0057EHD recordid -- recordaddr -- originid

Where:

recordid
The ID of the record.

recordaddr
The address of the record.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A hardware error was encountered while trying to find this record.

System Action: Recoup phase 1 is continued.

User Response: Do the following:

  1. Determine the cause of this error.
  2. Ignore the error or correct it and selectively recoup this record at the end of recoup phase 1.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0059EFA recordid--faceordnum originid

Where:

recordid
The ID of the record.

face
The file address compute program (FACE) record type.

ordnum
The ordinal number.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: An error occurred while trying to find this record in FACE.

System Action: Recoup phase 1 is continued.

User Response: Do the following:

  1. Determine the cause of this error.
  2. Ignore the error or correct it and selectively recoup this record at the end of recoup phase 1.

See TPF Database Reference for more information about recoup functions and procedures.

RECP005AIRESTARTING IN SSU ssu originid

Where:

ssu
The subsystem user (SSU) name.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is the response to a recoup phase 1 RESTART message in a multiple database function (MDBF) environment.

System Action: Recoup phase 1 is continued.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP005CWUNABLE TO FIND CORRECT SSU FOR RESTART originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In an MDBF environment). One of the following errors occurred:

System Action: Phase 1 is continued or on an SEL ID error recoup phase 1 is exited.

User Response: Do one of the following:

See TPF Database Reference for more information about recoup functions and procedures.

RECP005EIRESTARTING IN PRIME SSU originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This message is the response to a recoup phase 1 restart message in a multiple database function (MDBF) environment.

System Action: Phase 1 is continued.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0060EINVALID INFO UNABLE TO PROC BKD originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In an MDBF environment). Recoup phase 1 is unable to read one of its descriptor records.

System Action: Recoup phase 1 is exited.

User Response: Do the following:

  1. Determine the cause of the problem in the descriptor record.
  2. Correct the problem.
  3. Start recoup phase 1 again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0061ETO recordid -- recordaddr -- originid

Where:

recordid
The ID of the record.

recordaddr
The address of the record.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This record exceeded the processing time allowed for its chain-chase processing.

System Action: Recoup phase 1 is continued.

User Response: Do the following:

  1. Determine the cause of this error.
  2. Ignore the error or correct it and selectively recoup this record at the end of recoup phase 1.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0064ESS NOT AVAIL VIA SSUT FOR PROC originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In an MDBF environment). Recoup phase 1 is unable to set a correct response from the subsystem user table.

System Action: Recoup phase 1 is exited.

User Response:

  1. Determine the cause of the problem with the BSSU segment or the subsystem user table.
  2. Correct the problem.
  3. Start recoup phase 1 again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0066EINVALID SS/SSU NAME IN BSSU originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In an MDBF environment). Recoup phase 1 is unable to get a correct response from the subsystem user table.

System Action: Recoup phase 1 is exited.

User Response:

  1. Determine the cause of the problem with the BSSU segment or the subsystem user table.
  2. Correct the problem.
  3. Start recoup phase 1 again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0068IRECOUP ABORT IN PROGRESS originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal response to the ZRECP ABORT command.

System Action: Recoup processing ends.

User Response: None.

See TPF Operations for more information about the ZRECP ABORT command.

RECP0070EINPUT MESSAGE PROCESSOR ID INVALID originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In a loosely coupled environment). When entering the ZRECP PRIM command, the primary processor ID (PID) specified is not valid.

System Action: The recoup function is continued.

User Response: Do the following:

  1. Determine the correct processor ID (PID).
  2. Enter the command again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0072EPHASE 1 MUST BE PAUSED OR ACTIVE PROCESSOR DOWN originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In a loosely coupled environment). When entering ZRECP PRIM x MOVE, the recoup function was not paused and the active processor is not down.

System Action: The recoup function is continued.

User Response: Do the following:

  1. Pause the recoup function.
  2. Enter the command again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0074EREQUESTED PROCESSOR NOT ACTIVE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In a loosely coupled environment). The recoup function is trying to step to a processor that is not active.

System Action: The entry is exited.

User Response: Enter ZRECP PRIM x MOVE again and specify the correct processor.

See TPF Operations for more information about the recoup function and for more information about the ZRECP PRIM command.

RECP0076EFACE ERROR CALCULATING KEYPOINT ADDRESS originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In a loosely coupled environment). The BKP0 program was unable to access the recoup keypoint record.

System Action: The entry that is causing this error is exited.

User Response: Do the following:

  1. Correct the error.
  2. Enter the command again.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0077Etype/ordnum FACE ERROR-NOT LOADED.

Where:

type
An 8 character fixed-file record type.

ordnum
The decimal ordinal number.

Explanation: During processing of the BKD tape, the file address compute program (FACE) program was unable to calculate the disk address of a descriptor container record.

System Action: The record is bypassed and the load function is continued.

User Response: Do the following:

  1. Make sure a correctly formatted BKD tape was created and mounted.
  2. Make sure no other online segment opened the BKD tape.
  3. Enter ZRECP LOAD ALL to activate the descriptor load function.

See TPF Operations for more information about the recoup function and the ZRECP LOAD command.

RECP0078IINPUT NOT FROM PRIMARY/ACTIVE PROCESSOR(S) originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A ZRECP command was entered on a processor that is not being used in recoup processing.

System Action: The command fails.

User Response: Do one of the following:

See TPF Database Reference for more information about recoup functions and procedures.

RECP0079EBKD TAPE IS NO LONGER SUPPORTED

Explanation: The ZRECP LOAD command was entered, but is no longer supported.

System Action: The command is rejected.

User Response: None.

RECP007AEWRITE TAPE MARKS ON RCP AND DISMOUNT IT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In a loosely coupled environment). During a primary processor move, when the active processor is down, this message is to ensure that the RCP is closed out properly.

System Action: The recoup function is continued.

User Response: Write the tape marks on RCP and save it for recoup phase 2 use.

See TPF Database Reference for more information about recoup functions and procedures.

RECP007CEDISMOUNT RCI TAPE FROM OTHER PROCESSOR originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In a loosely coupled environment). On a primary processor move, if the RCI tape was mounted in the other processor, it must be dismounted.

System Action: The recoup function is continued.

User Response: Dismount the RCI tape.

See TPF Database Reference for more information about recoup functions and procedures.

RECP007EISTEPPING TO NEXT PROCESSORS originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In a loosely coupled environment) Recoup phase 1 chain chasing for processor-unique records exists and the recoup function is stepping to the next processor to begin processing there.

System Action: The recoup function is continued.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0080IRECOUP STARTING IN SECONDARY PROCESSOR originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: In a loosely coupled environment, recoup phase 1 chain chase processing for processor-unique records is beginning in the secondary processor.

System Action: Recoup processing continues.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0082ISTARTING AGAIN IN PRIMARY PROCESSOR originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP PRIM cpuid MOVE command was entered and recoup begins chain-chasing on the specified primary processor.

System Action: Chain-chasing continues on the specified primary processor.

User Response: None.

RECP0084AUNABLE TO INHIBIT CYCLE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: (In a loosely coupled environment). During recoup start processing, the recoup function was unable to inhibit system state cycling during directory capture.

System Action: Recoup is exited.

User Response: Do the following:

  1. Correct the problem, which is usually caused by the processors not being in the correct states.
  2. Start the recoup function again by entering the ZRECP START command.

See TPF Operations for more information about the ZRECP START command. See TPF Database Reference for more information about recoup functions and procedures.

RECP0086AV. F. A. FILE ERROR (PHASE 1 ONLY) originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The attempt to file virtual file access (VFA) buffers at the start of recoup phase 1 has failed.

System Action: Recoup is exited.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Start recoup again from the start of phase 1.

See TPF Database Reference for more information about recoup functions and procedures.

RECP0088IRECOUP CHAIN CHASE BEGINS originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is a normal response to the ZRECP RECALL command indicating that recoup chain chase processing has started.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP RECALL command.

RECP008AACYCLE ALL OTHER PROCESSORS TO 1052 STATE, ABORT RECOUP AND START RECOUP AGAIN originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP START command was entered with the PROC parameter specified, but the primary recoup processor is in 1052 state and this processor is not.

System Action: The command fails.

User Response: Do the following:

  1. Cycle all secondary recoup processors to 1052 state.
  2. Enter ZRECP ABORT to end recoup.
  3. Run recoup again.

See TPF Operations for more information about the ZRECP START and ZRECP ABORT commands.

RECP0096IMULTIPROCESSOR RECOUP RUN HAS BEEN DISALLOWED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP RECALL command was entered, but an error condition was detected during initialization processing while trying to find or file a multiprocessor recoup keypoint (#MPRECP) record.

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Start recoup processing again.

See TPF Operations for more information about the ZRECP RECALL command.

RECP0099WRANGE ERROR

Explanation: An internal error occured during recoup processing. An attempt was made to use an equate branch value that is not valid.

System Action: Recoup processing continues.

User Response: See your IBM service representative.

RECP0099IGLOBALS AND FUNCTION SWITCH RESET IN THIS PROCESSOR

Explanation: (In a loosely coupled environment). This message denotes that recoup phase 1 was aborted or recoup phase 3 was completed in the primary processor. This message will appear on all active processors containing the subsystem being recouped. It ensures that all recoup switches and globals were reset in all processors.

System Action: The recoup function is continued.

User Response: None.

See TPF Database Reference for more information about recoup functions and procedures.

RECP009AEFACE ERROR ON A MULTIPLE-PROCESSOR RECOUP KEYPOINT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP RECALL command was entered, but recoup was unable to calculate the file address of a processor-unique keypoint record.

System Action: Recoup processing ends abnormally.

User Response:

  1. Determine the cause of the problem. (Perhaps a bad FCTB was loaded.)
  2. Correct the problem.
  3. Start recoup processing again.

See TPF Operations for more information about the ZRECP RECALL command.

RECP009CEUNABLE TO FIND MULTIPLE-PROCESSOR RECOUP KEYPOINT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP RECALL command was entered, but recoup was unable to find a processor-unique keypoint record

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. Start recoup processing again.

See TPF Operations for more information about the ZRECP RECALL command.

RECP00A0EERROR FILE-ING MULTIPLE-PROCESSOR RECOUP KEYPOINT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP RECALL command was entered, but a file error occurred during initialization when attempting to file a multiprocessor recoup keypoint (#MPRECP) record.

System Action: Recoup continues but running chain chasing on multiple processors will not be allowed.

User Response:

  1. Determine the cause of the problem.
  2. Correct the problem.

See TPF Operations for more information about the ZRECP RECALL command.

RECP00A2IINCORRECT ENTRY WHILE A MULTIPLE-PROCESSOR RECOUP RUN IS ACTIVE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A ZRECP PRIM command was entered while a multiprocessor recoup chain chase was active.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZRECP PRIM command.

RECP00A4IINCORRECT ENTRY WHENEVER ZRECP PRIM ENTRY HAS BEEN ENTERED BEFORE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP PRIM command was entered while a multiprocessor recoup chain chase was active

System Action: The ZRECP message is rejected.

User Response: None.

See TPF Operations for more information about the ZRECP PRIM command.

RECP00A6IZRECP PROC cpuid START COMPLETE originid

Where:

cpuid
The name of the processor.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: This is the normal response to the ZRECP START command specifying the PROC parameter.

System Action: Multiprocessor chain chase begins on the target processor

User Response: None.

See TPF Operations for more information about the ZRECP START command.

RECP00A8IINCORRECT ENTRY - REQUESTED PROCESSOR EITHER STARTED/STOPPED/COMPLETED WORK originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP START command with the PROC parameter specified was entered for a target processor that has completed chain chase processing or has been forced to stop or exit.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZRECP START command.

RECP00AAEINCORRECT RETRIEVAL OF MULTI-PROCESSOR RECOUP KEYPOINT originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation:

System Action: None.

User Response: None.

RECP00ACEERROR UPDATING THE RECOUP KEYPOINT IN PRIMARY/ACTIVE PROCESSOR originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: During recoup processing, a secondary processor tried to update the primary processor keypoint but the status in the processor ID shows the primary processor to be no longer active.

Note:
The primary processor must always be active during a recoup.

System Action: Recoup processing continues

User Response: Abort recoup.

RECP00AEARECOUP RUN ABORTED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: An error occurred during multiprocessor recoup processing that caused a secondary processor, which was active, to end recoup abnormally.

System Action: Recoup processing ends abnormally on the secondary processor.

User Response: Enter the ZRECP EXIT command with the PROC parameter specified to allow recoup processing to continue on the primary processor.

See TPF Operations for more information about the ZRECP EXIT command.

RECP00B0TRECOUP RUN COMPLETED originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup successfully completed running on a secondary processor and all entry control blocks (ECBs) are exited.

System Action: None.

User Response: None.

RECP00B2WRECOUP FIXED ERRORS OCCURRED ON THIS RUN originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: Recoup chain chasing on this secondary processor found fixed errors.

System Action: Recoup is completing.

User Response: Ensure that all fixed errors are reprocessed on the primary processor at the end of recoup phase 1.

RECP00B4AOPERATOR REQUIRED TO EXIT RECOUP RUN FROM ABORTED PROCESSOR IN ORDER TO FINISH PHASE-I originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: During multiprocessor recoup, processing has ended abnormally on a secondary processor and operator intervention is required for processing to continue on the primary processor.

System Action: None.

User Response: Enter the ZRECP EXIT command with the PROC parameter specified to allow recoup to continue on the primary processor.

See TPF Operations for more information about the ZRECP EXIT command.

RECP00B6EENTRY VALID ONLY WHEN CHAIN-CHASE IN PROGRESS originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A ZRECP command specifying the PROC parameter was entered at the wrong time.

System Action: The command is rejected.

User Response: None.

RECP00B8IINCORRECT ENTRY, REQUESTED PROCESSOR SHOWS NO ACTIVE RECOUP originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A ZRECP command specifying the PROC parameter was entered for a target processor but the target processor is not performing a chain chase

System Action: The command is rejected.

User Response: None.

RECP00BAIINCORRECT ENTRY, REQUESTED PROCESSOR IS THE PRIMARY/ACTIVE PROCESSOR. originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A ZRECP command was entered specifying the PROC parameter for a processor which is currently the primary processor.

System Action: The command is rejected.

User Response: None.

RECP00BCIINCORRECT REQUEST, MULTIPROCESSOR OPTION NOT ACTIVE originid

Where:

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: A ZRECP command was entered specifying the PROC parameter for a target processor but the target processor is not performing a chain chase.

System Action: The command is rejected.

User Response: None.

RECP00BEIZRECP PROC cpuid STOP COMPLETE originid

Where:

cpuid
The name of the processor.

originid
The processor ID of the originating processor. This is appended to the message only if the message was originally generated on a different processor.

Explanation: The ZRECP STOP command was entered specifying the PROC parameter for a target processor.

System Action: The target processor will stop performing chain chase

User Response: None.