OW56086: CV57 CONTAINS DIFFERENT RIF FIELDS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The RIF field setting in CV57 is differnet if the XID comes in
  from a 2216 compared to the setting received from in the reqcon
  from NCP.
  RIF 062000510020 from 2216 (direction bit=0)
  RIF 06A000510020from NCP  (direction bit=1)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All using VTAM Config Services exit,         *
  *                 ISTEXCCS with switched XCA LAN connections.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Provide VTAM Config Services exit with  *
  *                      XCA FID2 LAN RIF direction bit set      *
  *                      in either INBOUND or OUTBOUND           *
  *                      direction.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  For LAN problem analysis, VTAM XCA (FID2) support provides
  the VTAM Config Services XID exit with the TokenRing
  "Routing Information Field" (RIF) of the received XID.
  The RIF is available in Subfield X'03' within the CV57
  (REQCONT RU).  The RIF direction bit is presented to
  the XID exit as it was received by VTAM from the device.
  
  Sample Configuration:
  
                Segment 001
   +--------+     oo o
   |        | 2216oo
   |   V    +-----o   o        Segment 002
   |   T    |     o   o           ooo
   |   A    |     o   +--Bridge1-o   +--PU1
   |   M    | 3745o   o           ooo
   |        +-----o   o
   |        |     ooooo
   +--------+
  
  In the sample configuation, PU1 may connect to VTAM via a
  D/T2216 or an NCP LAN connection.  When PU1 connects to VTAM
  through the NCP LAN, the RIF direction bit is flipped by the
  NCP prior to the information being forwarded to VTAM.  This
  would mean the RIF should be interpreted as a path from the
  NCP to the device (OUTBOUND direction).  This information is
  then passed to the VTAM Config Services XID exit.
  
  When PU2 connects to VTAM through the XCA FID2 (D/T2216)
  connection, the RIF direction bit is presented to the
  VTAM Config Services XID exit as it was received.  This
  would mean the RIF should be interpreted as a path from VTAM
  to the device (INBOUND direction).
  
  For users of the VTAM Config Services XID exit, this poses a
  problem in the RIF interpretation.  For this reason, VTAM
  XCA FID2 LAN support will now provide a mechanism to allow
  the RIF direction bit to be set to an INBOUND or OUTBOUND
  direction, prior to being presented to the XID exit.
  
  A new parameter, ROUTEDIR, will now be allowed on the XCA PORT
  definition statement for LAN connections.
  

Problem conclusion

• The following modules/macros have changed:
  
  ISTRXPOR - Define RXP_ROUTEDIR bit.
  ISTLSNCB - Define LSN_ROUTEDIR bit.
  ISTSDCPX - Changed to accept the ROUTEDIR parameter on the
             XCA PORT definition statement.  Not valid for
             EE XCA connections.  The default is to set
             RXP_ROUTEDIR to off (0) for INBOUND direction.
             This will be consistent with the RIF direction
             setting as provided to the XID exit today.
  ISTLSCAL - Propagates the RXP_ROUTEDIR bit setting to
             the LSNCB (LSN_ROUTEDIR)
  ISTLSCKK - Has been changed to set the RIF direction bit
             within the X'03' subfield of the CV57
             appropriately based on the ROUTEDIR bit setting.
  
  Module ISTLSCKN has been included for maintenance purposes.
  
  
  The following documentation changes have been made:
  
  OS/390 IBM Communications Server
  SNA Resource Definition Reference
  
  Under the Topic External Communication Adapter (XCA) Major Node
  a new parameter, ROUTEDIR, will be supported for the XCA PORT
  definition statement.
  
  Table 18. External Communication Adapter Major Node -
            LAN, ATM Emulation, or Enterprise Extender
  
  NAME     DEFINITION     Operands        Default
  _______________________________________________
  name     PORT           ADAPNO          MEDIUM
                          CUADDR
                          MEDIUM
                          CAPACITY
                          .
                          .
                                  1
                          ROUTEDIR        INBOUND
  
  NOTE: 1 For LAN or ATM emulation connections only.
  
  
  Under LAN and ATM Emulation Connections add the ROUTEDIR
  parameter to the railroad tracks.
  
  
                  ------ROUTEDIR=INBOUND-----
                 |                           |
            >----|---------------------------------->
                 |                           |
                 |                           |
                  ------ROUTEDIR=INBOUND-----
                 |                           |
                 |                           |
                  ------ROUTEDIR=OUTBOUND----
  
  Under Operand Descriptions add the following:
  
  ROUTEDIR
  
  
                  ------ROUTEDIR=INBOUND-----
                 |                           |
            >----|---------------------------------->
                 |                           |
                 |                           |
                  ------ROUTEDIR=INBOUND-----
                 |                           |
                 |                           |
                  ------ROUTEDIR=OUTBOUND----
  
  
            statements: PORT
            dependency: Switched LAN or ATM emulation connections
                        only.
  
  This parameter is relevent to users of the VTAM Config Services
  XID exit, ISTEXCCS.
  
  For LAN problem analysis, VTAM XCA (FID2) support provides
  the VTAM Config Services XID exit with the TokenRing
  "Routing Information Field" (RIF) of the received XID.
  The RIF is available in Subfield X'03' within the CV57
  (REQCONT RU).
  
  The ROUTEDIR parameter will allow VTAM to present the RIF field
  to the Config Services XID exit with the RIF direction bit
  set appropriately.  The default is to set the RIF direction
  bit as an INBOUND direction.  Meaning the direction of the
  route is from the device inbound to VTAM.  Coding ROUTEDIR
  to OUTBOUND will simply flip the RIF direction bit prior to
  presenting the information to the Config Services XID exit.
  This will allow the XID exit to interpret the RIF field in
  an INBOUND or OUTBOUND direction.
  

Temporary fix

Comments

APAR Information

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

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

  UW94282 UW94283 UW94284 UW94285

Modules/Macros

• ISTLSCAL ISTLSCKK ISTLSCKN ISTLSNCB ISTRXPOR
  ISTSDCPX
  

Fix information

• Fixed component name

  VTAM V4 MVS/ESA

• Fixed component ID

  569511701

Applicable component levels

• R10A PSY UW94283

     UP02/10/23 P F210

• R120 PSY UW94284

     UP02/10/23 P F210

• R140 PSY UW94285

     UP02/10/23 P F210

• R801 PSY UW94282

     UP02/10/23 P F210

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.