OW14443: CP-CP HANG NOT CLEANED UP BY VARY INACT OR VARY TERM

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A CP-CP session became hung during activation. A VARY TERM or
  VARY INACT was used to end the session, but subsequent session
  attempts hung. VTAM had to be recycled to get the CP-CP
  session active.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All using APPN.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A CP-CP session became hung during      *
  *                      activation.  A VARY TERM or VARY INACT  *
  *                      was used to end the session, but        *
  *                      subsequent session attempts hung. VTAM  *
  *                      had to be recycled to get the CP-CP     *
  *                      session active.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
    A CP-CP session became hung during activation. VTAMs CONWINNER
  session was waiting for a BIND RSP, PSEST/B.  VTAMs CONLOSER
  session was either active or not started.  The BIND RSP for the
  CONWINNER session was never received, so the operator issued
  a VARY TERM or VARY INACT for the CP-CP session.  The CONLOSER
  session was cleaned up, if it had been attempted.  For the
  CONWINNER session, a BFCLEANUP flowed toward the SLU CP and
  the SIB was freed.  But, LUS was never notified that the session
  was terminating.
    Whatever caused the BIND (or RSP) to be lost, also caused the
  BFCLEANUP to be lost or fail.  The BFCLEANUP is supposed to
  cause an UNBIND to come in to notify LUS of the session failure.
  Because the UNBIND did not come in, LUS thought the BIND was
  still pending.  This would cause MSGIST530I AM GBIND pending
  to be issued even though a display of the CP showed there
  were no sessions.
    Subsequent CP-CP session attempts will also hang.  When the
  other CP initiates it, VTAMs CONLOSER session may come active.
  Then a CP_SESSION_ACT will be sent to SSC.  SSC will look at
  the APNCB and see that the CONWINNER session is already in the
  activation process (the session with the BIND is outstanding)
  and ignore the CP_SESSION_ACT.  If the operator at this VTAM
  does a VARY NET,ACT,ID=CPname, it will be ignored.
    VTAM had to be recycled to clean up the APNCB.
  

Problem conclusion

• ISTSSCUP was changed to send a CLEANUP to LUS before freeing the
  SIB for a CP-CP session that is pending active.
  This was causing SSC to be posted back with a retryable sense
  code.  So ISTLUCTE was changed to post an outstanding BIND for a
  CP-CP session with a non retryable sense of 80200000, SNSRRIVR,
  if a CLEANUP is received as a result of a VARY TERM or VARY
  INACT of the CP.  If the CLEANUP is the result of some other
  action (i.e. an INOP), the CLEANUP will have a CV35 with the
  true failing sense code, which will be used.
  

Temporary fix

Comments

APAR Information

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

  OW11833

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

  UW20104

Modules/Macros

• ISTLUCTE ISTSSCUP
  

Fix information

• Fixed component name

  VTAM V4 MVS/ESA

• Fixed component ID

  569511701

Applicable component levels

• R301 PSY UW20104

     UP95/08/21 P F508

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.