IBM Support

II09147: CHANGES TO DB2 DIAGNOSIS GUIDE & REFERENCE LY27-9618-00 THAT DID NOT MAKE V4.1 GA PUBS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • Do NOT CLOSE this APAR.  Leave it in INTRAN status.
    =====================================================
    5740xyr00 DB2 R410 V4
    This APAR documents changes to the DB2 Diagnosis Guide and
    Reference LY27961800 which did not make Version 4.1 GA pubs.
    ================================================================
    Version 4 Book Title: Diagnosis Guide and Reference
    Pages: 10
    Change Description:
    Change the last line on page 10 to:
    
    Control block field descriptions, which were formerly part
    of this book, have been moved into flat file
    DSNWCBDS in data set DSN410.SDSNSAMP.
    ============================================================
    Version 4 Book Title:  Diagnosis Guide and Reference
    Pages:  164
    Change Description:
    Change this statement:
    
    DB2 global trace data written to GTF has a GTF ID of X'0FC8'
    and an FID of '00'.
    
    to this:
    
    DB2 global trace data written to GTF has a GTF ID of X'0FB9'
    and an FID of '00'.
    ============================================================
    Version 4 Book Title: Diagnosis Guide and Reference
    Pages: 166
    Change Description:
    
    Administration Guide, Version 3, Appendix E, contained
    information on how to load the contents of file
    DSNWMSGS into a DB2 table.  That information was
    removed from Administration Guide because DSNWMSGS
    is classified as diagnosis, modification, and tuning
    (DMTI), and non-DMTI documents cannot point to DMTI
    documents.  The information on loading DSNWMSGS
    still needs to be somewhere, however, so it has been
    moved to the file DSNWMSGS itself, and a pointer to it
    has been placed in Diagnosis Guide and Reference,
    which is DMTI.
    ============================================================
    Version 4 Book Title:  Diagnosis Guide and Reference
    Pages:  321, 324, 325, 326, 328, 329, 331, 332, 333
    
    Change all descriptions of PGLOGID to this:
    
    07  PGLOGID   CHAR(1)     For non-data-sharing, whether the
                              log RBA is valid.  For data
                              sharing, whether the log RBA is
                              valid, and the ID of the log sub-
                              system.
    
                  0000 0000   For non-data-sharing, the log RBA
                              is valid.
    
                  nnnn nnnn   Log RBA is valid.   nnnn nnnn
                              represents the data sharing member
                              ID.   nnnn nnnn  can be  0000 0001
                              through  1111 1110 .
    
                  1111 1111   For non-data-sharing and data
                              sharing, the last update to the
                              page was not logged; RBA is not
                              valid (last update was LOAD or
                              REORG).
    
    Change all descriptions of IPLOGID to this:
    
    10  IPLOGID   FIXED(8)    For non-data-sharing, whether the
                              log RBA is valid.  For data
                              sharing, whether the log RBA is
                              valid, and the ID of the log sub-
                              system.
    
                  0000 0000   For non-data-sharing, the log RBA
                              is valid.
    
                  nnnn nnnn   Log RBA is valid.   nnnn nnnn
                              represents the data sharing member
                              ID.   nnnn nnnn  can be  0000 0001
                              through  1111 1110 .
    
                  1111 1111   For non-data-sharing and data
                              sharing, the last update to the
                              page was not logged; RBA is not
                              valid (last update was through
                              a utility).
    ============================================================
    Version 4 Book Title: Diagnosis Guide and Reference
    Pages: 329, 335, 336, 349
    Change Description:
    
    On page 329, in the description of PGFLAGS:
    - Change
      ..01 1...           Page is a header page
      to
      ..01 1...           Page is a type 1 header page
    - Add
      ..10 0...           Page is a type 2 header page
    
    On page 335, in Table 70 (Type 2 Index Space Map Header),
    replace
    00      *       CHAR(12)       Common page declares (DSNDPG)
    with descriptions of fields PGCOMB, PGLOGRBA, PGLOGID,
    PGNUMBER, and PGFLAGS.
    
    On page 336, in Table 73 (Type 2 Index Physical Index
    Page Header), replace
    00      *       CHAR(12)       Common page declares (DSNDPG)
    with descriptions of fields PGCOMB, PGLOGRBA, PGLOGID,
    PGNUMBER, and PGFLAGS.
    
    On page 349, in Descriptor of a Check Constraint, add
    the offsets for all fields in OBDCC.
    ============================================================
    Version 4 Book Title: Diagnosis Guide and Reference
    Pages: 342-343
    Change Description:
    
    Delete the information at offsets 06 and 0A. Recalculate
    the offsets for the fields following the deleted fields.
    Correct the offset and non-data sharing value for LGRMEMB.
    ============================================================
    Version 4 Book Title:  Diagnosis Guide and Reference
    Pages:  345
    Change Description:
    
    In table SYSIBM.SYSUTILX, add this row after the row
    that describes SEQNO:
    18   *           CHAR(12)       Reserved
    In table SYSIBM.SYSUTILX, change the row that describes
    CHECKPOINT to this:
    24   CHECKPOINT  VARCHAR(4000)  The overflow checkpoint/
                                    restart information
    =============================================================
    Version 4 Book Title: Diagnosis Guide and Reference
    Pages: 351
    Change Description:
    
    Under the heading "RECORD EXTENSION FOR SEGMENTED TABLES,"
    changed:  "Each segment in a segmented table space contains
    the following data area."
    
    To:  "Each table in a segmented table space contains the
    following data area."
    ============================================================
    Version 4 Book Title: Diagnosis Guide and Reference
    Pages: 420
    Change Description:
    This procedure replaces the current procedure for finding
    the CICS LOT in a formatted dump:
    
    Use one of these methods to find the LOT in a CICS formatted
    dump:
    
    - If the abend occurred in the CICS attachment facility,
      register 9 usually contains the address of the LOT.  Look
      at the data area pointed to by register 9.  If the
      first 8 bytes are 'DSNCLOT ' for CICS 3.3 and below,
      or 'DSN2LOT ' for CICS 4.1 and above, you have found the
      LOT.
    
    - Find the TCATIEBA field in the Task Control Area (TCA).
      TCATIEBA contains the address of the first of one or
      more chained Task Interface Element (TIE) blocks.  The
      resource manager name field, DWERMNME, for DB2's TIE
      contains the string 'DSNCSQL '.  The LOT comes
      immediately after DB2's TIE.
    
    - If your CICS dump is a system dump, your CICS level is 3.3
      or higher, and you have IPCS, you can format the TIE and
      the LOT using the subcommand:
      VERBEXIT CICSnn0 'UEH=2'
      where nn is the CICS release level.
    
    The TCA and TIE control blocks are documented in CICS/MVS
    Data Areas and CICS/ESA Data Areas.  Use of IPCS with CICS
    dumps is described in CICS/ESA Operations and Utilities
    Guide.
    ============================================================
    Version 4 Book Title:  Diagnosis Guide and Reference
    Pages:  441-445
    Change Description:
    
    In table 198, Correlation Identifiers, in the Correlation
    ID column, if the first 3 characters are 003, 004, 016, or
    026, change all instances of an underscore (_) to a blank.
    ============================================================
    Version 4 Book Title: Diagnosis Guide and Reference
    Pages: 444
    Change Description:
    
    In table 198, Correlation Identifiers, change
    020.DBcommand_05 to 020.DBCMD_05 and
    020.DBcommand_06 to 020.DBCMD_06.
    ============================================================
    Version 4 Book Title:  Diagnosis Guide and Reference
    Pages:  486-487
    Change Description:
    
    Add this CAF trace message:
    
    DSNA815I DSNACA70 TCB=ADDRESS FDBKEIB=EIB-ADDRESS SSID=SSID
        GATT=GROUP-ATTACH-NAME GRPN=GROUP-NAME MBRN=MEMBER-NAME
    
    EXPLANATION:  This message displays the address and contents
    of the DB2 environment information control block (EIB).  DB2
    displays this message when the EIB address is not 0.
    
    Modify CAF trace message DSNA825I as shown here:
    
    DSNA825I DSNACA70 TCB=ADDRESS CABSSID=SSID CABREL=RELEASE
        CABDECPP=ADDRESS EIBPARM=EIB-ADDRESS
    
    EXPLANATION:  This message lists the current values in
    DSNHDECP, which is link edited with the call attachment
    facility main load module, DSNACAF.  These values are used
    as defaults on implicit connection requests.
    ==============================================================
    Version 4 Book Title:  Diagnosis Guide and Reference
    Pages:  486, 487
    Change Description:
    
    In message DSNA814I, change RC2=retcode to RC2=reascode.
    In message DSNA822I, change CABFRC2=retcode to
    CABFRC2=reascode.
    ============================================================
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II09147

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1995-12-19

  • Closed date

  • Last modified date

    1999-07-22

  • 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:
22 July 1999