gtpm4m1hMessages (System Error and Offline)

DAT0-DYO0

DAT001MORE THAN ONE DATACO MACRO WAS CODED

Severity: 5

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Remove all but one DATACO macro.
  2. Rerun SIP stage I.

DB2P0000IDB2PP COMPLETED SUCCESSFULLY

Explanation: The TPF DB2 postprocessor (DB2PP) completed successfully.

System Action: None.

User Response: None.

See TPF Application Requester User's Guide for more information.

DB2P0001EUNABLE TO ACCESS INPUT FILE

Explanation: An error occurred because the file containing the modified source file or the database resource module (DBRM) could not be opened.

System Action: The postprocessor returns failure status and posts an error message to the message file.

User Response: Have your system programmer determine the cause of the error and correct it.

See TPF Application Requester User's Guide for more information.

DB2P0002EUNABLE TO ACCESS OUTPUT FILE

Explanation: An error occurred because the file could not be opened for the postprocessor output.

System Action: The postprocessor returns failure status and posts an error message to the message file.

User Response: Have your system programmer determine the cause of the error and correct it.

See TPF Application Requester User's Guide for more information.

DB2P0003EERROR -- INVALID PARAMETER DEFINITION

Explanation: An error occurred because you specified a parameter that is not valid for the TPF DATABASE 2 (DB2) postprocessor keywords. Valid parameters are:

System Action: The postprocessor returns the failure status and posts an error message to the message file.

User Response: Specify the correct parameters for the TPF DB2 postprocessor keywords.

See TPF Application Requester User's Guide for more information about the valid parameters for the TPF DB2 postprocessor keywords.

DB2P0004WWARNING -- UNABLE TO FIND KEY: CHAR SQLTEMP[19]

Explanation: An error occurred because the expected key was not found.

System Action: The postprocessor returns the success status and posts a warning message to the message file.

User Response: Add the key to the source file.

See TPF Application Requester User's Guide for more information.

DB2P0005WWARNING -- UNABLE TO FIND KEY: STRUCT SQLCA SQLCA

Explanation: An error occurred because the expected key was not found.

System Action: The postprocessor returns the success status and posts a warning message to the message file.

User Response: Add the key to the source file.

See TPF Application Requester User's Guide for more information.

DB2P0006EERROR -- DUPLICATE KEYS FOUND: #PRAGMA LINKAGE

Explanation: An error occurred because two or more occurrences of the same key were found.

System Action: The postprocessor returns the failure status and posts an error message to the message file.

User Response: Remove the duplicate keys from the source file.

See TPF Application Requester User's Guide for more information.

DB2P0007EERROR -- DUPLICATE KEYS FOUND: CHAR SQLTEMP[19]

Explanation: An error occurred because two or more occurrences of the same key were found.

System Action: The postprocessor returns the failure status and posts an error message to the message file.

User Response: Remove the duplicate keys from the source file.

See TPF Application Requester User's Guide for more information about the FINIS macro.

DB2P0008EERROR -- INVALID NUMBER OF PARAMETERS

Explanation: An error occurred because you specified an incorrect number of parameters to the postprocessor for the TPF DATABASE 2 (DB2) postprocessor keywords. You can specify up to 3 parameters:

Note:
If 3 parameters are specified for HOST(C), the third parameter is ignored.

System Action: The postprocessor returns the failure status and posts an error message to the message file.

User Response: Specify the correct number of parameters to the postprocessor.

See TPF Application Requester User's Guide for more information about the valid parameters for the TPF DB2 postprocessor keywords.

DB2P0009ETHE PKGISOL PARAMETER IS INCORRECT OR NOT SPECIFIED.

Explanation: An error occurred because the values specified for the package isolation level were not valid. Valid values are RR or CS. PKGISO is a required field for HOST(ISOC).

System Action: The postprocessor returns the failure status and posts an error message to the message file.

User Response: Specify the correct value for the package isolation level.

DB2P0010EUNABLE TO OPEN DBRM FILE.

Explanation: An error occurred while opening the database request module specified in the INDBRM DD statement of the postprocessor job control language.

System Action: The postprocessor returns failure status and posts an error message to the message file.

User Response: Ensure the database request module file is specified correctly.

DB2P0053WKEY NOT FOUND: #pragma linkage (DSHNLI,OS)

Where:

#pragma linkage
#pragma key number 1

Explanation: An error occurred because the expected key was not found.

System Action: The postprocessor returns the success status and posts a warning message to the message file.

User Response: Add the missing key to the source file being post processed.

DDC0010xxx0yyy STARTING INTERVAL GREATER THAN FINISHING INTERVAL

Where:

xxx
The starting interval.

yyy
The finishing interval.

Severity: 5

Explanation: The starting interval referenced in the message must be less than or equal to the finishing interval referenced in the message for the INTxP and INTxN parameters of the DDCCAP macro.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

DDC002HYPHEN MISSING IN SUBOPERAND xxxx

Where:

xxxx
The suboperand value.

Severity: 5

Explanation: The suboperand value referenced in the message did not contain a hyphen (-) as a delimiter.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

DDC004NO OPERANDS SPECIFIED FOR DDCCAP

Severity: 5

Explanation: All non-default operands must be specified.

System Action: None.

User Response: Do the following:

  1. Specify the required operands.
  2. Rerun SIP stage I.

DDC007xxxx/yyyy MODS OVERLAP

Where:

xxxx
Operand 1.

yyyy
Operand 2.

Severity: 5

Explanation: The modules between operand 1 and operand 2, as referenced in the message, overlap.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

DDC008OPERAND xxxx CONTAINS MORE THAN yyyy SUB-OPERANDS

Where:

xxxx
The operand.

yyyy
The valid number of suboperands.

Severity: 5

Explanation: The operand referenced in the message contains more than the valid number of suboperands.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

DDC011xxxx MOD RANGE yyyy OVERLAP

Where:

xxxx
The module range.

yyyy
The operand.

Severity: 5

Explanation: The module range for the operand referenced in the message overlaps another range for the same operand.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

DYO01000Wdirectories DIRECTORIES WERE SPECIFIED FOR SHORT TERM POOL SECTION identifier. ONLY THE FIRST 65,536 WILL BE USABLE ONLINE.

Where:

directories
The number of directories (in decimal format).

identifier
The pool section identifier (for example, SSTA).

Explanation: The FACE table (FCTB) input specified more than 65 536 directories for this short-term pool section; however, there is an addressing limit of 65 536 directories for each short-term pool section in the online system.

System Action: The DYOPM job runs to completion but only the first 65 536 directories in this pool section are usable online.

User Response: Do the following:

  1. Review the OPMTBL input for this pool section to determine the cause of the error.
  2. Correct the error.

DYO01001WMAXIMUM RECORD ID TABLE SIZE TO BE USED = entries

Where:

entries
The current maximum number of entries that DYOPM will allocate for the record ID hash table.

Explanation: This message indicates that, even though you tried to specify a larger number of entries for DYOPM to allocate for the record ID hash table, this is the number of entries that DYOPM actually used.

System Action: None.

User Response: None.

See TPF Database Reference for more information about valid parameters for offline pool maintenance.

DYO02000Edirectories DIRECTORIES WERE SPECIFIED. ONLY 16,777,216 ARE ALLOWED.

Where:

directories
The number of directories (in decimal format).

Explanation: The OPMTBL input specified more than 16 777 216 directories; however, there is an addressing limit of 16 777 216 directories in the online system.

System Action: The DYOPM job ends with an error return code.

User Response: Do the following:

  1. Review the OPMTBL input for this pool section to determine the cause of the error.
  2. Correct the error.
  3. Run the DYOPM job again.

DYO02001ERCP RUN NUMBER: value1 DOES NOT MATCH value2 - RUN ABORTED

Where:

value1
The time stamp value saved in the first RCP tape mounted.

value2
The time stamp value saved in another RCP tape.

Explanation: There is a mismatch in the time stamps between the RCP tapes. These RCP tapes are not from the same recoup run.

System Action: The DYOPM job ends with an error return code.

User Response: Do the following:

  1. Mount the correct RCP tapes with the same time stamp.
  2. Run the DYOPM job again.

DYO02002EEND OF RCP DATA NOT FOUND

Explanation: The last routing control parameter (RCP) tape is missing.

System Action: The DYOPM job ends with an error return code.

User Response: Run the DYOPM job again ensuring all RCP tapes are used.

DYO02003EINVALID NUMBER OF ENTRIES FOR RECORD ID TABLE: string -- RUN ABORTED

Where:

string
A portion of the string that DYOPM encountered where a numerical parameter was expected.

Explanation: DYOPM found a non-numerical value coded where it was expecting to find the number of entries to allocate for its record ID hash table.

System Action: None.

User Response: Do one of the following:

See TPF Database Reference for more information about valid parameters for offline pool maintenance.

DYO02004EINVALID PARM DELIMITER: character -- RUN ABORTED

Where:

character
A character that DYOPM encountered where a valid delimiter (a comma) was expected in the parameter string.

Explanation: Any parameter specified after the DYOPM intervention parameter must be preceded by a valid delimiter.

System Action: None.

User Response: Do the following:

  1. Correct the parameter string coded for DYOPM.
  2. Submit the job again.

See TPF Database Reference for more information about valid parameters for offline pool maintenance.