Inconsistent data in a data sharing environment

As is true in the non-data-sharing environment, problems with inconsistent data in the data sharing environment might be caused by broken pages, inconsistent data pages and index pages, or down-level data sets.

One cause of inconsistent data occurs only in the data sharing environment: Db2 might be improperly maintaining communication or data coherency between members. If more than one group member returns incorrect output, it might be an indication of a buffer pool coherency problem. For diagnosis of this problem, you must provide merged logs from all members of the data sharing group. Use the DSN1LOGP utility to obtain them. To format the merged logs, include the following in your DSN1LOGP job:

  • A GROUP DD statement in the JCL. This statement names a BSDS for one member of the data sharing group. Db2 can find the rest of the information from that one BSDS.
  • The option LRSNSTART in the DSN1LOGP statement.

You might also be asked to provide the following for all members of the data sharing group:

  • A dump of the group buffer pool (GBP) and shared communications area (SCA) list structures.

    You can use an z/OS® DUMP command similar to this one to obtain a dump of each group buffer pool:

    DUMP COMM=(GBPx-dump-name)
    nnn,STRLIST=(STRNAME=GBPx-structure-name,
        CONNAME=conname,ACCESSTIME=NOLIMIT,
        (STGCLASS=ALL,COCLASS=ALL,EDATA=SER)),END

    To obtain a dump of the shared communications area, use a DUMP command similar to this one:

    DUMP COMM=(SCA-dump-name)
    nnn,STRLIST=(STRNAME=SCA-structure-name,
        (LISTNUM=ALL,EDATA=SER)),END
  • Dumps of all Db2 and IRLM address spaces
  • Console logs
  • SYS1.LOGREC data sets