IBM Support

OA32369: ACTPU FOR SWITCHED PU REMAINS IN PDISC STATE, FAILS TO ACTIVATE WITH IST380I ACTPU REQUEST ERROR MESSAGE AND SENSE 08010000

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In certain conditions, the ACTPU processing for a switched PU
    might fail with the following message:
     IST380I ERROR FOR ID = xxxxxx - REQUEST: ACTPU, SENSE: 08010000
    A display of the switched PU resource will show state of PDISC
    to indicate pending discontact response and the PU fails to
    activate and remains hung.
    The associated LSNCB will show LSNFSM value of x'9C' for
    LSN_SW_CONNECT_REQUESTED state and the RCCRNAA bits in RCCBITAN
    flags for the switched PU control block will show value of x'4'
    for RCCRNAT4 to indicate that CONTACTED x'0A' has been received.
    The VIT trace will show that the switched PU got sidequeued
    (non-zero LSNSIDEQ) and the PAB did not get scheduled to update
    the switched PU to the correct state of CONCT.
    

Local fix

  • None. There is no certainty that forced deactivation and
    re-activation of the switched resources will work.
    KEYWORDS:
    IST380I ACTPU SWITCHED PU PUT2 PUT21 SENSE 08010000 PDISC
    CONTACTED 0A LSN_SW_CONNECT_REQUESTED LSNSIDEQ ISTACCQ4
    RCCRNAT4 Q4CTD0A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All using dependent PUs (PU T2.0)            *
    *                 attached as switched PUs through XCA LAN.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: PU T2.0 hangs in PDISC state after      *
    *                      ACTPU failure (SENSE 08010000).         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem is summarized as follows:
    
    1) A switched PU T2.0 is being dialed:
    
     V NET,DIAL,ID=puname
    
     IST590I CONNECTOUT ESTABLISHED FOR PU puname ON LINE linename
     IST380I ERROR FOR ID = puname - REQUEST: ACTPU, SENSE: 08010000
    
    2) During CONTACTED processing, module ISTACCQ4 initiates an
       ACTPU flow to activate the SSCP-PU session.  The ACTPU
       request is eventually queued by SESSER to the LSNCB PC PAB.
    
    3) Module ISTLSC6V rejects the ACTPU with SENSE 08010000 because
       the LSNFSM (LSNCB link state) is not in station active state
       prior to the arrival of the ACTPU request.  In this problem,
       the LSNCB PU PAB (ISTLSCLA) has not run to change the
       LSNFSM to station active (from CONTACTED processing).
    
    4) A subsequent display of the PU shows it is hung in PDISC
       state (Could be PFDSC state).
    
    5) A similar problem exists if the PU dials-in to VTAM:
    
     IST590I CONNECTIN ESTABLISHED FOR PU puname ON LINE linename
     IST380I ERROR FOR ID = puname - REQUEST: ACTPU, SENSE: 08010000
    

Problem conclusion

  • The following changes have been made:
    
    ISTLSC6V - Has been changed to check the LSNCB_CONTACT_COMPLETE
               bit.  If ON, the LSNFSM is set to
               LSN_SW_STATION_ACTIVE.  This code is added in the
               event the LSNCB PU PAB has not yet run prior to the
               LSNCB PC PAB being dispatched to process the ACTPU
               request.
    ISTLSCNG,
    ISTLSCNH - Both modules have been changed to set the
               LSNFSM to LSN_SW_STATION_ACTIVE for PU T2.0
               devices after a CONTACTED request is sent to PUNS.
    
    ISTLSCLJ - Modified segment SWITCHED to process a DISCONTACT
               request if the LSNFSM is LSN_SW_CONNECT_REQUESTED
               state and the LSNLFLOW bit is ON, indicating a
               positive Connect.confirm has been received.  If
               LSNLFLOW is OFF, the DISCONTACT will be sidequeued
               until the TQE timing the Connect flow expires.
    
    ISTACCQ4,
    ISTLSC6I,
    ISTLSCSN,
    ISTLSCLA - Included for maintenance purposes.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    OA32369

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    1A0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-03-19

  • Closed date

    2010-04-13

  • Last modified date

    2010-05-04

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

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

    UA53596 UA53597 UA53598 OA32797

Modules/Macros

  • ISTACCQ4 ISTLSCLA ISTLSCLJ ISTLSCNG ISTLSCNH
    ISTLSCSN ISTLSC6I ISTLSC6V
    

Fix information

  • Fixed component name

    VTAM V4 MVS/ESA

  • Fixed component ID

    569511701

Applicable component levels

  • R1A0 PSY UA53596

       UP10/04/27 P F004 Ž

  • R1B0 PSY UA53597

       UP10/04/27 P F004 Ž

  • R190 PSY UA53598

       UP10/04/27 P F004 Ž

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

Document Information

Modified date:
04 May 2010