IBM Support

OA44763: ACTIVATE FAILED DEVICES PINNED BY IOS FAST PIN PROCESSING 14/03/27 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When attempting to dynamically delete devices, the dynamic
    activate fails, with a reason=0151, due to devices being:
    pinned by the IOS FAST PIN PROCESSING:
    
    IOS1500I ACTIVATE RESULTS 614
    ACTIVATE FAILED - ERROR MESSAGE(S) ISSUED
    NOTE = 0100,SOFTWARE-ONLY CHANGE
     COMPID=SC1C3
    REASON=0151,CAN NOT DELETE DEVICE 2100
     DESCTEXT=DEVICE PINNED
              IOS FAST PIN PROCESSING
    
    The problem occurs as a result of the IOS_CMRTIME_MONITOR and
    IOS_IORATE_MONITOR reporting an exception during the same
    interval. From the SYSLOG, the following error messages will be
    seen:
    
    HZS0002E CHECK(IBMIOS,IOS_CMRTIME_MONITOR): 644
    IOSHC112E Analysis of command response (CMR) time detected
    one or more control units with an exception.
    
    HZS0002E CHECK(IBMIOS,IOS_IORATE_MONITOR): 645
    IOSHC132E Analysis of I/O rates detected one or
    more control units with an exception.
    
    When the IOS_CMRTIME_MONITOR and IOS_IORATE_MONITOR report an
    exception during the same interval, the fast pin count
    is not properly managed, which can lead to an activate failure
    due to the fast pin count.  Note, the monitor may have reported
    an exception hours, days, etc prior to the dynamic activate.
    
    PE INFORMATION:
    ===============
    Users Affected:
    Users with PTFs for APAR OA40548 applied at HBB7770(UA69335),
    HBB7780(UA69336) and HBB7790(UA69337) who use IBM Health
    Checker for z/OS and have both the IOS_CMRTIME_MONITOR and
    IOS_IORATE_MONITOR health check active.
    
    User Impact:
    APAR OA40548 provided New Function and introduced a problem
    which leaves a device UCB in the PINNED state when both an
    IOS_CMRTIME_MONITOR and an IOS_IORATE_MONITOR health check
    exception are found in the same monitor interval. When this
    happens the Fast PIN Count for the UCB is incremnted twice,
    however only decremented oncewhich leaves the device UCB
    with an outstanding UCB Fast PIN count. This becomes an
    impact if the device will be deleted or changed in such a
    way that it must be deleted and readded during a Dynamic
    ACTIVATE.  The ACTIVATE will fail in this case.
    
    If the APAR is not critical for production, it can be removed or
    either the IOS_CMRTIME_MONITOR or IOS_IORATE_MONITOR health
    check can be deactivated. IBM recommends chosing to deactivate
    the IOS_CMRTIME_MONITOR health check if running on a zEC12.
    
    To Deactivate a Health Check use:
       F hzsproc,DEACTIVATE,
       CHECK(IBMIOS,check_name)
    
    If the problem has already been experienced, Deactivating the
    health checks will not address already outstanding PIN counts.
    

Local fix

  • 1.Disable either the  IOS_CMRTIME_MONITOR or the
      IOS_IORATE_MONITOR to prevent additinal device experiencing
      an outstanding PIN count. The problem occurs only when both
      of these Health Checks are active so disabling 1 of them will
      avoid the problem. This will not clear up any outstanding PINs
      as a result of the problem.
      - If running on a zEC12 processor, we recommend disabling the
      IOS_CMRTIME_MONITOR as it is less likely to report an
      exception.
    
    2.Apply the ++APARS
    
    Note for level 2:  For a slip to modify the
    pin count of the ucb see z page.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users at HBB7770 and above with any of the   *
    *                 following PTFS applied - UA69335, UA69336    *
    *                 UA69337.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: An ACTIVATE command that causes devices *
    *                      to be deleted, may fail with            *
    *                      MSGIOS500I REASON=0151, if previously   *
    *                      Health Checker for z/OS detected an     *
    *                      IOS_CMRTIME_MONITOR exception           *
    *                      (MSGIOSHC112E) and an                   *
    *                      IOS_IORATE_MONITOR exception            *
    *                      (MSGIOSHC132E) during the same monitor  *
    *                      interval.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If Health Checker for z/OS detects an IOS_CMRTIME_MONITOR
    exception indicated via message IOSHC112E and an
    IOS_IORATE_MONITOR exception indicated via message IOSHC132E
    during the same monitor interval for the same control unit,
    it's possible that the IOS Storage Area Network Monitor may
    leave a UCB in the problem LSS with an outstanding Fast PIN
    count causing the device to remain PINNED.
    
    If an ACTIVATE is performed which causes the PINNED UCB to be
    deleted, the ACTIVATE will fail with message IOS500I,
    REASON=0151,CAN NOT DELETE DEVICE dddd
    DESCTEXT=DEVICE PINNED
    IOS FAST PIN PROCESSING
    

Problem conclusion

  • The IOS Storage Area Monitor module, IOSVSANM is being changed
    to ensure that when both an IOS_CMRTIME_MONITOR exception and
    an IOS_IORATE_MONITOR exception are detected in the same
    monitor interval for the same Logical Subsystem (LSS), an
    outstanding PIN will not be left on the UCB used for processing.
    
     KEYWORDS: HCHECKER/K
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    OA44763

  • Reported component name

    IOS

  • Reported component ID

    5752SC1C3

  • Reported release

    780

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-03-17

  • Closed date

    2014-04-03

  • Last modified date

    2014-05-02

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

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

    UA73077 UA73078 UA73079

Modules/Macros

  • IOSVSANM
    

Fix information

  • Fixed component name

    IOS

  • Fixed component ID

    5752SC1C3

Applicable component levels

  • R770 PSY UA73077

       UP14/04/16 P F404 «

  • R780 PSY UA73078

       UP14/04/16 P F404 «

  • R790 PSY UA73079

       UP14/04/16 P F404 «

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":"780","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 May 2014