IBM Support

OA47307: MPC HANGS PREQC STATE AT ACTIVATION. LOGS SHOW IST574E AND INOP ON THIS SIDE - INOP AND VARY INACT ON THE OTHER SIDE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • MPC activation logs/dumps show:
    SideA:  IST574E Read device
            IST1222I Read device INOP
            IST1578I INOP ISTTSCXI CODE 104
            Activation is hung
    SideB:  IST1222I Write device INOP
            IST1578I INOP ISTTSC8X CODE 022
            IST1578I INOP ISTTSC8X CODE 009
            IST1136I VARY INACT SCHEDULED
            MPC becomes inact
    ----
    The doc is showing XID0's were exchanged successfully - but an
    error occurred on subsequent XID7 exhanges. This is not
    expected - and both sides should have become INACT at this
    point.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All using MPC/AHHC connections.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * MPC HANGS PREQC state after XID7 timeout.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * FIN                                                          *
    ****************************************************************
    The problem may be summarized as follows:
    1) An MPC/AHHC connection is being activated.
    2) The XID0 exchanges over the subchannels is successful.
    3) The low side of the connection initiated XID7 exchange.
    4) In this failure, message IST574E indicating a START I/O
    TIMEOUT occurred for the read subchannel.
    5) After this failure, the MPC/AHHC connection hung incorrectly
    hung in PREQC state.
    
    NOTE: The root cause of the I/O failure will need to be
    investigated and corrected.  However VTAM should have
    inactivated the MPC PU after the failure occurred.
    

Problem conclusion

Temporary fix

Comments

  • The solution for this APAR is included in CS for zOS Version 2
    Release 2.
    

APAR Information

  • APAR number

    OA47307

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    210

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-13

  • Closed date

    2015-03-16

  • Last modified date

    2015-09-25

  • 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

  • R210 PSN

       UP

[{"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":"210","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 September 2015