Collecting data for IRLM hangs

Db2 uses the IRLM subsystem to control the locking of data. To diagnose IRLM waits and hangs, collect IRLM supervisor call (SVC) dumps, SYSLOG, and LOGREC.

Before you begin

To diagnose IRLM problems, you must have the appropriate authorization to collect data from different z/OS® components.

About this task

The following messages might be displayed on the z/OS console (SYSLOG):

  • DXR167E indicates that IRLM detected a hang. Diagnostic information must be collected before IRLM no longer detects delayed processes.
  • IXL040E with reference to the IRLM address space in CONNECTOR NAME, JOBNAME, and ASID message tokens indicates that z/OS detected a possible hang with IRLM.

Procedure

To collect IRLM diagnostic information when a message indicates an IRLM hang:

  1. Capture the IRLM SVC dump for your Db2 environment by setting up a SLIP trap.
    • If you are not in a data sharing environment, set up and enable a SLIP trap to capture associated SVC dumps:
      SLIP SET,MSGID=message-id,ACTION=SVCD,ID=trapid,
      JOBLIST=(ssnmIRLM,ssnmMSTR,ssnmDBM1),
      SDATA=(XESDATA,COUPLE,PSA,LSQA,LPA,GRSQ,RGN,CSA,SQA,SUM,TRT,ALLNUC),END
      

      Where:

      • message-id is the message that indicates the hang, (for example DXR167E or IXL040E)
      • trapid is the trap identifier
      • ssnmIRLM,ssnmMSTR,ssnmDBM1 are the address spaces to be dumped
    • If you are in a data sharing environment, set up and enable an SLIP trap to capture associated SVC dumps:
      SLIP SET,MSGID=message-id,ACTION=SVCD,ID=trapid,
      JOBLIST=(XCF*,ssnmIRLM,ssnmMSTR,ssnmDBM1),
      SDATA=(XESDATA,COUPLE,PSA,LSQA,LPA,GRSQ,RGN,CSA,SQA,SUM,TRT,ALLNUC),
      REMOTE=(JOBLIST,SDATA),END
      

      Where:

      • message-id is the message that indicates the hang, (for example DXR167E or IXL040E)
      • trapid is the trap identifier
      • XCF* is the value that you specify for the Cross System Coupling Facility name using wildcards
      • ssnmIRLM,ssnmMSTR,ssnmDBM1 are the address spaces to be dumped
  2. Collect any abend dumps with JOBNAME ssnmIRLM for ABEND=S026, REASON=08118001.
  3. Collect the SYSLOG, which might contain messages that indicate the source of the problem.
  4. Collect the LOGREC, which might contain messages that indicate the source of the problem.