IBM Support

OA46037: APPLICATIONS REQUESTING A SYSPLEXPORT ARE HUNG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • .
    TCPIP on this system is configured with a Distributed Dynamic
    VIPA that has SYSPLEXPORTS enabled.  The potential exists for
    applications that are requesting an ephemeral port requiring
    Coupling Facility activity to become hung waiting for a port to
    be assigned.  All other applications making this request after
    this point will also hang.
    
    Other symptoms:
    
    If the SMF Job Wait Time (JWT value in the SMFPRMxx PARMLIB
    member) is enabled, the applications in this state will begin
    receiving S522 ABENDs.  These events will be accompanied by the
    following set of messages:
    
       IST931I SYMPTOM STRING = AB/S0522 LVLS/6xx RIDS/ISTAPCFR#R1
       IST931I SYMPTOM STRING = PIDS/5695-11701 ADRS/xxxxxxxx
                                RIDS/UNKNOWN
       IST931I SYMPTOM STRING = #L RIDS/ISTAPCSU LVLS/1x.xxx
                                PTFS/xxxxxxx
       IST931I SYMPTOM STRING = REGS/0xxxx ASID/xxxx
       IST314I END
    
       The ASID value will be for the VTAM address space.
    
    Other conditions terminating an affected application (such as an
    S222 ABEND from an operator CANCEL) will also produce these
    messages.
                                                                   .
    

Local fix

  • .
    When this occurs, VTAM (and all using applications, including
    TSO and TCPIP) will need to be recycled to clear this condition.
    
    The problem can be avoided by not using SYSPLEXPORTS.  This is
    typically not an option most systems where this has been
    configured (such as those using the DVIPA as a
    TCPSTACKSOURCEVIPA address).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users that connect to TCP/IP coupling                    *
    * facility structures EZBEPORT and EZBDVIPA.                   *
    * SYSPLEXDS                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Application requesting a sysplexport were                    *
    * hung.                                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the PTF when it is available.                          *
    ****************************************************************
    This problem may be described as follows:
       1. TCPIP application was using sysplexports.
       2. TCPIP issued VTAM request to use the port.
       3. ISTFSVPC received control to process the request.
           It issued SETFRR request to setup the FRR to set
           up the recovery environment. It also issued SETVRR
           to put the retry routine FSVPC_VRR on stack. It
           issued GETLOCK to obtain the EZBEPORT structure
           lock.
       4. ISTFSVLG received control to obtain the lock. It
           obtained the SSVCBLCK lock with the exclusive
           option. It also obtained the SSV structure lock.
       5. TCPIP application abended for some reason.
       6. FSVPC_VRR received control to retry the error.
           It freed the SSV structure lock successfully.
           It did not free the SSVCBLCK lock in error.
       7. Other processes needed the SSVCBLCK lock.
           They were waiting in a queue for the SSVCBLCK lock.
           This cause a wait for all TCPIP applications wanted to
           use sysplexports.
    

Problem conclusion

  • FSVPC_VRR routine of ISTFSVPC has been changed
    to release the SSVCBLCK correctly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA46037

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-09-17

  • Closed date

    2014-09-30

  • Last modified date

    2014-12-01

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

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

    OA46100 UA74993

Modules/Macros

  • ISTFSVPC
    

Fix information

  • Fixed component name

    VTAM V4 MVS/ESA

  • Fixed component ID

    569511701

Applicable component levels

  • R210 PSY UA74993

       UP14/11/04 P F411 ¢

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":"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:
01 December 2014