gtpm4m1h | Messages (System Error and Offline) |
DAT001 | MORE THAN ONE DATACO MACRO WAS CODED |
Severity: 5
Explanation: None.
System Action: None.
User Response: Do the following:
DB2P0000I | DB2PP 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.
DB2P0001E | UNABLE 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.
DB2P0002E | UNABLE 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.
DB2P0003E | ERROR -- 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.
DB2P0004W | WARNING -- 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.
DB2P0005W | WARNING -- 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.
DB2P0006E | ERROR -- 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.
DB2P0007E | ERROR -- 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.
DB2P0008E | ERROR -- 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:
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.
DB2P0009E | THE 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.
DB2P0010E | UNABLE 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.
DB2P0053W | KEY NOT FOUND: #pragma linkage (DSHNLI,OS) |
Where:
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.
Where:
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:
Where:
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:
Severity: 5
Explanation: All non-default operands must be specified.
System Action: None.
User Response: Do the following:
Where:
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:
Where:
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:
Where:
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:
DDC001 0xxx0yyy STARTING INTERVAL GREATER THAN FINISHING
INTERVAL
DDC002 HYPHEN MISSING IN SUBOPERAND xxxx
DDC004 NO OPERANDS SPECIFIED FOR DDCCAP
DDC007 xxxx/yyyy MODS OVERLAP
DDC008 OPERAND xxxx CONTAINS MORE THAN yyyy SUB-OPERANDS
DDC011 xxxx MOD RANGE yyyy OVERLAP
DYO01000W | directories DIRECTORIES WERE SPECIFIED FOR SHORT TERM POOL SECTION identifier. ONLY THE FIRST 65,536 WILL BE USABLE ONLINE. |
Where:
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:
DYO01001W | MAXIMUM RECORD ID TABLE SIZE TO BE USED = entries |
Where:
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.
DYO02000E | directories DIRECTORIES WERE SPECIFIED. ONLY 16,777,216 ARE ALLOWED. |
Where:
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:
DYO02001E | RCP RUN NUMBER: value1 DOES NOT MATCH value2 - RUN ABORTED |
Where:
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:
DYO02002E | END 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.
DYO02003E | INVALID NUMBER OF ENTRIES FOR RECORD ID TABLE: string -- RUN ABORTED |
Where:
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.
DYO02004E | INVALID PARM DELIMITER: character -- RUN ABORTED |
Where:
Explanation: Any parameter specified after the DYOPM intervention parameter must be preceded by a valid delimiter.
System Action: None.
User Response: Do the following:
See TPF Database Reference for more information about valid parameters for offline pool maintenance.