00E40417

Explanation

An object descriptor block (OBD) could not be found for the object identifier (OBID) that is associated with the object descriptor. Either the database descriptor (DBD) address or the OBID is zero.

System action

The utility job is abended. A SYSABEND dump of batch storage is requested.

System programmer response

Determine the failing environment. 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.

User response

Notify the system programmer.

Problem determination

This code identifies an internal error. The name of the control section (CSECT) that is involved is given in VRARRK5. The full CSECT name given in the dump title.

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.
  • A listing of the SYS1.LOGREC data set, obtained by executing IFCEREP1.
  • 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.
  • UTPRINT output, produced by utility invocation of SORT.
  • Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 (for 04E and 04F abends). Availability of this dump is dependent on the failing environment.
  • SYSABEND, SYSUDUMP, or SYSMDUMP output. Availability of these dumps is dependent on the failing environment.
  • The DBID and OBID shown in the abend diagnostics that precede the DSNU016I message in the failing utility job step.