00D44031

Explanation

The Db2-DL/I batch support cannot continue because a connection could not be established to the Db2 subsystem named in the DDITV02 SYSIN data set. This error usually occurs for one of these reasons:
  • The Db2 subsystem name specified either in the DDITV02 SYSIN data set (default) or in the member defined by the IMSID-SSM combination is incorrect.
  • The Db2 system is not operational.

System action

The Db2-DL/I batch support cannot continue and processing is terminated.

Operator response

It might be necessary to start the Db2 subsystem specified.

System programmer response

Either correct the DDITV02 DD SYSIN or the member pointed to by the IMSID-SSM combination for the Db2 subsystem name if it is incorrect, and rerun the job. Otherwise, have the operator start the Db2 subsystem if it is stopped.

User response

Notify the system programmer.

Problem determination

Either check the DDITV02 DD SYSIN or the member pointed to by the IMSID-SSM combination for the proper Db2 subsystem name. Make sure the correct data set name is specified by the DDITV02 DD statement and the DCB RECFM is F or FB for the data set.

The WAL control block in the dump contains information about the connection and the IMS attach trace table. Field WALSSID indicates the name of the Db2 subsystem being called.

The last entry in the trace table has an ID of ID00 and the CALL STATUS contains the 2-byte return code and 4-byte reason code of the failure. The 4-byte reason code might provide additional diagnostic information to help determine the cause of the failure.

If you suspect an error in Db2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.

If the correct Db2 subsystem name was specified and was available, refer to the specific reason code explanation for details about the error.

Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • SYSABEND, SYSUDUMP, or SYSMDUMP output.
  • SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
  • Copy of the DDITV02 SYSIN data set.
  • Copy of the DDOTV02 output data set.
.