Error messages for the DPSUMLD program
The following error messages are produced by the table load DPSUMLD program. All messages are written to the DPSYSOUT data set.
CANNOT OPEN DPLOAD DATASET
Explanation: DPLOAD DD was not defined. The load request is aborted.
User response: Add DPLOAD DD for LOAD requests.
KEYWORD xxxxxxxx MUST BE SPECIFIED WITH VALUE
Explanation: The keyword xxxxxxxx does not have a default value and a value must be specified. The request is not processed.
User response: Supply correct value.
TABLE OR SUMMKEY MUST BE SPECIFIED
Explanation: Either TABLE or SUMMKEY must be specified in a summarization request. The request is not processed.
User response: Supply correct value.
EITHER FROMTBL OR FROMDD MUST BE SPECIFIED, BUT NOT BOTH
Explanation: FROMTBL and FROMDD are specified. One or the other must be specified, but not both. The request is not processed.
User response: Supply correct value.
EITHER EXPDT OR REPTD MUST BE SPECIFIED, BUT NOT BOTH
Explanation: EXPDT and REPTD are specified. One or the other must be specified, but not both. The request is not processed.
User response: Supply correct value.
SUMMKEY - LUWIDNID - IS ALLOWED ONLY IF TYPE IS SUMACCT OR SUMDDFACCT
Explanation: The SUMMKEY - LUWIDNID - is allowed only if the type is SUMACCT or SUMDDFACCT. The request is not processed.
User response: Do not use LUWIDNID as the SUMMKEY. Correct and resubmit.
SUMMKEY - LUWIDLUNM - IS ALLOWED ONLY IF TYPE IS SUMACCT OR SUMDDFACCT
Explanation: The SUMMKEY - LUWIDLUNM - is allowed only if the type is SUMACCT or SUMDDFACCT. The request is not processed.
User response: Do not use LUWIDLUNM as the SUMMKEY. Correct and resubmit.
SUMMKEY - DDFLOCATION - IS ALLOWED ONLY IF TYPE IS DDFACCT OR SUMDDFACCT
Explanation: The SUMMKEY - DDFLOCATION - is allowed only if the type is DDFACCT or SUMDDFACCT. The request is not processed.
User response: Do not use DDFLOCATION as the SUMMKEY. Correct and resubmit.
xxxxxxxxxxxxxx IS NOT A VALID SUMMKEY VALUE
Explanation: The column xxxxxxxxxxxxxx is not a valid SUMMKEY column. The request is not processed.
User response: Supply correct value.
DB2 ERROR MESSAGES RECEIVED
Explanation: DB2 has issued error messages. The request is not processed.
User response: Refer to the DB2 error message received.
PROCESSING ABORTED AS INVFIELD=ABORT (DEFAULT)
Explanation: An invalid column was found. The request is not processed.
User response: Specify INVFIELD=IGNORE or redefine the table without the invalid column.
DATA AREA RUNS OUT. CONTACT BMC SOFTWARE
Explanation: The internal data area for SQLDA runs out. The request is not processed.
User response: Contact BMC Customer Support.
CANNOT OPEN xxxxxxxx DD, PROCESS TERMINATED
Explanation: The DD xxxxxxxx statement cannot be opened. The request is not processed.
User response: Correct the DD statement and resubmit.
SORT HAS ENCOUNTERED ERROR. SUMMARY PROCESS TERMINATED
Explanation: Errors have occurred in the sort. The request is not processed.
User response: Determine the reason for the sort error from the sort messages.
COMBINE FIELD - xxxxxxxxxxxxx IS AN INVALID FIELD, COMBINE ABORTED
Explanation: The field xxxxxxxxxxxxx defined in the COMBINE parameter is an invalid field. Processing of the COMBINE parameter is aborted.
User response: Supply correct values for the COMBINE parameter.
COMBINE FIELD - xxxxxxxxxxxxx HAS INVALID ATTRIBUTE, COMBINE ABORTED
Explanation: The COMBINE xxxxxxxxxxxxx field has an invalid or incompatible attribute. Processing of the COMBINE parameter is aborted.
User response: Supply correct values for the COMBINE parameter.
SUMMKEY - xxxxxxxxxxxx IS NOT DEFINED IN RECEIVING TABLE
Explanation: The column xxxxxxxxxxxx defined in SUMMKEY is not defined in the receiving table. The request is not processed.
User response: Supply correct values for SUMMKEY or TABLE.
DB2 CONNECTION NOT ESTABLISHED
Explanation: DB2 connection cannot be established. No further requests can be accepted.
User response: Refer to subsequent messages for diagnostics.
DB2 CONNECTION MUST BE ESTABLISHED BEFORE PROCESSING ANY REQUEST
Explanation: A request cannot be processed until the DB2 connection is established. The request is not processed.
User response: Find the reason for the DB2 connection failure.
MAKE SURE GLOBAL STATEMENT IS CODED
Explanation: DB2 connection is not established. No further requests can be accepted.
User response: Assure GLOBAL statement was coded; if it was, continue looking for the reason for the DB2 connection failure.
INVALID PARM PASSED. PROGRAM TERMINATED.
Explanation: An invalid PARM= was specified on the EXEC JCL statement. The only valid values are none or NGTLOAD. The job step is terminated.
User response: Correct the PARM value and resubmit the job.
Related topic