OA36610: EE CONNECTION DOES NOT AUTOMATICALLY RECOVER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An EE connection exists between a VTAM and another EE endpoint.
  The switched PU for the connection on VTAM is defined with
  DWINOP=YES and REDIAL=FOREVER.  The partner EE host is brought
  down.  The EE connection on VTAM INOPs and attempts to recover
  the connection.  Because the adjacent host is down the initial
  recovery fails.  VTAM then begins to redial the connection
  forever at the interval specified.  After a few attempts VTAM
  issues the following message:
  IST493I SOFT INOP FOR ID=swpuname OVERRIDDEN BY REQDISCONT
  .
  After this message the switched PU does not attempt to redial
  the connection.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:   All using Enterprise Extender (EE) with    *
  *                 DWINOP=YES coded.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION:   An Enterprise Extender switched PU    *
  *                      failed to automatically recover after   *
  *                      an INOP.  The following message was     *
  *                      issued when the redial attempts stopped *
  *                      IST493I SOFT INOP FOR ID=swpuname       *
  *                      OVERRIDDEN BY REQDISCONT.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem can be summarized as follows:
  1. An EE connection existed between a VTAM and another EE
     endpoint.  The switched PU for the connection on VTAM was
     defined with DWINOP=YES, REDIAL=FOREVER, and DISCNT=NO.
  2. The partner EE host was brought down.  Then, the EE
     connection on VTAM INOPed and attempted to recover.
  3. Because the adjacent host was down, the initial recovery
     failed.  VTAM then began to redial the connection forever,
     at the interval specified.
  4. After a few redial attempts had occurred, a PLU initiated
     session from a subarea attached host tried to use this
     switched PU for a session to the other EE endpoint.
  5. ISTSSCU7 issued a VARY DIAL to activate the switched PU.
  6. This was rejected because DWINOP had already started the
     redial process.  This cause the following message to be
     issued:
       IST607I VARY DIAL FOR swpuname FAILED -- INVALID NODE
         TYPE OR STATE
  7. Some time later, the session setup failed.  In this case, the
     OLU host failed it with the IOPURGE sense, 087D000D.  When
     the session was cleaned up in the EE VTAM, ISTINCY5
     disconnected the PU.  This caused the DWINOP retries to be
     stopped and the following message was issued:
       IST493I SOFT INOP FOR ID=swpuname OVERRIDDEN BY REQDISCONT
  

Problem conclusion

• To resolve this problem, ISTSSCU7 and ISTINCY5 have been
  changed to detect when redial is in progress due to DWINOP.  If
  this is the case, ISTSSCU7 will not try to issue a VARY DIAL and
  ISTINCY5 will not disconnect the PU if it has DISCNT=NO coded.
  

Temporary fix

Comments

APAR Information

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

  OA35531

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

  UA60612

Modules/Macros

• ISTINCY5 ISTSSCU7
  

Fix information

• Fixed component name

  VTAM V4 MVS/ESA

• Fixed component ID

  569511701

Applicable component levels

• R1D0 PSY UA60612

     UP11/07/01 P F106

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.