The DB2 portion of the abend report is produced whenever a program that accesses a DB2 database using DB2 for MVS/ESA Release 4.1.0 or above abends. The first page of the DB2 report displays the following information:
****A*********************************************** * DB2 8.1.0 RELATED INFORMATION FOR SUBSYSTEM D81A * B **************************************************** ********************************** * RETURN CODE FROM LAST SQL CALL * C ********************************** DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION ********************** * LAST SQL STATEMENT * ********************** STATEMENT LOCATION: D COLLECTION-ID OPT2DB2DEMO PACKAGE NAME DB2DEMO CONSISTENCY TOKEN 1841B4DE029F3FE6 SECTION NUMBER 00012 STATEMENT NUMBER 00755 SQL STATEMENT: E SELECT EMP , FIRSTNAME , LASTNAME , DEPT , MANAGER INTO :DCLEMPLOY.EMPLOY-EMP :EMP-IND-1.EMP-IND-EMP , :DCLEMPLOY.EMPLOY-FIRSTNAME :EMP-IND-1.EMP-IND-FNAME , :DCLEMPLOY.EMPLOY-LASTNAME :EMP-IND-1.EMP-IND-LNAME , :DCLEMPLOY.EMPLOY-DEPT :EMP-IND-1.EMP-IND-DEPT , :DCLEMPLOY.EMPLOY-MANAGER :EMP-IND-1.EMP-IND-MANAGER FROM EMPLOY WHERE EMP = :DCLJOB.JOB-EMP
The DB2 and the LAST SQL Statement portions of the abend report display the following information:
Displays the release of DB2.
Displays the DB2 subsystem-ID.
Displays the SQL return code, SQLCODE, and the message associated with that code. If SQLCODE is non-zero, the SQLSTATE value also displays.
Displays the location of the last SQL statement executed. (This is the last SQL statement before the ABEND or the abending SQL statement.)
If the DB2 program containing the last SQL statement is bound into a package, the location information includes the collection-ID, package name, consistency token, section number, and statement number (as shown in the example).
If the DB2 program is not bound into a package, the location information includes the plan name, DBRM name, consistency token, section number, and statement number.
In both cases, the statement number refers to the listing generated by the SQL precompile, not the COBOL compile listing.
Displays the last or abending SQL statement. If there is an associated cursor declaration, it is also displayed.
If the last SQL statement is not found in the DB2 catalog (for packages or plans which were bound remotely, for example), the statement type displays.
******************************** * SQL DESCRIPTOR AREA (OUTPUT) * A ******************************** LINE# LEVEL/FIELD NAME VALUE/LOCATION DEFINITION ------ ------------------------------- --------------------------------------- -------------------------------------- 001225 05 SQL-AVAR-LIST31 BLW=0001+0008B4 (000669EC) 001226 10 PRE-SQLDAID ? X 'E2D8D3C4C1404008' X(8) 001227 10 PRE-SQLDABC +236 S9(9) BINARY 001228 10 PRE-SQLN +5 S9(4) BINARY 001229 10 PRE-SQLLD +5 S9(4) BINARY 001230 10 PRE-SQLVAR BLW=0001+0008C4 (000669FC) 001231 12 SQLVAR-BASE1 BLW=0001+0008C4 (000669FC) 001232 15 SQL-AVAR-TYPE1 +501 S9(4) BINARY 001233 15 SQL-AVAR-LEN1 +2 . . . . . . *************************** * HOST VARIABLES (OUTPUT) * B *************************** LINE# LEVEL/FIELD NAME VALUE/LOCATION DEFINITION ------ ------------------------------- --------------------------------------- -------------------------------------- 000311 01 DCLEMPLOY BLW=0000+000940 (00065A78) 000312 10 EMPLOY-EMP +7 S9(4) BINARY 000322 01 EMP-IND-TABLE BLW=0000+000988 (00065AC0) 000323 10 EMP-IND-1 BLW=0000+000988 (00065AC0) 000324 20 EMP-IND-EMP +0 S9(4) BINARY 000331 10 EMP-IND-2(1) +0 S9(4) BINARY REDEFINES EMP-IND-1
The SQL Descriptor Area and the Host Variables portions of the report display the following information:
Displays the contents of the SQLDAs for the last SQL statement, if applicable. If the MERGEDB option is ON and symbolic information is available for the program, the SQLDA is mapped. Otherwise, the SQLDA is displayed in dump format.
Displays the contents of the host variables for the last SQL statement, if applicable. If relevant, the output host variables are displayed following the SQLDA for the output variables, and the input host variables are displayed following the SQLDA for the input variables. If the MERGEDB option is ON and symbolic information is available for the program, the host variables are mapped. Otherwise, the fully qualified names of the host variables are displayed, with the address, length, and data in dump format.
If DB2 objects are referenced by the last SQL statement, the names and types of the objects are displayed after the Host Variables. Similarly, if columns in a table or view are referenced, the contents of the referenced columns are displayed.
*************************** * SQL COMMUNICATIONS AREA * A *************************** LINE# LEVEL/FIELD NAME VALUE/LOCATION DEFINITION ------ ------------------------------- --------------------------------------- -------------------------------------- 000219 01 SQLCA BLW=0000+000848 (00065980) 000220 05 SQLCAID *SQLCA * X(8) 000221 05 SQLCABC +136 S9(9) BINARY 000222 05 SQLCODE +0 S9(9) BINARY 000223 05 SQLERRM BLW=0000+000858 (00065990) 000224 49 SQLERRML +0 S9(4) BINARY 000225 49 SQLERRMC SPACES X(70) 000226 05 SQLERRP *DSN * X(8) 000227 05 SQLERRD(1) +0 S9(9) BINARY OCCURS 6 <UNMERGED DATA FOR SQLERRD> X '0000000000000000FFFFFFFF00000000' LENGTH 20 (+000016) X '00000000' 000229 05 SQLWARN BLW=0000+0008C0 (000659F8) 000230 10 SQLWARN0 SPACES X
The SQL Communications Area portion of the report displays the following information:
Displays the contents of the SQLCA. If the MERGEDB option is ON and symbolic information is available for the program, data item information such as the data name, picture clause, and usage type are merged with the SQLCA storage. Otherwise, the address, length, and contents of the SQLCA are displayed in dump format.
The connection information is displayed, as shown in the following example:
************************** * CONNECTION INFORMATION * ************************** A CONNECTION MODE BACKGROUND B CONNECTION TYPE BATCH C CONNECTION ID BATCH D CORRELATION ID USER001D E AUTHORIZATION ID USER001
The Connection Information portion of the report displays the following information:
Displays the connection mode.
Displays the connection type.
Displays the connection ID.
Displays the correlation ID.
Displays the authorization ID.
The plan information follows the connection information:
***************************** * APPLICATION PLAN OPT2DEMO * A ***************************** BIND DATE/TIME 06 MAR,2008 14.57.54 B BOUND BY USER001 C BIND OPTIONS: E ACQUIRE(USE), CACHESIZE(3072), CURRENTDATA(YES), CURRENTSERVER(), DBPROTOCOL(DRDA), NODEFER(PREPARE), DEGREE(1), DISCONNECT(EXPLICIT), DYNAMICRULES(RUN), ENCODING CCSID(500), EXPLAIN(NO), FUNCTIONTS(2008-03-06-14.57.54.294632), GROUP MEMBER(), IMMEDWRITE(NO), ISOLATION(CS), KEEPDYNAMIC(NO), OPERATIVE(YES), OPTHINT(), OWNER(USER001 ), PATHSCHEMAS(), QUALIFIER(CAOPTII ), RELBOUND(L), RELEASE(DEALLOCATE), REOPT(NONE), SQLRULES(DB2), VALID(YES), VALIDATE(RUN) TABLE DEPENDENCIES: F CAOPTII.DEPART CAOPTII.DIVISN CAOPTII.EMPLOY CAOPTII.JOB CAOPTII.TITLES TABLE SPACE DEPENDENCIES: F CAOPTII.DEPART CAOPTII.DIVISN CAOPTII.EMPLOY CAOPTII.JOB
The Application Plan portion of the report displays the following information:
Displays the application plan name.
Displays the date and time when the plan was bound.
Displays the ID of the user who bound the plan.
Displays the comment associated with the plan, if applicable (not shown).
Displays the bind options.
Displays the database objects on which the plan is dependent.
The package information is displayed for each package in the plan. If the DB2ACTIV option is specified, package information is displayed only for the packages that are active at the time of the ABEND. An example showing the package information follows:
************************************* * PACKAGE SUMMARY FOR PLAN OPT2DEMO * ************************************* ******************** * PACKAGE DB2ADD * A ******************** B COLLECTION-ID OPT2DB2DEMO C BIND DATE/TIME 06 MAR,2008 14.57.52 D PRE-COMPILE DATE/TIME 06 MAR,2008 14.57.22 E CONSISTENCY TOKEN 1841B4DE1D8BFF84 F DBRM LIBRARY USER001.DBRMLIB.D810 H BIND OPTIONS: CREATOR(USER001), DBPROTOCOL(DRDA), CURRENTDATA(C), DEGREE(1), ENCODING CCSID(500), EXPLAIN(NO), FUNCTIONTS(2008-03-06-14.57.52.723939), GROUP MEMBER(), IMMEDWRITE(NO), ISOLATION(CS), KEEPDYNAMIC(NO), OPERATIVE(YES), OPTHINT(), OWNER(USER001), PATHSCHEMAS(), QUALIFIER(CAOPTII), RELBOUND(L), RELEASE(DEALLOCATE), REMOTE(NO), REOPT(NONE), SQLERROR(NOPACKAGE), TYPE(BINDPKG), VALID(YES), VALIDATE(RUN) PRE-COMPILE OPTIONS: I APOST, DEC(31), NOGRAPHIC, HOST(IBMCOB), NOTKATAKANA, PERIOD, VERSION() TABLE DEPENDENCIES: J CAOPTII.DEPART CAOPTII.DIVISN CAOPTII.EMPLOY CAOPTII.JOB CAOPTII.TITLES TABLE SPACE DEPENDENCIES: CAOPTII.DIVISN CAOPTII.EMPLOY CAOPTII.DEPART CAOPTII.JOB
The Package Summary portion consists of the following information:
Displays the package name.
Displays the collection ID.
Displays the bind date and time.
Displays the precompile date and time.
Displays the consistency token.
Displays the library where the DBRM resides.
Displays the comment associated with the package, if applicable (not shown).
Displays the bind options.
Displays the precompile options.
Displays the database objects on which the package is dependent.
Finally, CA SymDump Batch displays the information for DBRMs within the plan not bound into a package. If the DB2ACTIV option is specified, DBRM information is displayed only for the DBRMs that are active at the time of the ABEND.
********************************** * DBRM SUMMARY FOR PLAN OPT2DEMO * A ********************************** ***************** * DBRM DB2DEL * ***************** B PRE-COMPILE DATE/TIME 06 MAR,2008 14.57.26 C CONSISTENCY TOKEN 1841B4DF0D4A201A D DBRM LIBRARY USER001.DBRMLIB.D810 PRE-COMPILE OPTIONS: E APOST, DEC(31), NOGRAPHIC, HOST(IBMCOB), NOTKATAKANA, PERIOD, VERSION()
The DBRM Summary for Plan portion consists of the following information:
Displays the DBRM name.
Displays the precompile date and time.
Displays the consistency token.
Displays the library where the DBRM resides.
Displays the precompile options.
|
Copyright © 2011 CA.
All rights reserved.
|
|