gtpm5m2cMessages (Online)

RECP0401E-RECP0798E

RECP0401EBEWD - ERROR ON READ OF FIRST INDEX

Explanation: The ZRECP ONEL command was entered with the LOG parameter specified, but an error occured while trying to access the first entry in the online error log (SRHH1P) file.

System Action: The command fails.

User Response: Do the following:

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

RECP0402EBEWD - ERROR ON READ OF NEXT INDEX

Explanation: The ZRECP ONEL command was entered with the LOG parameter specified, but an error occured while trying to access the an entry other than the first entry in the online error log (SRHH1P) file.

System Action: The command fails.

User Response: Do the following:

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

RECP0404IONLINE ERROR LOG DISPLAY FOR LOG

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

System Action: None.

User Response: None.

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

RECP0410IBEWP - EXCEEDED ONEL THRESHOLD FOR ID charid/hexid. POOL ERRORS WILL BE WRITTEN TO RCP TAPE ONLY

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.

Explanation: During recoup processing, the number of errors in the online error log (SRHH1P) has exceeded the allowed number that was set using the ZRECP PROFILE command.

System Action: Errors are written only to the RCP tape.

User Response: None.

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

RECP0411EBEWE - 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: None.

User Response: Do the following:

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

RECP0412EBEWE - FATAL ERROR ON READ OF DETAIL

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

System Action: None.

User Response: Do the following:

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

RECP0415EBEWF - ERROR TAKEN ON DISPLAY CALL

Explanation: The ZRECP ONEL command was entered, but an error An error was detected occured while trying to display the temporary file GW01SR.

System Action: The command fails.

User Response: Do the following:

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

RECP0416EBEWF - ERROR ON ADD TO DISPLAY WORK FILE

Explanation: The ZRECP ONEL command was entered, but an error condition was detected by the DFADD macro while trying to add a new logical record (LREC) to the work file mapped by GW01SR.

System Action: The command displays information that is not accurate.

User Response: Do the following:

  1. Determine the cause of the problem.
  2. Correct the problem.
  3. If the problem persists, enter ZRECP ELOG OFF to deactivate online error logging.

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

RECP0417IMSG SENT TO PRINTER

Explanation: This is the normal response to the ZRECP ONEL command with the PTR parameter specified..

System Action: None.

User Response: None.

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

RECP0418IONLINE ERROR LOG DISPLAY - NO DATA

Explanation: The ZRECP ONEL command was entered with the REC-SUM or REC-ALL parameter specified, but there is no data in the online error log because online error logging was not active for the specified recoup run.

System Action: None.

User Response: None.

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

RECP0421IRECOUP PHASE 4 CREATE CONTINUING

Explanation: This is the normal response to the ZRPDU CREATE command indicating that recoup phase 4 is still running.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRPDU CREATE command.

RECP0431IRECOUP ABORT STARTED

Explanation: This is the normal response to the ZRECP ABORT command or an internal recoup abort.

System Action: None.

User Response: None.

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

RECP0432IRECOUP ABORT IN PROGRESS

Explanation: The BRPE segment was entered to internally abort recoup but recoup is already aborting.

System Action: None.

User Response: None.

RECP0433IRECOUP PHASE 4 CREATE IS COMPLETE TOTAL LOST ADDRESSES = lacnt TOTAL ERRONEOUSLY AVAILABLE ADDRESSES = eacnt

Where:

lacnt
The total number of lost addresses (LA).

eacnt
The total number of erroneously available addresses (EA).

Explanation: This is the normal response to the ZRPDU CREATE command indicating that recoup phase 4 is completed.

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRPDU CREATE command.

RECP0434EBOF6 - FILE ERROR ON SONUP ORDINAL ordnum

Where:

ordnum
The hexadecimal ordinal number of the pool directory update (PDU) pseudo directory (#SONUP) record.

Explanation: The ZRECP PHASE4 command was entered, but an error condition was detected while trying to file the specified ordinal.

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 ZRECP PHASE4 command again.

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

RECP0435EBOF6 - FACE ERROR ON SONUP ORDINAL ordnum

Where:

ordnum
The hexadecimal ordinal number of the pool directory update (PDU) pseudo directory (#SONUP) record.

Explanation: The ZRECP PHASE4 command was entered, but an error condition was detected by a FACS-type call while trying to use the PDU pseudo directory (#SONUP) ordinal.

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 ZRECP PHASE4 command again.

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

RECP0436EBOF6 - FACE ERROR ON SONROLL ORDINAL ordnum

Where:

ordnum
The hexadecimal ordinal number of the recoup rollin directory (#SONROLL) record.

Explanation: The ZRECP PHASE4 command was entered, but an error condition was detected by a FACS-type call while trying to use the recoup rollin directory (#SONROLL) ordinal.

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 ZRECP PHASE4 command again.

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

RECP0437EBOF6 - FIND ERROR ON SONUP ORDINAL ordnum

Where:

ordnum
The hexadecimal ordinal number of the pool directory update (PDU) pseudo directory (#SONUP) record.

Explanation: The ZRECP PHASE4 command was entered, but an error condition was detected while trying to find the specified ordinal.

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 ZRECP PHASE4 command again.

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

RECP0438EBOF6 - FIND ERROR ON SONROLL ORDINAL ordnum

Where:

ordnum
The hexadecimal ordinal number of the recoup rollin directory (#SONROLL) record.

Explanation: The ZRECP PHASE4 command was entered, but an error condition was detected while trying to find the specified ordinal.

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 ZRECP PHASE4 command again.

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

RECP0500EBRR2 - INCORRECT OPTION SPECIFIED, TPFDF REQUIRED

Explanation: The ZRECP PROFILE command was entered using a parameter that requires the TPFDF product.

System Action: The command is rejected.

User Response: Enter the ZRECP PROFILE command again without any parameters that require the TPFDF product.

RECP0501EBRR2 - INCORRECT INPUT MESSAGE

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.

RECP0502EBRR5 - INCORRECT PROFILE OPTION

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

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.

RECP0503EBRR5 - NO OPTION IS SPECIFIED

Explanation: The ZRECP PROFILE command was entered without specifying a parameter.

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.

RECP0504IRECOUP OPTIONS

Explanation: This is the normal response to the ZRECP PROFILE command and this message is also displayed during recoup processing.

System Action: None.

User Response: None.

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

RECP0520IRECOUP KEYPOINT UNAVAILABLE

Explanation: The ZRECP STATUS command was entered, or an internal status request was made, but the recoup keypoint is not in main storage. This is usually because a recoup run is not active, or recoup phase 1 processing is not in progress. This can also mean that a recoup restart is required.

System Action: None.

User Response: Do the following:

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

RECP0521IPHASE 1 COMPLETED

Explanation: This is the normal response to the ZRECP STATUS command, or an internal status request, indicating that recoup phase 1 processing has completed.

System Action: None

User Response: None.

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

RECP0522IRECALL HAS NOT BEEN DONE YET

Explanation: The ZRECP STATUS command was entered, or an internal status request was made, but the ZRECP RECALL command has not been entered to recall recoup processing.

System Action: None.

User Response: None.

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

RECP0523IDIRECTORY CAPTURE IN PROGRESS

Explanation: This is a normal response to the ZRECP STATUS command or an internal status request indicating that directory capture processing is in progress.

System Action: None.

User Response: None.

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

RECP0524INO RESTART AREAS ACTIVE

Explanation: This is a normal response to the ZRECP STATUS command or an internal status request indicating that recoup phase 1 processing is not processing a TPF group or TPFCS data store now.

System Action: None.

User Response: None.

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

RECP0525IRECOUP RESTART REQUIRED ON PROCESSOR cpuid

Where:

cpuid
One of the following:

Explanation: ZRECP PROC cpuid STATUS was entered and the returned message indicates that recoup processing on processor cpuid failed and must be restarted.

System Action: None.

User Response: Do the following:

  1. Enter ZRECP PROC cpuid RESTART to restart recoup processing on processor cpuid.

See TPF Operations for more information about the ZRECP RESTART and ZRECP STATUS commands. See TPF Database Reference for more information about recoup functions and procedures.

RECP0531IRECOUP STATUS REPORT

Explanation: This is a normal response to the ZRECP STATUS command or to an internal status request, displaying information about the active restart areas. This header is followed by a formatted display of information about the active restart areas.

System Action: None.

User Response: None.

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

RECP0533IRECOUP STATUS REPORT COMPLETED

Explanation: This is a normal response to the ZRECP STATUS command or to an internal status request.

System Action: None.

User Response: None.

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

RECP0601IRECOUP INITIALIZATION STARTED

Explanation: This is the normal response to the ZRECP SETUP command when recoup has begun.

System Action: Recoup initialization continues.

User Response: None.

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

RECP0602ICREATING RECOUP SCHEDULER

Explanation: This is the normal response to the ZRECP SETUP and ZRECP RECALL commands when the recoup scheduling control table (IRSCT) has started to be built.

System Action: Recoup initialization continues.

User Response: None.

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

RECP0603ICREATING ACTIVE ROOT TABLE TEMPLATE

Explanation: This is the normal response to the ZRECP SETUP command when the recoup active root table (IRART) template has started to be built.

System Action: Recoup initialization continues.

User Response: None.

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

RECP0604ICREATING ACTIVE ROOT TABLE FOR PROC procID

Where:

procID
The processor ID.

Explanation: This is the normal response to the ZRECP SETUP command when the recoup active root tables (IRARTs) have started to be built.

System Action: Recoup initialization continues.

User Response: None.

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

RECP0605IRECOUP INITIALIZATION COMPLETED

Explanation: This is the normal response to the ZRECP SETUP command when recoup initialization has completed.

System Action: None.

User Response: None.

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

RECP0606IRECOUP INITIALIZATION RESET

Explanation: This is the normal response to the ZRECP SETUP command with the RESET parameter specified.

System Action: None.

User Response: None.

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

RECP0650EUNABLE TO PROCESS - RECOUP SETUP IN PROGRESS

Explanation: The ZRECP SETUP or ZRECP START command was entered while recoup setup processing was in progress.

System Action: The command is rejected.

User Response: Do one of the following:

See TPF Operations for more information about the ZRECP commands.

RECP0651ECANNOT SET UP RECOUP - GFS NOT ACTIVE

Explanation: The ZRECP SETUP command was entered to initialize recoup, but the command could not be processed because recoup could not obtain pool records.

System Action: The command is rejected.

User Response: Do the following:

  1. Enter the ZCYCL command to cycle the subsystem to a state where get file storage (GFS) is active.
  2. Enter the ZRECP SETUP command again.

See TPF Operations for more information about the ZRECP SETUP and ZCYCL commands.

RECP0652ECANNOT SET UP RECOUP - RECOUP ACTIVE

Explanation: The ZRECP SETUP command was entered to initialize recoup, but the command could not be processed because recoup is active.

System Action: The command is rejected.

User Response: Do one of the following:

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

RECP0653EUNABLE TO CREATE ENVIRONMENT FOR DS - dsName

Where:

dsName
The name of the data store (DS).

Explanation: A ZRECP command was entered, but a TPF collection support (TPFCS) environment could not be created for the data store indicated. This could be the result of TPFCS not being initialized, the recoup data store not being initialized on the subsystem that the command was entered from, database corruption, or an internal error.

System Action: Recoup processing continues.

User Response: Do one of the following:

See TPF Operations for more information about the ZOODB INIT and ZRECP SETUP commands.

RECP0654EUNABLE TO CREATE RECOUP DATA STORE - dsName errorText

Where:

dsName
The name of the TPFCS data store (DS).

errorText
An additional description of the error, if available.

Explanation: The ZRECP SETUP command was entered, but the TPF collection support (TPFCS) recoup data store indicated could not be created in the TPFCS database because of corruption to the system dictionary (DS_SYSTEM_DICT) or the browser dictionary (DS_BROWSE) in the TPFDB data store, or because of an internal error.

System Action: The command is rejected.

User Response: See your IBM service representative.

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

RECP0655EERROR ACCESSING SYSTEM COLLECTION - colName IN DS-dsName function errorText

Where:

colName
The name of the system collection.

dsName
The name of the TPFCS data store (DS) where the system collection resides.

function
The name of the TPF collection support (TPFCS) function that was not successful.

errorText
An additional description of the error, if available.

Explanation: A ZRECP command was entered, but an error occurred while trying to perform the TPFCS function indicated on the system collection indicated.

System Action: If ZRECP SETUP was the command entered, the command is rejected. Otherwise, recoup processing ends abnormally.

User Response: Do the following:

  1. Determine why the system collection indicated is corrupted.
  2. Correct the error.
  3. If the problem continues, see your IBM service representative.

See TPF Operations for more information about the ZRECP commands.

RECP0656EERROR ACCESSING RECOUP SCHEDULER - function errorText

Where:

function
The name of the TPF collection support (TPFCS) function that was not successful.

errorText
An additional description of the error, if available.

Explanation: A ZRECP command was entered, but an error occurred while trying to access the recoup scheduling control table (IRSCT).

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Enter the ZRECP SETUP command from the subsystem that attempted the ZRECP command to access the IRSCT.
  2. Enter the appropriate ZRECP command again.
  3. If the problem continues, see your IBM service representative.

See TPF Operations for more information about the ZRECP commands.

RECP0657ECANNOT UPDATE RECOUP SCHEDULER - GFS NOT ACTIVE

Explanation: The ZRECP RECALL command was entered to run a full recoup, but the command could not be processed because the recoup scheduling control table (IRSCT) could not acquire more pool records needed to store record ID and data store (DS) information.

System Action: Recoup ends abnormally before recoup phase 1 has been completed.

User Response: Do the following:

  1. Enter the ZCYCL command to cycle the subsystem to a state where get file storage (GFS) is active.
  2. Enter the ZRECP SETUP command from the subsystem that attempted the ZRECP RECALL command to reinitialize the IRSCT.
  3. Start recoup processing again.

See TPF Operations for more information about the ZRECP RECALL, ZRECP SETUP, and ZCYCL commands. See The TPF Database Reference for more information about recoup functions and procedures.

RECP0658EFACE ERROR ON DESCRIPTOR CONTROL RECORD

Explanation: A ZRECP command was entered, but an error occurred while trying to access the recoup descriptor control record (#BKDCTL).

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Ensure the FACE table (FCTB) is built correctly.
  2. Ensure the #BKDCTL is allocated correctly.
  3. Enter the appropriate ZRECP command again.

See TPF Operations for more information about the ZRECP commands. See TPF System Generation for more information about the FACE table.

RECP0659EUNDEFINED FACE RECORD TYPE FOUND RECID-recID DSCR-descriptor

Where:

recID
The record ID.

descriptor
The name of the descriptor containing the group with the undefined record type.

Explanation: A ZRECP command was entered, but an error occurred while trying to access the indicated record ID, which is specified in the descriptor shown.

System Action: Recoup processing continues with the next record ID.

User Response: Do the following:

  1. Ensure the FACE table (FCTB) is built correctly.
  2. Ensure the symbolic FACE record types specified in the TYP parameter on the GROUP macro statements for this descriptor, contain FACE record types that are defined in the FACE table. If they do not, do the following:
    1. Correct the GROUP macro statements for the descriptor.
    2. Assemble the changed descriptor.
    3. Load the changed descriptor to the TPF system.
    4. If the version number of the descriptor has changed, enter the ZRBKD command with the MOVE parameter specified to update the descriptor control record.
  3. Enter the appropriate ZRECP command again.

See TPF Operations for more information about ZRECP commands and the ZRBKD command. See TPF System Generation for more information about the FACE table.

RECP0660EGROUP COUNT MISMATCH NUMBER PROCESSED - numProcessed KEYPOINT VALUE - kpValue

Where:

numProcessed
The total number of groups processed and added to the recoup scheduling control table (IRSCT).

kpValue
The number of groups as stored in the recoup keypoint.

Explanation: A ZRECP command was entered that resulted in the IRSCT being built. However, validation of the table failed because the number of groups processed and added to the IRSCT did not match the recoup keypoint value of the expected number of groups.

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Make sure all descriptors are up to date and correctly loaded on the subsystem.
  2. Enter the appropriate ZRECP command again.

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

RECP0662ESEQUENCE COUNTER ERROR DURING CHECKPOINT

Explanation: During an internal checkpoint while phase 1 of recoup was running, a sequence counter error occurred on the recoup active root table (IRART). This indicates that an attempt was made to checkpoint a copy of the IRART that was older than the version already filed.

System Action: The checkpoint attempt is rolled back and recoup processing continues.

User Response: None.

RECP0663EERROR LOCKING RECOUP SCHEDULER errorText

Where:

errorText
An additional description of the error, if available.

Explanation: A ZRECP command was entered, but an error occurred while attempting to lock the recoup scheduling control table (IRSCT) by creating a locking cursor on it.

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Enter the ZRECP SETUP command to reinitialize the internal recoup structures.
  2. Start recoup processing again.
  3. If the problem continues, see your IBM service representative.

See TPF Operations for more information about the ZRECP commands.

RECP0664EERROR UNLOCKING RECOUP SCHEDULER errorText

Where:

errorText
An additional description of the error, if available.

Explanation: A ZRECP command was entered, but an error occurred while attempting to unlock the recoup scheduling control table (IRSCT).

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Determine the cause of the error and correct it.
  2. Enter the appropriate ZRECP command again.
  3. If the problem continues, see your IBM service representative.

See TPF Operations for more information about the ZRECP commands.

RECP0665EERROR ACCESSING TEMPLATE ROOT TABLE - function errorText

Where:

function
The name of the TPF collection support (TPFCS) function that was not successful.

errorText
An additional description of the error, if available.

Explanation: The ZRECP SETUP command was entered, but an error occurred while trying to access the recoup active root table (IRART) template.

System Action: Setup processing ends abnormally.

User Response: Do the following:

  1. Enter ZRECP SETUP from the same subsystem again.
  2. If the problem continues, see your IBM service representative.

See TPF Operations for more information about the ZRECP commands.

RECP0666EERROR ACCESSING ACTIVE ROOT TABLE - function errorText

Where:

function
The name of the TPF collection support (TPFCS) function that was not successful.

errorText
An additional description of the error, if available.

Explanation: A ZRECP command was entered, but an error occurred while trying to access one of the recoup active root tables (IRARTs).

System Action: If the error occurred while reading the IBM recoup active root table (IRART), recoup aborts. Otherwise, if the error occurred while filing the IRART, the checkpoint is rolled back and recoup processing continues.

User Response: Do the following:

  1. Enter the ZRECP SETUP command from the subsystem that attempted the ZRECP command to reinitialize the IRARTs.
  2. Enter the appropriate ZRECP command again.
  3. If the problem continues, see your IBM service representative.

See TPF Operations for more information about the ZRECP commands.

RECP0667EERROR UPDATING RECOUP SCHEDULER - function errorText

Where:

function
The name of the TPF collection support (TPFCS) function that was not successful.

errorText
An additional description of the error, if available.

Explanation: A ZRECP command was entered, but an error occurred while trying to access the recoup scheduling control table (IRSCT). This could be caused by database corruption, possibly including the data store system dictionary (DS_SYSTEM_DICT) for the appropriate recoup data store.

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Enter the ZRECP SETUP command from the subsystem that attempted the ZRECP command to reinitialize the IRSCT.
  2. Enter the appropriate ZRECP command again.
  3. If the problem continues, see your IBM service representative.

See TPF Operations for more information about the ZRECP commands.

RECP0668EERROR OCCURRED WHILE CLEARING TPFCS POOL REUSE TABLE

Explanation: The ZRECP RECALL command was entered, but an error occurred while trying to clear the TPF collection support (TPFCS) pool reuse table (CMMTO2P). This problem could be caused by database corruption.

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Enter the ZRECP RECALL command again.
  2. If the problem continues, see your IBM service representative.

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

RECP0701IPROCESSING STARTING FOR DS dsname

Where:

dsname
The data store (DS) name.

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

System Action: Processing for the data store displayed in the message begins.

User Response: None.

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

RECP0702IPROCESSING COMPLETED FOR DS dsname

Where:

dsname
The data store (DS) name.

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

System Action: Processing for the data store displayed in the message has been completed.

User Response: None.

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

RECP0706IZRECP SEL PID -- COMPLETE

Explanation: This is the normal response to the ZRECP SEL command with the PID parameter specified.

System Action: None.

User Response: None.

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

RECP0708IREST AREA-restartarea SSU-ssu

Where:

restartarea
The index of the restart area whose statistics are being displayed.

ssu
The subsystem user (SSU) associated with the restart area.

Explanation: This is the normal response to the ZRECP STATUS command or when the processing of an item is completed. This is the display of information about a recoup restart area that is processing a TPF collection support (TPFCS) data store or persistent identifier (PID).

System Action: None.

User Response: None.

See TPF Operations for more information about the ZRECP STATUS command and for an example of the informational display. See TPF Database Reference for more information about recoup functions and procedures.

RECP0771EERROR BUILDING DS PID LIST -- function errortext

Where:

function
The name of the TPF collection support (TPFCS) function that was not successful.

errortext
An additional description of the error, if available.

Explanation: An internal error occurred during the TPFCS recoup function. The list of system collections for a particular data store could not be processed.

System Action: Processing for this data store ends and TPF recoup processing continues.

User Response: Examine other messages to determine which data store is being processed, correct the errors, and run recoup processing again. If the problem continues, see your IBM service representative.

See TPF Database Reference for more information about the recoup function.

RECP0772EERROR ACCESSING PID DS NAME PID - pid REF - ref

Where:

pid
The persistent identifier (PID) of the collection being recouped.

ref
The file address or PID of the collection that references the collection being recouped. The reference may be an embedded reference or an internal TPFCS reference to an associated collection. A value of all zeros indicates that the collection being recouped is a system collection.

Explanation: The data store (DS) to which the collection being recouped belongs could not be determined. This error can occur for one of the following reasons:

System Action: The following will occur:

User Response: Do one of the following:

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

RECP0773EERROR ACCESS DATA STORE - dsName - function errortext

Where:

dsName
The name of the data store (DS).

function
The name of the TPF collection support (TPFCS) function that was not successful.

errortext
An additional description of the error, if available.

Explanation: An internal error occurred during the TPF recoup function. The TPFCS data store subsystem information could not be verified.

System Action: The specified data store is not recouped and recoup processing continues.

User Response: See your IBM service representative.

See TPF Operations for more information about the recoup function.

RECP0774EERROR RECOUPING COLLECTION errortext PID - pid REF - ref

Where:

errortext
An additional description of the error, if available.

pid
The persistent identifier (PID) of the collection being recouped.

ref
The file address or PID of the collection that references the collection being recouped. The reference may be an embedded reference or an internal TPFCS reference to an associated collection. A value of all zeros indicates that the collection being recouped is a system collection.

Explanation: An error occurred while processing a particular TPF collection support (TPFCS) collection during phase 1 of recoup processing. If the PID specified was not valid, a recoup index might have been used to locate PIDs embedded in a collection and this PID was retrieved incorrectly because of an error in the index or in the application that manages the collection.

System Action: Processing for this collection ends and processing continues with the next item.

User Response: Do the following:

  1. Determine the cause of the failure by examining the data store being processed and the relevant file addresses. These are contained in the PID.
  2. Run recoup processing again.

See TPF Operations for more information about the recoup function.

RECP0775EERROR RECOUPING CHAIN -- function errortext PID - pid

Where:

function
The TPF collection support (TPFCS) function that was not successful.

errortext
An additional description of the error, if available.

pid
The persistent identifier (PID) of the collection being recouped.

Explanation: An internal error occurred during the TPF recoup function. The internal collections associated with the collection being recouped could not be accessed.

System Action: The collections internally associated with the collection being recouped are not recouped and recoup continues.

User Response: See your IBM service representative.

See TPF Database Reference for more information about the recoup function.

RECP0776EERROR ACCESSING RECOUP INDEX index -- function errortext PID - pid REF - ref

Where:

index
The name of the recoup index that could not be accessed.

function
The TPF collection support (TPFCS) function that was not successful.

errortext
An additional description of the error, if available.

pid
The persistent identifier (PID) of the collection being recouped.

ref
The file address or PID of the collection that references the collection being recouped. The reference may be an embedded reference or an internal TPFCS reference to an associated collection. A value of all zeros indicates that the collection being recouped is a system collection.

Explanation: An internal error occurred during the TPF recoup function. The TPFCS recoup index associated with the collection being recouped could not be accessed.

System Action: Processing for this collection ends and processing continues with the next item.

User Response:

See TPF Operations for more information about the ZBROW RECOUP command.

RECP0777ERECOUP INDEX PARAMETER NOT VALID -- parameter RECOUP INDEX - indexname

Where:

parameter
The recoup index field that is not valid, such as ACCESSTYPE, COLTYPE, or ENTRYTYPE.

indexname
The name of the recoup index.

Explanation: An error occurred while trying to access embedded TPFCS persistent identifiers (PIDs) or file addresses in a particular collection during the TPF recoup function. This is most likely the result of the recoup index not being valid.

System Action: Processing for this collection ends and processing continues with the next item.

User Response: Do the following:

  1. Determine the cause of the failure by examining the recoup index being used to access embedded information.
  2. Correct the recoup index.
  3. Run recoup processing again.

See TPF Operations for more information about the ZBROW RECOUP command, that can be used to modify recoup indexes.

RECP0778EERROR ACCESSING COLLECTION -- function errortext PID - pid REF - ref

Where:

function
The TPF collection support (TPFCS) function that was not successful.

errortext
An additional description of the error, if available.

pid
The persistent identifier (PID) of the collection being recouped.

ref
The file address or PID of the collection that references the collection being recouped. The reference may be an embedded reference or an internal TPFCS reference to an associated collection. A value of all zeros indicates that the collection being recouped is a system collection.

Explanation: An internal error occurred during the recoup function. The collection being recouped could not be accessed to retrieve embedded PIDs or file addresses.

System Action: Processing for this collection ends and processing continues with the next item.

User Response: See your IBM service representative.

See TPF Operations for more information about the recoup function.

RECP0779EERROR READING COLLECTION INDEX - indexname PID - pid REF - ref

Where:

indexname
The name of the recoup index.

pid
The persistent identifier (PID) of the collection being recouped.

ref
The file address or PID of the collection that references the collection being recouped. The reference may be an embedded reference or an internal TPFCS reference to an associated collection. A value of all zeros indicates that the collection being recouped is a system collection.

Explanation: The ZRECP RECALL command was entered, but an error occurred because embedded PIDs or file addresses could not be read. This may occur because the access type associated with the recoup index entries is not compatible with the collection type. For example, a key sorted set cannot be associated with a heterogeneous recoup index that accesses elements by index.

System Action: Processing for this PID ends and processing continues with the next PID.

User Response: Do the following:

  1. Determine the cause of the failure by checking the collection for corruption.
  2. Run the recoup function again.

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

RECP0782ETPFCS ERROR THRESHOLD REACHED

Explanation: The maximum number of TPF collection support (TPFCS) errors to report to the computer room agent set (CRAS) terminal has been reached for the data store being processed. This number is set by the ZRECP PROFILE command with the CSERRMAX parameter.

System Action: Recoup will continue to run but will not report any additional errors to the CRAS terminal for that data store.

User Response: If it is desired for more errors to be sent to the CRAS terminal on future recoup runs, use the ZRECP PROFILE command with the CSERRMAX parameter to increase the TPFCS recoup error threshold prior to your next run of recoup.

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

RECP0784EUNABLE TO FIND DESCRIPTOR EMBEDDED DATA - embeddata PID-pid

Where:

embeddata
The embedded file address entry in the collection element, which is displayed as hexadecimal character data.

pid
The persistent identifier (PID) of the collection being recouped.

Explanation: TPF recoup processing tried to chain-chase a TPF record embedded in a TPF collection support (TPFCS) collection, but a descriptor for the embedded record was not found.

System Action: The embedded file address reference is bypassed and processing continues.

User Response: Do the following:

  1. Ensure that the appropriate descriptor is loaded.
  2. Run recoup processing again.

See TPF Operations for more information about the ZRECP commands.

RECP0785EEMBEDDED FILE ADDRESS REFERENCE FLAG NOT VALID EMBEDDED DATA - embeddata PID-pid

Where:

embeddata
The embedded file address entry in the collection element, which is displayed as hexadecimal character data.

pid
The persistent identifier (PID) of the collection being recouped.

Explanation: The embedded reference flag in the embedded file address entry is not valid. The only allowed values are TO2_RECOUP_DSCR_NO and TO2_RECOUP_DSCR_YES.

System Action: The embedded file address reference is bypassed and processing continues.

User Response: Do the following:

  1. Update your data to make sure the embedded file address entry contains a valid embedded reference flag.
  2. Run recoup processing again.

See TPF Operations for more information about the ZRECP commands.

RECP0786EEMBEDDED REFERENCE LENGTH NOT VALID PID-pid

Where:

pid
The persistent identifier (PID) of the collection being recouped.

Explanation: TPF recoup attempted to retrieve an embedded reference from a collection, but the length of the embedded reference was too short to represent an embedded reference.

System Action: The embedded reference is bypassed and processing continues with the next embedded reference.

User Response: Do the following:

  1. Determine if the recoup index associated with the collection containing the embedded reference needs to be corrected.
  2. Determine if the embedded reference was stored in the collection incorrectly.
  3. Correct the errors.
  4. Run recoup processing again.

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

RECP0787EEMBEDDED ADDRESS FORMAT NOT VALID EMBEDDED DATA - embeddata PID-pid

Where:

embeddata
The embedded file address entry in the collection element, which is displayed as hexadecimal character data.

pid
The persistent identifier (PID) of the collection being recouped.

Explanation: TPF recoup attempted to extract an embedded file address from a collection, but the file address format indicator was not valid.

System Action: The embedded file address is bypassed and processing continues with the next embedded reference.

User Response: Do the following:

  1. Check the file address indicator in the embedded reference data to be sure it is set up correctly.
  2. Correct the errors.
  3. Run TPF recoup processing again.

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

RECP0788ETPFCS RECOUP TIMEOUT PID-pid REF-ref

Where:

pid
The persistent identifier (PID) of the collection that did not end normally when the timeout occurred.

ref
The file address or PID of the collection that references the collection being recouped. The reference may be an embedded reference or an internal TPFCS reference to an associated collection. A value of all zeros indicates that the collection being recouped is a system collection.

Explanation: TPF recoup could not confirm that an entry control block (ECB) used to process a particular PID was completed in the specified amount of time. It is possible that the ECB either ended abnormally or continued to run after the timeout threshold was reached.

System Action: TPF recoup continues.

User Response: Do either of the following:

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

RECP0789EPID NOT FOUND IN ECB TABLE PID-pid

Where:

pid
The persistent identifier (PID) of the collection being recouped.

Explanation: A recoup entry control block (ECB) that was processing a collection exited, but a corresponding entry could not be located in the recoup active root table (IRART) for the processor where the ECB was running. This could result from a timeout occurring and the ECB entry in the IRART being removed by the system.

System Action: The ECB exits and processing continues.

User Response: Do one of the following:

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

RECP0790EHEX CONVERSION ERROR ON PID PARAMETER

Explanation: A ZRECP SEL command was entered with the PID parameter specified. This command was not processed because the hexadecimal value specified for the PID parameter contained one of the following:

System Action: The command is rejected.

User Response: Enter the ZRECP SEL command again specifying a valid hexadecimal value for the PID parameter.

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

RECP0791EDESCRIPTOR dscr VERSION MISMATCH BEFORE CHAIN CHASE

Where:

dscr
The name of the descriptor.

Explanation: The ZRECP RECALL command was entered, but the active descriptor version in core memory did not match the version stored in the BKD load control record (#BKDCTL).

System Action: The command fails and recoup processing ends abnormally.

User Response: Do the following:

  1. Determine which version of the descriptor is correct.
  2. Do one of the following:
  3. Start recoup processing again.

See TPF Operations for more information about the ZRBKD command.

RECP0792EDESCRIPTOR dscr NOT CORE RESIDENT BEFORE CHAIN CHASE

Where:

dscr
The name of the descriptor.

Explanation: The ZRECP RECALL command was entered, but the active descriptor version is not core resident.

System Action: The command fails and recoup processing ends abnormally.

User Response: Do the following:

  1. Define the recoup descriptor as core resident.
  2. Start recoup processing again.

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

RECP0793EDESCRIPTOR dscr VERSION MISMATCH ON PRIMARY PROCESSOR

Where:

dscr
The name of the descriptor.

Explanation: Recoup chain chase processing on the primary processor accessed a descriptor with an active descriptor version in core memory that did not match the version stored in the BKD load control record (#BKDCTL).

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Determine which version of the descriptor is correct.
  2. Do one of the following:
  3. Start recoup processing again.

See TPF Operations for more information about the ZRBKD command.

RECP0794EDESCRIPTOR dscr NOT CORE RESIDENT ON PRIMARY PROCESSOR

Where:

dscr
The name of the descriptor.

Explanation: Recoup chain chase processing on the primary processor accessed a descriptor version that is not core resident.

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Define the recoup descriptor as core resident.
  2. Start recoup processing again.

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

RECP0795EDESCRIPTOR dscr VERSION MISMATCH ON SECONDARY PROCESSOR

Where:

dscr
The name of the descriptor.

Explanation: Recoup chain chase processing on the secondary processor accessed a descriptor with an active descriptor version in core memory that did not match the version stored in the BKD load control record (#BKDCTL).

System Action: Recoup processing does not chain chase the accessed version of the descriptor on this processor, but will chase it on the primary processor.

User Response: Ensure that all processors that are running recoup are at the same program update tape (PUT) level.

RECP0796EDESCRIPTOR dscr NOT CORE RESIDENT ON SECONDARY PROCESSOR

Where:

dscr
The name of the descriptor.

Explanation: Recoup chain chase processing on a secondary processor accessed a descriptor that was not core resident.

System Action: Recoup processing does not chain chase the accessed descriptor on this processor, but will chase it on the primary processor.

User Response: Ensure that all processors that are running recoup are at the same program update tape (PUT) level.

RECP0797EFACE ERROR ON DESCRIPTOR CONTROL RECORD

Explanation: A ZRECP command was entered, but an error occurred while trying to access the recoup descriptor control record (#BKDCTL).

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Ensure the FACE table (FCTB) is built correctly.
  2. Ensure the #BKDCTL record is allocated correctly.
  3. Enter the appropriate ZRECP command again.

See TPF Operations for more information about the ZRECP commands. See TPF System Generation for more information about the FACE table.

RECP0798EDUPLICATE RECID / VERSION FOUND DESCRIPTOR CONTROL RECORD SLOTS slot1, slot2 RECID-recID VERSION- version

Where:

slot1
The slot number of the first descriptor with the duplicate record ID and version.

slot2
The slot number of the second descriptor with the duplicate record ID and version.

recID
The duplicate record ID in 4-byte hexadecimal format.

version
The duplicate version, if available.

Explanation: A ZRECP command was entered that resulted in the recoup scheduling control table (IRSCT) being built. However, validation of the table failed because two entries were found that had the same record ID and version number.

System Action: Recoup processing ends abnormally.

User Response: Do the following:

  1. Examine the descriptor control record whose slots are indicated and make sure each record ID and version are unique for the subsystem.
  2. Make sure all descriptors are up to date and correctly loaded on the subsystem.
  3. Enter the appropriate ZRECP command again.

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