APAR status
Closed as canceled.
Error description
MSGDSNV086E -xxxx DB2 ABNORMAL TERMINATION REASON=00E80084 The DB2 Message and Codes manual (all releases), notes return code 00E80084: Explanation: A resource manager provided notification of failure during subsystem startup notification processing. This abend reason code is issued by the following CSECT: DSNYSIRM Operator Response: Verify that you entered the -START DB2 command using the correct DSNZPARM init parm module. etc.. --------------------------------------------------------------- This operator response is rarely the cause of this error, and the ZPARM inference is vague and misleading. This infoapar will list several more common reasons for DB2 startup to terminate and issue this RC00E80084 error code. In all cases, the true 'OPERATOR RESPONSE', is to check the MVS SYSLOG for messages that precede the DSNV086E shutdown message. ---------------------------------------------------------------- (1) During DB2 coldstart, DB2 Log Manager will force a log switch. If there are no ACTIVE logs to switch to, then DB2 will terminate with the E80084 code. User will need to allocate more logs using the DSNJU003 Change Log Inventory standalone utility. See your DB2 Command and Utility Reference manual for parms and JCL. (2) During DB2 startup, an IRLM error may cause DB2 to issue the 00E80084 termcode. Check your SYSLOG for IRLM errors that precede this termination message. Attempt to start IRLM alone, without DB2. Note: If IRLM does not startup, then DB2 will never startup. DB2 does not run without IRLM. Correct any IRLM error first, then startup DB2. Note: the default for IRLM autostart is 300 seconds. This means that if DB2 is to autostart IRLM, IRLM must comeup completely within the 300 second time period. If it fails to do so, then DB2 will be terminated with the E80084 termination code. DSN6SPRM IRLMSWT (SPRM+50) (3) DB2 startup error RC00E30081 then DB2 terminates. In the IRLMPROC, JCL points to the wrong IRLM subsystem. This IRLM subsystem may be valid and startable, but it is NOT the same IRLM that is defined in DSNZPARM SubSystem Name (IRLMSID). (4) Allocating the ACTIVE logs with improper VSAM dataset SHAREOPTIONS. The termination code will be preceded by MSGDSNJ250E and MSGDSNJ251E. For DB2 datasharing members, all ACTIVE log VSAM LDS should be defined with SHAREOPTIONS(2 3). User can use the IDCAMS ALTER command to change the VSAM shroptns to the appropriate (crossregion crosssystem) values. See manual: DFSMS/MVS Access Method Services for the ICF (5) There are several BSDS related problems that will result in the 00E80084 termination: (a) BSDS timestamp mismatch between the 2 BSDS datasets. (b) BSDS End OF Log (EOF) RBA mismatch. (c) BSDS RBA higher than any known RBA during NON-coldstart. (d) Bad Active LOG entry in BSDS (e) Bad, invalid record read from the BSDS (f) MSGDSNJ112E Active LOGs defined incorrectly to BSDS. (6) In regards to the DSNZPARM, what may occur would be that in the ZPARM is a pointer to the associated ICF catalog. If you started DB2x, pointing to the ZPARMs of DB2y, this catalog mismatch might be sensed. This error would usually be preceded by a VSAM open error. DSNZPARM: DSN6SPRM CATALOG (CATALOG ALIAS SPRMVCAT) (7) The Abend Reason code 00E80084 may also be issued if there are storage related problems. The storage shortage may not be seen in the SYSLOG. JOBLOG or EREP data. If no other conditions are found for the failure, the current common storage utilization should be monitored using RMF or monitors that display common storage usage.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
Closed for DB2INFO use. DB2 5740XYR00 ABEND04F R230 R310 R410 Note: This E80084 error is a DB2 startup termination err. In your DB2 Administration Guide there is a section called: STARTING and STOPPING DB2 (R310 VOLII chap6 page15) When reporting this ABTERM, it is very helpfull to note to the service rep, what was the last of these startup messages that was presented before the DSNV086E Abterm was presented. These messages along with any of the aforementioned messages can be found in the MVS SYSLOG.
APAR Information
APAR number
II09170
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1996-01-04
Closed date
1996-01-21
Last modified date
2008-10-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
20 October 2008