00E30071
Explanation
Either Db2 terminated without successfully signing off from IRLM, or another subsystem with the same SSNAME is still connected. This abend reason code accompanies message DSNT380I.
System action
A record is written to SYS1.LOGREC, and an SVC dump is requested. Db2 is abended.
Operator response
Determine if another Db2 subsystem is active. If another subsystem is not active, and IMS is not sharing the same IRLM, cancel IRLM prior to starting Db2. Regardless, notify the system programmer.
System programmer response
Obtain a copy of SYS1.LOGREC and the SVC dump. 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 error was caused by a previously unsuccessful QUIT from the IRLM, manually stop IRLM. If IMS is using the same IRLM, refer to the IMS documentation to determine the effect of IRLM terminating while IMS is connected.
If you are running multiple versions of Db2, ensure that the SSNAME specified by the DSN6SPRM macro during the installation of the member DSNZPARM is not the same as the SSNAME in another version of Db2.
Problem determination
A previously unsuccessful sign-off from the IRLM is documented by an abend of X'00E30075' during the previous termination of Db2.
- 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.
- Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 (04E and 04F abends).
- SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
- A listing of the SYS1.LOGREC data set, obtained by executing IFCEREP1.
- Listing of DSNZPARM module used.
- IRLM trace output.