IBM Support

PK98021: AT DASD H/W ERROR, ADS STOP PROCESS HUNG BETWEEN TWO IMSS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • At DASD H/W error, ADS STOP process hung between two IMSs.
    Many regions in IMS3 are waiting for lock and SYNC Share latch.
    DBFLIRL0 ITASK hold many CI locks for OTHREAD DMHRs.
     These DMHRs are waiting for OTHREAD SRB.
    ----------------------------------------------------------------
      DMACOTHQ=0001D703 18CE37B8
               ====     --------> 260 DMHRs are queued.
      Due to active OTHREAD for DEPO40 is waiting on DBFMER00,
      DBFFORI0 cannot process other OTHREAD DMHRs for this AREA.
    ----------------------------------------------------------------
    This is a deadlock situation between 4 ITASKs in two IMSs as
    follows.
    -------------------
    IMS3: OTHREAD DMHR was queued on DBFMER00 and DBFMER00 is
          waiting for AREA lock for DEPO40, which is held by IMS1.
    IMS1: DBFCST00 ITASK hold AREA lock for DEPO40 and is waiting
          for VUNLOAD lock, which is held by IMS3
    IMS3: DBFCST00 ITASK hold VUNLOAD lock and is waiting for SYNC
          EX Latch.
    IMS3: CHKPT ITASK hold SYNC EX latch and is waiting for OTHREAD
          completion.
    ----------------------------------------------------------------
    <<< IMS3 >>>
    IMS3-1;
     SAP AT 1AD87580             FLG-C8100002 40080A00 DPNO-0097BD4F
                     POST-40D9E2E7 ECB-16FBB060 TYPE-GPST
     DBFMER0007/11/06PK23227 ABCD                      +00B8
     MERMAIN                                           +0170
     DBFLRH00-910-05/08/08-16.36PK34059 ABCDEFG        +057A
      VECTOR.G.*DFSLMGR0-910-05/08/08PK34059 ABCDEG    +????
     UNKNOWN                                           +????
     ==> OTHREAD of DEPO40 got I/O error.
     ==> Waiting for AREA lock for DEPO40.
          ==> Owner is DBFCST00 ITASK in IMS91LP1. ==> IMS1-1
    -----------------
    IMS3-2;
     SAP AT 1ADF6D60             FLG-C8100002 40080800 DPNO-0094F394
                     POST-80C800DB ECB-1AD9A060 TYPE-GPST
     DBFCST00-910-08/19/05-16.08PK08720 0ACDE          +020C
     DBFARD2001/09/07PK34202 ABCD                      +0ACE
     DBFMFLG009/08/05PK10754 ABCDE                     +014A
     GETSYNLE                                          +0050
     DBFSYNL003/12/0811.30PK17084 ABC                  +0068
     GET_EXC                                           +00D2
     DFSISERW
     ==> STOP ADS process for DEPO49
     ==> Hold VUNLOAD lock and Update AREA lock of DEPO49
     ==> Waiting for SYNC EX latch
          ==> Owner is CHKPT ITASK.    ==> IMS3-3
    ----------------
    IMS3-3;
     SAP AT 164CB040             FLG-D0050000 40000000 DPNO-0093712B
                     POST-80C800BB ECB-00C86060 TYPE-ZPST
     DFSRCRT0-10/30/03-11.22                           +018E
     DFSRCP00-10/24/08-PK66280 0AB                     +0A4C
     DFSRCP10-11/04/05-16.09PK13463 AB                 +0294
     DBFCHKP0-08/06/0415.06PQ90744 AB                  +00EA
     CHKPDMHR                                          +005C
     DFSIWAIT
     ==> Hold EX SYNC latch.
     ==> CHKPT ITASK is waiting for OTHREAD I/O completion
           OTHREAD DMHR was pending on DFMER00 => IMS3-1
    ----------------------------------------------------------------
    <<< IMS1 >>>
    IMS1-1
     SAP AT 1AE1CD60             FLG-C8100002 40080A00 DPNO-0056D8B9
                     POST-80CA70DB ECB-1AD2A060 TYPE-GPST
     DBFCST00-910-08/19/05-16.08PK08720 0ACDE          +020C
     DBFARD2001/09/07PK34202 ABCD                      +0502
     DBFXSVC008/19/05PK08720 AB                        +021E
     DBFLRH00-910-05/08/08-16.36PK34059 ABCDEFG        +057A
      VECTOR...*DFSLMGR0-910-05/08/08PK34059 ABCDEG    +????
     ==> hold update AREA lock for DEPO40
     ==> waiting for VUNLOAD lock.
           ==> Owner is DBFCST00 ITASK in IMS91LP3.  ==> IMS3-2
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMSFP V11 users are affected.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: At DASD H/W error, ADS STOP process     *
    *                      hung between two IMSs. Many regions in  *
    *                      IMS are waiting for lock and SYNC       *
    *                      Share latch. DBFLIRL0 ITASK hold many   *
    *                      CI locks for OTHREAD DMHRs.             *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    At DASD H/W error, ADS STOP process hung between two IMSs.
    Many regions in IMS are waiting for lock and SYNC Share latch.
    DBFLIRL0 ITASK hold many CI locks for OTHREAD DMHRs. These DMHRs
    are waiting for OTHREAD SRB.
    
    ----------------------------------------------------------------
    
    DMACOTHQ=0001D703 18CE37B8
    ==== --------> 260 DMHRs are queued.
    Due to active OTHREAD for DEPO40 is waiting on DBFMER00,
    DBFFORI0 cannot process other OTHREAD DMHRs for this AREA.
    
    ----------------------------------------------------------------
    
    This is a deadlock situation between 4 ITASKs in two IMSs as
    follows.
    
     IMS3: OTHREAD DMHR was queued on DBFMER00 and DBFMER00 is
           waiting for AREA lock for DEPO40, which is held by IMS1.
     IMS1: DBFCST00 ITASK hold AREA lock for DEPO40 and is waiting
           for VUNLOAD lock, which is held by IMS3
     IMS3: DBFCST00 ITASK hold VUNLOAD lock and is waiting for SYNC
           EX Latch.
     IMS3: CHKPT ITASK hold SYNC EX latch and is waiting for OTHREAD
           completion.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    
    When I/O error occurs during command /STO AREA, /VUN processing,
    the othread DMHR will be enqueued to htmg errq to be process
    later.  In case it failed to obtained the AREA lock, it will
    continue to try getting the lock before enqueued the othread
    to htmg errq.  The reenq count will be increased by 1 each
    time the code enter the REENQ routine due to failure getting
    the AREA lock. If the reenq count exceeds 500, it aborts the
    wait for AREA lock, and returns with error which will break
    the deadlock.
    
    The following modules were changed:
    
       DBFMER00 - The fixed codes will force ADS stop when it
                  exceeded the REENQ retry limit.
       DBFFORI0 - The fix codes will clear the REENQ retry counter.
       DBFMIOE0 - The fix codes will clear the REENQ retry counter.
       DBFVOCI0 - The fix codes will clear the REENQ retry counter.
       DBFVXOC0 - The fix codes will clear the REENQ retry counter.
       DBFVXOE0 - The fix codes will clear the REENQ retry counter.
    
    The following macros/copy files were changed:
    
       DBFDMHR - Added DMHRRENQ. This is a REENQ retry counter.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PK98021

  • Reported component name

    IMS V11

  • Reported component ID

    5635A0200

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-10-06

  • Closed date

    2009-12-03

  • Last modified date

    2010-01-05

  • APAR is sysrouted FROM one or more of the following:

    PK95700

  • APAR is sysrouted TO one or more of the following:

    UK52556

Modules/Macros

  • DBFDMHR  DBFFORI0 DBFMER00 DBFMIOE0 DBFVOCI0
    DBFVXOC0 DBFVXOE0
    

Fix information

  • Fixed component name

    IMS V11

  • Fixed component ID

    5635A0200

Applicable component levels

  • R100 PSY UK52556

       UP09/12/10 P F912 Ž

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 January 2010