gtpm5m2bMessages (Online)

RECP00C0I-RECP0400E

RECP00C0IZRECP PROC cpuid EXIT 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 a normal response to the ZRECP EXIT command specifying the PROC parameter for a target processor.

System Action: None.

User Response: None.

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

RECP00C2IINCORRECT ENTRY - REQUESTED PROCESSOR EITHER STOPPED/EXITED/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 STOP or ZRECP EXIT command was entered specifying the PROC parameter for a target processor but the target processor has already completed chain chasing, or it has been previously stopped or exited.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZRECP STOP and ZRECP EXIT commands.

RECP00C4IZRECP PROC cpuid RESTART 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 RESTART command specifying the PROC parameter.

System Action: None.

User Response: None.

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

RECP00C6IINCORRECT TO START PROCESSOR ORDINAL 0, WHEN THE PRIMARY PROCESSOR IS > 0 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 specifying the PROC parameter but the specified processor was the first processor in the loosely-coupled complex and cannot be chosen to be a secondary processor.

System Action: The command is rejected.

User Response: Do one of the following:

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

RECP00C8EERROR - DUPLICATE ID'S AND VERSION NUMBERS FOUND, CONTACT PROGRAMMER. 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:

Explanation: The ZRECP START command was entered, but there is more than one record ID with the same ID in the set of recoup descriptors.

Note:
Recoup requires that whenever two or more descriptors (meaning GROUP ID=XX,USE=BASE) are loaded with the same ID, then the VER= parameter on the GROUP macro (only when USE=BASE coded) must be used to distinguish one ID from another.

System Action: Recoup processing ends abnormally.

User Response: Do the following:

See TPF Operations for more information about the ZRECP START command. See TPF System Macros for more information about the GROUP macro.

RECP00CAEINCORRECT ENTRY, MULTIPROCESSOR RECOUP HAS 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: The ZRECP START command was entered specifying the PROC parameter for a target processor, but multiprocessor recoup as already completed.

System Action: The command is rejected.

User Response: None.

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

RECP00CCWUNPROCESSED RECORD IDS WILL NOW BE PROCESSED 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: Segment B1BK has detected that some record IDs did not complete processing at the end of traditional recoup. The B1BK segment will chain chase these records.

System Action: Recoup processing continues.

User Response: Determine why some record IDs did not complete chain chasing. Primary causes could be that a descriptor with CPUID=X was coded but that processor was not active, or IDCOMP= was coded which conflicted with another descriptor's IDCOMP=. Recoup will still perform the chain chase of these descriptors as a necessary safety precaution.

RECP00CEIRECOUP RUN STOPPED IN THIS 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: This is a normal response to the ZRECP STOP command specifying the PROC parameter indicating that the target processor has stopped all chain chasing.

System Action: None.

User Response: None.

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

RECP00D0IRECOUP RUN EXITED FROM THIS 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: This is a normal response to the ZRECP EXIT command specifying the PROC parameter indicating that the target processor has exited all recoup activity.

System Action: None.

User Response: None.

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

RECP00D2IPSEUDO DIRECTORY INIT 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 phase 1 processing indicating that recoup pseudo directory initialization has started on this processor.

System Action: Recoup processing continues.

User Response: None.

RECP00D4IPSEUDO DIRECTORY INIT 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 a normal message during recoup phase 1 processing indicating that recoup pseudo directory initialization has completed on this processor.

System Action: Recoup processing continues.

User Response: None.

RECP00D6EUNABLE TO FIND THE DESCRIPTOR 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 processing was unable to find a descriptor segment that was scheduled for chain chase processing.

System Action: Recoup processing ends without completing.

User Response: None.

RECP00DAECANNOT START RECOUP ON EXITED 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 START command was entered specifying the PROC parameter with the processor that was previously exited by entering the ZRECP EXIT command specifying the PROC parameter.

System Action: The command is rejected.

User Response: None.

See TPF Operations for more information about the ZRECP STOP and ZRECP EXIT commands.

RECP00DCIREQUESTED PROCESSOR ALREADY EXITED FROM 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: A ZRECP command was entered specifying the PROC parameter with the processor that had already been previously exited by entering the ZRECP EXIT command specifying the PROC parameter.

System Action: The command is rejected.

User Response: None.

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

RECP00DEISTOP ISSUED AND WILL TAKE EFFECT WHEN ALL ECBS ARE COMPLETE. IF THIS TAKES TOO LONG, ISSUE STOP 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 STOP command was entered specifying the PROC parameter for a target processor but all ECBs have not completed.

System Action: All recoup chain chase activity stops on the specified processor when the chain chasing of the current file ends. Message RECP00CEI should follow in a few seconds to indicate that the target processor has been stopped.

User Response: If chain chasing does not stop on the specified processor in a few seconds, enter the ZRECP STOP command specifying the PROC parameter for the target processor again.

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

RECP00E0IID COUNTS RESTORED BACK TO TPF STATUS IF TPFDF RECOUP IS RUNNING, OTHERWISE THE COUNTS ARE CLEARED 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 EXIT command was entered specifying the PROC parameter for a target processor and the ID counts for the processor are reset to their beginning recoup values or the ID counts are cleared.

System Action: None.

User Response: None.

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

RECP00E2EFIND/FACE ERROR ON ID COUNTS RECORD. TPF RECOUP COUNTS NOT RESTORED CORRECTLY 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 EXIT command was entered specifying the PROC parameter but an error occurred while restoring the ID counts record of the specified processor.

System Action: The command stops restoring the ID counts record but recoup processing continues. When recoup ends, the ID counts for the specified processor will not be correct.

User Response: If the recoup run is not critical, do the following:

  1. Enter ZRECP ABORT to end recoup.
  2. Determine the cause of the problem.
  3. Correct the problem.
  4. Start the entire recoup run again.

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

RECP00E4IPSEUDO DIRECTORY MERGE 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 a normal message, during recoup processing, indicating that a set of recoup pseudo directories has been merged with the processor-unique master copy.

System Action: Recoup processing continues.

User Response: None.

RECP00E6ITPF RECOUP ID COUNTS COPIED TO SAVEAREA 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, when TPF recoup ends chain chasing and before TPFDF recoup begins, indicating that the ID counts records have been saved.

System Action: None.

User Response: None.

RECP00E8EERROR - TPF RECOUP ID COUNTS NOT COPIED 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: TPF recoup has completed but the ID counts records were not saved. If the ZRECP EXIT command is entered before TPFDF recoup ends on this processor, ID counts will be incorrect.

System Action: Recoup processing continues.

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

User Response: Determine the cause of the error.

RECP00EAATARGET CPU STILL PERFORMING CHAIN CHASE. ENTER ZRECP PROC X STOP OR RE-IPL THE CPU 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 EXIT command was entered specifying the PROC parameter for a processor that was still performing chain chase.

System Action: The command is rejected.

User Response: Enter the ZRECP STOP command specifying the PROC parameter before entering the ZRECP EXIT command specifying the PROC parameter.

See TPF Operations for more information about the ZRECP STOP and ZRECP EXIT commands.

RECP00ECTPSEUDO DIRECTORY CHECKS FAILED. SEE 41210 SNAP DUMP. RECOUP IS ABORTING 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 processor-unique recoup pseudo directories have been corrupted or were not filed out correctly from virtual file access (VFA) and an older, incorrect copy of them is being used. This can be the result of a hard-IPL with a loss of whatever delay-file records were in VFA.

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 again.

RECP00EEWPSEUDO DIRECTORY INTEGRITY COUNTS ADJUSTED. WERE WITHIN PROPER THRESHOLD 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 count of pools chain chased is lower or slightly higher than the count of pools found to be in use by recoup (according to the recoup pseudo directories). This condition is usually caused by an IPL of the TPF system.

System Action: Recoup processing continues.

User Response: If this was not caused by an IPL, contact a system programmer.

RECP00F0IPSEUDO DIRECTORY MERGE 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 a set of recoup pseudo directories has started to be merged with the processor-unique master copy.

System Action: None.

User Response: None.

RECP00F2IPSEUDO DIRECTORY COPY 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 a set of recoup pseudo directories has started to be copied into another set.

System Action: None.

User Response: None.

RECP00F4IPSEUDO DIRECTORY COPY 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 a normal message, during recoup processing, indicating that a set of recoup pseudo directories has been copied into another set.

System Action: Recoup processing continues.

User Response: None.

RECP00F6IPSEUDO DIRECTORY VERIFY 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 a set of recoup pseudo directories has started to be verified.

System Action: Recoup processing continues.

User Response: None.

RECP00F8IPSEUDO DIRECTORY VERIFY 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 a normal message, during recoup processing, indicating that a set of recoup pseudo directories has been verified.

System Action: Recoup processing continues.

User Response: None.

RECP00FAIPSEUDO DIRECTORY FLUSH 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 a set of recoup pseudo-directories has started to be flushed from virtual file access (VFA).

System Action: Recoup processing continues.

User Response: None.

RECP00FCIPSEUDO DIRECTORY FLUSH 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 a normal message, during recoup processing, indicating that a set of recoup pseudo-directories has been flushed from virtual file access (VFA).

System Action: Recoup processing continues.

User Response: None.

RECP00FEIPHASE 2 START 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 RECALL command, indicating that recoup phase 2 is starting.

System Action: Recoup phase 2 starts.

User Response: None.

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

RECP0300IRECP WAITING FOR PROC cpuid TO FINISH chasetype

Where:

cpuid
The name of the processor.

chasetype
The type of recoup chain chase processing (TPF for TPF, or PH-1 for TPFDF).

Explanation: This is a normal message from the primary processor during multiprocessor recoup processing indicating the TPF or TPFDF recoup status on another processor.

System Action: None.

User Response: None.

RECP0300ESONRPE RECORD INITIALIZATION INCOMPLETE

Explanation: The ZRECP RESTART command was entered, but the recoup pseudo directory (#SONRPE) record could not be initialized.

System Action: Recoup processing ends abnormally.

User Response: Start recoup processing again, from the beginning.

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

RECP0301EECB/ORDINAL TABLE RESTART INCOMPLETE

Explanation: The ZRECP RESTART command was entered specifying the PROC parameter but a FACE-type, find, or wait error condition was detected while trying to retrieve the ordinal backup table.

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 RESTART command again.

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

RECP0301ITPF RECOUP COMPLETED ON CPU- cpuids.

Where:

cpuids
The name of the processor or processors.

Explanation: This is a normal message indicating that TPF recoup chain chase processing has completed on the specified processor or processors.

System Action: Recoup processing continues.

User Response: None.

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

RECP0302EBRR5 - INCORRECT PROFILE OPTION

Explanation: The ZRECP PROFILE command was entered incorrectly.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter ZRECP PROFILE HELP to see all of the parameters that are allowed.
  2. Enter the ZRECP PROFILE command again using correct parameters.

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

RECP0303WVFA DELAYED FILES DISABLED BY OPERATOR

Explanation: During recoup initialization of pseudo directories, virtual file access (VFA) was disabled by the operator.

System Action: Recoup processing continues.

User Response: None.

RECP0304WVFA DELAYED FILES DISABLED BY SYSTEM

Explanation: During recoup initialization of pseudo directories, virtual file access (VFA) was disabled by the operator.

System Action: Recoup processing continues.

User Response: None.

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

RECP0305WRECOUP ECB LEVEL PAUSED

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

System Action: Recoup processing is paused.

User Response: Enter the ZRECP LEVEL command to continue with recoup processing.

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

RECP0306WZRECP SEL WAS IN PROGRESS PRIOR TO IPL

Explanation: The ZRECP RESTART command was entered following a system IPL, but selective recoup processing was occurring at the time of the IPL.

System Action: None.

User Response: Enter the ZRECP SEL command again to start selective recoup processing again.

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

RECP0307ARE-ENTER PREVIOUS ZRECP SEL ENTRY TWICE IN ORDER TO PROCESS THAT FILE ADDRESS AGAIN

Explanation: The ZRECP RESTART command was entered following a TPF system IPL, but selective recoup processing was occurring at the time of the IPL.

System Action: None.

User Response: Enter the ZRECP SEL command again to start selective recoup processing again.

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

RECP0308IPHASE 2 RESTART

Explanation: This is the normal response to the ZRECP RESTART command if recoup was in phase 2 when recoup stopped.

System Action: Recoup phase 2 starts again.

User Response: None.

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

RECP0310WVFA DELAYED FILES DISABLED BY 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: During recoup processing, keypoint B indicator does not show virtual file access (VFA) delayed files to be functionally disabled, yet they are.

System Action: Processing continues.

User Response: None.

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

RECP0311IRESTART BEING INITIATED 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 RESTART command specifying the PROC parameter.

System Action: Recoup processing continues.

User Response: None.

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

RECP0312AMOUNT RCP TAPE 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: Recoup phase 1 is ready to process and there is no RCP tape mounted.

System Action: Recoup processing waits until the RCP tape is mounted.

User Response: Mount an RCP tape.

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

RECP0313WRECOUP ECB LEVEL PAUSED 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 processing has internally paused after determining that virtual file access (VFA) delayed files have been disabled either by an operator or by the TPF system.

System Action: Recoup processing pauses.

User Response: Do the following:

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

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

RECP0314EUNABLE TO DO RESTART PROCESS 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 RESTART command was entered specifying the PROC parameter but an error switch was passed to the B0SH segment indicating that a temporary keypoint could not be built

System Action: The command fails.

User Response: Do the following:

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

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

RECP0315IRECOUP RESTARTED 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 RESTART command.

System Action: Recoup processing continues.

User Response: None.

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

RECP0316ERECOUP ALREADY ACTIVE THIS 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 RESTART command was entered specifying the PROC parameter but recoup is already be active on the specified processor.

System Action: The command is rejected.

User Response: None.

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

RECP0319WVFA DELAYED FILES DISABLED BY OPERATOR 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, keypoint B was found to have an indicator set showing that virtual file access (VFA) delayed files have been functionally disabled.

System Action: Recoup processing continues.

User Response: None.

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

RECP0361EBEWA - NO PARM LIST FOUND ON LEVEL 8

Explanation: The ZRECP ONEL command was entered, but an error condition was detected because the BEWA segment was called without a core block on level 8.

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 ONEL command again.

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

RECP0362IBEWA - ONLINE ERROR LOG - NOT ACTIVE

Explanation: This is a normal response to the ZRECP ONEL command specifying the STA parameter indicating that online error logging is not active.

System Action: None.

User Response: None, if you do not want online error logging active, or enter ZRECP ELOG ON to make online error logging active.

See TPF Operations for more information about the ZRECP ONEL and ZRECP ELOG commands.

RECP0363IBEWA - ONLINE ERROR LOG - ACTIVE

Explanation: This is a normal response to the ZRECP ONEL command specifying the STA parameter indicating that online error logging is active.

System Action: None.

User Response: None, if you want online error logging active, or enter ZRECP ELOG OFF to make online error logging inactive.

See TPF Operations for more information about the ZRECP ONEL and ZRECP ELOG commands.

RECP0364EBEWA - INCORRECT DISPLAY REQUEST - CHECK INPUT

Explanation: The ZRECP ONEL command was entered incorrectly.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the correct format of the command.
  2. Enter the ZRECP ONEL command again using the correct format.

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

RECP0365EBEWA - INCORRECT FORMAT - MISSING RUN NUMBER

Explanation: The ZRECP ONEL command was entered incorrectly.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the correct format of the command.
  2. Enter the ZRECP ONEL command again using the correct format.

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

RECP0366EBEWA - INCORRECT PARAMETER REQUEST

Explanation: The ZRECP ONEL command was entered incorrectly.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the correct format of the command.
  2. Enter the ZRECP ONEL command again using the correct format.

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

RECP0371EBEWB - ERROR ON ADD TO ONLINE ERROR LOG

Explanation: Recoup processing was trying to display errors found during chain chase processing or the ZRECP ONEL command was entered, but an error condition was detected when the BEWB segment issued a TPFDF DBADD macro and was unable to add a logical record (LREC) to the online error log.

System Action: Chain chase processing errors cannot be displayed and the error log is closed.

User Response: Do the following:

  1. Extract data from the RCP tape because the online error log for this recoup run is not correct.
  2. Enter ZRECP ELOG OFF to turn off the online error log.
  3. Advise a system programmer of the problem.

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

RECP0372EBEWB - I/O ERROR FOUND

Explanation: Recoup processing was trying to display errors found during chain chase processing or the ZRECP ONEL command was entered, but an I/O error condition was detected when the BEWB segment attempted to initialize an online error log set (both LREC and detail files).

System Action: Chain chase processing errors cannot be displayed.

User Response: Do the following:

  1. Extract data from the RCP tape because the online error log for this recoup run is not correct.
  2. Enter ZRECP ELOG OFF to turn off the online error log.
  3. Advise a system programmer of the problem.

See TPF Operations for more information about the ZRECP ONEL and ZRECP ELOG commands.

RECP0373EBEWB - INCORRECT ALG OR ITEM NOT FOUND

Explanation: Recoup processing was trying to display errors found during chain chase processing or the ZRECP ONEL command was entered, but an error condition was detected when the BEWB segment tried to find an algorithm or an item.

System Action: Chain chase processing errors cannot be displayed.

User Response: Do the following:

  1. Extract data from the RCP tape because the online error log for this recoup run is not correct.
  2. Enter ZRECP ELOG OFF to turn off the online error log.
  3. Advise a system programmer of the problem.

See TPF Operations for more information about the ZRECP ONEL and ZRECP ELOG commands.

RECP0374EBEWB - FACE ERROR FOUND

Explanation: Recoup processing was trying to display errors found during chain chase processing or the ZRECP ONEL command was entered, but an error condition was detected by a FACE-type call when the BEWB segment tried to initialize an online error log set (both LREC and detail files).

System Action: Chain chase processing errors cannot be displayed.

User Response: Do the following:

  1. Extract data from the RCP tape because the online error log for this recoup run is not correct.
  2. Enter ZRECP ELOG OFF to turn off the online error log.
  3. Advise a system programmer of the problem.

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

RECP0375EBEWB - ERROR ON DELETE

Explanation: Recoup processing was trying to display errors found during chain chase processing or the ZRECP ONEL command was entered, but an unspecified error condition was detected when the BEWB segment tried to initialize an online error log set (both LREC and detail files).

System Action: Chain chase processing errors cannot be displayed.

User Response: Do the following:

  1. Extract data from the RCP tape because the online error log for this recoup run is not correct.
  2. Enter ZRECP ELOG OFF to turn off the online error log.
  3. Advise a system programmer of the problem.

See TPF Operations for more information about the ZRECP ONEL and ZRECP ELOG commands.

RECP0376EBEWB - ERROR ADDING INDEX DATE LREC

Explanation: Recoup processing was trying to display errors found during chain chase processing or the ZRECP ONEL command was entered, but an error condition was detected when the BEWB segment tried to add (using the TPFDF DBADD macro) the first LREC to a newly initialized set of online error logs.

System Action: Chain chase processing errors cannot be displayed.

User Response: Do the following:

  1. Extract data from the RCP tape because the online error log for this recoup run is not correct.
  2. Enter ZRECP ELOG OFF to turn off the online error log.
  3. Advise a system programmer of the problem.

See TPF Operations for more information about the ZRECP ONEL and ZRECP ELOG commands.

RECP0377IBEWB - DUMP UTILITY PROCESSING COMPLETED

Explanation: This is a normal message during recoup processing indicating that errors found during recoup chain chase processing have been written to RCP tape.

System Action: None.

User Response: None.

RECP0378EBEWB - INCORRECT PARAMETER REQUEST

Explanation: The ZRECP ONEL command was entered, but the BEWB segment was passed an unsupported keyword.

System Action: The command is rejected.

User Response: Contact a system programmer.

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

RECP0379IBEWB - NO MATCHING DATA FOUND

Explanation: This is a normal response to the ZRECP ONEL command specifying the ERR parameter when no errors are found for the specified error type.

System Action: None.

User Response: None.

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

RECP0381EBEWG - BAD KEYWORD FOUND - keywerr

Where:

keywerr
is the keyword parameter value that is incorrect.

Explanation: The ZRECP ONEL command was entered specifying an incorrect parameter.

System Action: The command is rejected.

User Response: Do the following:

  1. Determine the correct format of the command.
  2. Enter the ZRECP ONEL command again using the correct format.

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

RECP0382EBEWG - INCORRECT ERR- VALUE ENTERED - keywerr

Where:

keywerr
is the keyword parameter value that is incorrect.

Explanation: The ZRECP ONEL command was entered specifying an incorrect value with the ERR parameter.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter ZRECP ONEL HELP to display error types collected for the online error log.
  2. Enter the ZRECP ONEL command again specifying a correct error type.

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

RECP0383EBEWG - INCORRECT RUN- VALUE

Explanation: The ZRECP ONEL command was entered specifying an incorrect value with the RUN parameter.

System Action: The command is rejected.

User Response: Enter the ZRECP ONEL command again specifying a correct RUN parameter value.

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

RECP0384EBEWG - INCORRECT RID- ridnum

Where:

ridnum
is the RID parameter value that is incorrect.

Explanation: The ZRECP ONEL command was entered specifying an incorrect value with the RID parameter.

System Action: The command is rejected.

User Response: Enter the ZRECP ONEL command again specifying a correct RID parameter value.

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

RECP0385EBEWG - INCORRECT EID- STRING excludedids MAX OF 4 EID ITEMS ALLOWED

Explanation: The ZRECP ONEL command was entered specifying an incorrect record ID with the EID parameter.

System Action: The command is rejected.

User Response: Enter the ZRECP ONEL command again specifying a correct EID parameter value.

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

RECP0386EBEWG - INCORRECT EID- STRING excludedids

Where:

excludedids
is the string of excluded IDs that was entered with the EID parameter.

Explanation: The ZRECP ONEL command was entered specifying too many record IDs with the EID parameter. A maximum of 4 record IDs are allowed.

System Action: The command is rejected.

User Response: Enter the ZRECP ONEL command again specifying 4 or less IDs with the EID parameter.

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

RECP0387EBEWG - INCORRECT EID COUNT- STRING excludedids

Where:

excludedids
is the string of excluded IDs that was entered with the EID parameter.

Explanation: The ZRECP ONEL command was entered with the EID parameter specified but a maximum of 4 record IDs are allowed in requesting a display of the online error log by exclusion.

System Action: The command is rejected.

User Response: Enter the ZRECP ONEL command again specifying 4 or less IDs with

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

RECP0388EBEWG - LNIATA NOT REFERENCED IN WGTA TABLE

Explanation: The ZRECP ONEL command was entered, but the LNIATA specified with the PTR parameter was incorrect.

System Action: The command is rejected.

User Response: Enter the ZRECP ONEL command again specifying a correct LNIATA address for the printer.

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

RECP0391EBEWC - NO INPUT BLK FOUND ON LEVEL 8

Explanation: The ZRECP ONEL command was entered, but the BEWC segment was called without a core block on level 8. A parameter list is expected on that level.

System Action: None.

User Response: None.

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

RECP0392EBEWC - FATAL ERROR ON READ OF INDEX

Explanation: The ZRECP ONEL command was entered, but an error condition was detected by the DFRED macro while trying to read an index record using the index keylist for the online error log (SRHH1P). The index structure for the online error log was built incorrectly.

System Action: The command fails.

User Response: Do the following:

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

RECP0393EBEWC - INCORRECT ERROR INDI FOUND

Explanation: The ZRECP ONEL command was entered, but an incorrect error indicator was detected by the BEWC segment while trying to read the online error log (SRHH1P) to get a count of the error types.

System Action: Continues processing.

User Response: None.

RECP0394EBEWC - INCORRECT LOG PARAMETER

Explanation: The BEWC segment was internally passed a parameter that is not supported.

System Action: The function call is rejected.

User Response: See your IBM service representative.

RECP0395IONLINE ERROR LOG DISPLAY FOR ddmon

Where:

ddmon
The current day and month.

Explanation: This is the normal response to the ZRECP ONEL command with the REC-SUM parameter specified. This is followed by a display containing the summary of the total error counts by record ID.

System Action: None.

User Response: None.

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

RECP0396EBEWC - ENTRY NOT ALLOWED - POOLS NOT AVAILABLE

Explanation: The ZRECP ONEL command was entered to display all of the detail records but the TPF system is in 1052 state with no get file storage (GFS) available.

System Action: None.

User Response: If the TPF system can be cycled to NORM state, do the following:

  1. Cycle the TPF system to NORM state.
  2. Enter the ZRECP ONEL command again.

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

RECP0397IONLINE ERROR LOG DISPLAY FOR ddmon

Where:

ddmon
The current day and month.

Explanation: This is the normal response to the ZRECP ONEL command with the REC-ALL parameter specified. This is followed by a display containing the details of all the individual errors.

System Action: None.

User Response: None.

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

RECP0400EBEWD - NO INPUT BLK FOUND ON LEVEL 8

Explanation: The ZRECP ONEL command was entered, but an error condition was detected when the BEWD segment was called without a core block on level 8. A parameter list is expected on that level.

System Action: None.

User Response: None.

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