OW30639: RTP PIPE DOES NOT INACTIVATE AFTER INOP

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The configuration is:
  VTAM === NCP --token ring-- ROUTER
       (DLUS)=======================(DLUR)
     HPR tower=====(rtp pipe)======HPR tower
  When the router powers down, NCP sends an INOP to VTAM.  The
  INOP is processed and cleans up the PU, but the RTP Context
  Manager is not notified, and the RTP pipe is not cleaned up
  immediately, but instead, it times out after several minutes.
  When the router powers back up, the DLUR/DLUS session cannot
  be re-established because VTAM is still waiting for the first
  session to come down, and that session will not come down until
  the RTP pipe cleans up.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a PU downstream from an NCP goes   *
  *                      INOP, HPR path switching is not kicked  *
  *                      off immediately for pipes traversing    *
  *                      the INOPed PU.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a PU downstream from an NCP INOPs, the INOP is processed
  by Configuration Services.  Configuration services does not
  notify the RTP Context Manager (RCM) component of the INOP, so
  affected HPR pipes must wait for timers to expire before
  pathswitching is started.
  

Problem conclusion

• Macro ISTRTI was modified as follows:
    A new bit was defined to indicate that Config. Services
    is the orgin of the signal.
    RTI_SA was mapped on top of RTI_NCB_ADDR.  This
    will allow CS to pass the subarea number of the INOPing
    device to RCM.
  
  Module ISTDECQ4 was modified to send an RTI to RCM when
  an INOP is received for a PU which is HPR capable.
  
  Module ISTRCCIN was modified to process the RTI from
  config. services as follows:
    - using the subarea number and element address passed
      from CS, the TG number and CP name of the INOPing
      PU is determined.
    - all ICNCBs in this host are scanned for RPNCBs which
      have as their first hop (found in the RSCV hung off the
      RPNCB) the same TG number and CP name as the INOPing
      PU.  For all matches, an RTI is built and forwarded to
      RTP for path switching.
  

Temporary fix

Comments

• ×**** PE98/04/30 FIX IN ERROR. SEE APAR OW33104  FOR DESCRIPTION
  

APAR Information

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

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

  UW46304 UW46305

Modules/Macros

• GETCPCB  ISTDECQ4 ISTRCCIN ISTRTI
  

Fix information

• Fixed component name

  VTAM V4 MVS/ESA

• Fixed component ID

  569511701

Applicable component levels

• R401 PSY UW46304

     UP98/04/06 P F804

• R411 PSY UW46305

     UP98/03/10 P F803

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.