IBM Support

OW05684: DSPU STAYS IN PCTD2

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Several DSPU's are remain in PCTD2 after VTAM INACT/ACT.
    Asy. channel status will not be processed correctly. it appears
    that the DE will be lost within vtams ios.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All with Down Stream PUs (DSPUs) hung off of *
    *                 a 3174 PU 2.0.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: DSPUs off of 3174s hang in PCTD2 state. *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The scenario is as follows:
    
    1) a CONNECT is sent to a DSPU off of a 3174.
    2) the 3174 responds DE/UC
    3) MVS issues a SENSE CCW on VTAM's behalf.
    4) 3174 responds with sense Not Initialized and Abort
    5) a DSPU now wants to become active and 3174 sends in
       Asynchronous DE/UC
    6) MVS issues a SENSE CCW on VTAM's behalf.
    7) 3174 responds with sense Not Initialized - this
       is a wake up to VTAM to reissue the connect in 1).
    8) the Asynch DE/UC in 5) is processed in VTAMs Attention
       routine running in Master's ASID and processing completes
       BEFORE the interrupt for the CONNECT in 1).
    9) As VTAM's attnetion routine thinks the device is
       busy (NCBBUSYF=1 because the interrupt in 1) hasn't
       completed), the Asynch DE/UC to wake up the device is
       discarded.
    10) the device hangs in PCTD2.
    
    Normally, the interrupt from the CONNECT in 1) will complete
    before the Asynchronous DE/UC in 5).
    
    VTAM needs to remember that this ASYNCH DE/UC has come in
    if the device is in Contact Pending state.
    

Problem conclusion

  • ISTTSCLA has been changed to remember the Asynchronous DE/UC
    with sense of Not Initialized when it is received in Connect
    Pending state (x'04').  When the NCBPUPAB (ISTTSC2I) processes
    the completion of the CONNECT CCW it will check to see if
    the Asynchronous DE/UC has been received.  If it has, a new
    CONNECT CCW will be issued.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OW05684

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    101

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1994-06-03

  • Closed date

    1994-06-14

  • Last modified date

    1994-11-25

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

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

    UW08317 UW08318 OW07143

Modules/Macros

  • ISTICNCB ISTTSCLA ISTTSC2I
    

Fix information

  • Fixed component name

    VTAM V4 MVS/ESA

  • Fixed component ID

    569511701

Applicable component levels

  • R101 PSY UW08317

       UP94/08/10 P F408

  • R201 PSY UW08318

       UP94/08/26 P F408

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":"101","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":"101","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 November 1994