00D94001 and message DSNV086E. Standard DB2 diagnostic information is recorded in SYS1.LOGREC. An 04 - IBM DB2
1. Run the print log map (DSNJU004) utility to print the content of both BSDSs. 2. Print SYS1.LOGREC. 3. Use the MVS DISPLAY DUMP command to get the failure reason code from dump titles. 4. Notify your system programmer. Obtain a copy of the SYS1.LOGREC and the SVC dump for the original error. Refer to the recovery scenarios in Part 4 (Volume 1) of DB2 Administration Guide before restarting. To restart DB2, you must do one of the following: v Add the missing archive log data sets back to the BSDS with the change log inventory (DSNJU003) utility and increase the MAXARCH parameter in the DSN6LOGP member of DSNZPARM to complete the rollback, or v Restart DB2 with a conditional restart specifying BACKOUT=NO to bypass the unit of recovery that is in-abort. At the time of the abend, registers 3 and 4 contain the 6-byte relative byte address (RBA) of the beginning of this unit of recovery. DB2 must read the log back to this point to complete the ROLLBACK of this unit of recovery. Login to see more
Comments |
| |
00D30021 - IBM DB2
The processing of the CONNECT statement at a DB2 remote server has failed. This is because acceptable CONNECT information was not conveyed in the distributed relational database architecture (DRDA) ACCRDB command sent by the local DB2 to the remote server. This reason code is issued by the following CSECT: DSNLTACC ; The remote server database access agent (DBAA) sends a DRDA reply message (for example, VALNSPRM) to the local DB2 which indicates the specific nature of the problem. The above reason code is sent in the server diagnosis area of the reply message. The DBAA awaits further DRDA commands from the local DB2.
The SQLCA returned in response to the CONNECT stat ... Login to see more
Comments |
| |
00D44031 - IBM DB2
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: v 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. v The DB2 system is not operational. This abend reason code is issued by the following CSECT: DSNMTV03 ; The DB2-DL/I batch support cannot continue and processing is terminated. User Response: Notify the system programmer.
It might be necessary to start the DB2 subsystem s ... Login to see more
Comments |
| |
00F3009C - IBM DB2
An RRS syncpoint exit was invoked for a DB2 agent by a task different than the task currently associated with the DB2 agent and the DB2 early code module installed on the system does not support this function. ; The RRS syncpoint request is abended. This will result in DB2 losing it’s connection with RRS. The DB2 subsystem must be stopped and then started again in order to establish a new connection with RRS.
Notify the system programmer. The version of the ... Login to see more
Comments |
| |
00F70003 - IBM DB2
The DB2 subsystem parameters specified that data sharing should be active. DB2 startup checking failed for either of two reasons: v The group and member names contained in the subsystem parameters are not equal to the group and member names contained in the DB2 ssnmMSTR JCL start procedure, or v The DB2 member is already active on another MVS system.; DB2 terminates.
Make sure the correct subsystem parameter load mod ... Login to see more
Comments |
| |
00E80051 - IBM DB2
An error was detected in the command that was used to start the DB2 subsystem. There are two conditions that can cause this error. If the -START DB2 command is in error, this abend results. Secondly, if the DB2 subsystem is not running (had never been started, or had been stopped), any DB2 command that is entered is interpreted as being a -START DB2 command. In this second case, the subsystem starts just long enough to discover that the command actually is not a -START DB2 command and then issues the abend. This abend reason code is issued by the following CSECT: DSNYSTRT ; The DB2 subsystem is terminated.
Reenter the command if it was entered in error; ot ... Login to see more
Comments |
| |
00D30020 - IBM DB2
The processing of the CONNECT statement at a remote server has failed. This is because acceptable CONNECT information was not conveyed in the distributed relational database architecture (DRDA) EXCSAT command sent by the local DB2 to the remote server. This reason code is issued by the following CSECT: DSNLTEXC ; The remote server database access agent (DBAA) sends a DRDA reply message (for example, MGRLVLRM) to the local DB2 which indicates the specific nature of the problem. The above reason code is sent in the server diagnosis area of the reply message. The DBAA awaits further DRDA commands from the local DB2.
The SQLCA returned in response to the CONNECT stat ... Login to see more
Comments |
| |
00C20203 - IBM DB2
DB2 cannot connect to a group buffer pool. The group buffer pool is not usable by this release of DB2. This DB2 subsystem is a member of a data sharing group containing DB2 members of different release levels. A later release level of DB2 specified an option for this group buffer pool that is not supported by the previous DB2 releases. The presence of this option makes the group buffer pool inaccessible to the previous DB2 releases. ; DB2 takes the following actions: v Unless already issued, message DSNB301E is sent to the console with this reason code to indicate that a connect failure occurred. v SQLCODE -904 (resource not available) is returned to the user with this reason code. The resource type and resource name are also returned.
Contact the system programmer. ; Do one of the fo ... Login to see more
Comments |
| |
00D3103C - IBM DB2
An attempt to allocate an LU6.2 conversation failed because the specified partner LU cannot support the LU6.2 SECURITY=SAME capability (that is, the LU6.2 Already-Verified security function). This abend reason code is issued by the following CSECT: DSNLVAAC ; The attempt to allocate an LU6.2 conversation fails, and the error is reported to the DB2 application that requested access to the distributed resource.
Notify your DB2 system programmer. ; DB2 will att ... Login to see more
Comments |
| |
00C30805 - IBM DB2
The caller’s connection with DB2 terminated because the CICS attachment facility is terminating in stop force mode. This reason code indicates that the CICS attachment facility is terminating because stop force was initiated. Stop force was probably initiated by the DSNC STOP FORCE command, the STOP DB2 MODE(FORCE) command, DB2 abnormally terminating, or the CICS attachment facility abnormally terminating. If a command was not used to cause stop force processing, abnormal termination dumps are produced by either DB2 if it is abnormally terminating, or by the CICS attachment facility if it is abnormally terminating. This abend reason code is issued by the following CSECTs: DSNCEXT1 DSN2CEXT1 ; All current requests are returned with an indication that the CICS attachment facility is terminating.
Wait until the CICS attachment facility is restart ... Login to see more
Comments |
| |