PH36143: DEVELOPMENT FIXES

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• Development Fixes
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the IBM Communications Server for z/OS Version  *
  * 2 Release 5: IP                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * 85270 - SmcrSysplexTest and SmcdSysplexTest failed on V2R5   *
  * 85397 - SMC-Dv1 reason code not set                          *
  * 85436 - NMI/SMF updates for SMCRv2 Interfaces, Link Groups,  *
  * and Links                                                    *
  * 85423 - v obey for smcexclude list cleans out smcpermit      *
  * list.                                                        *
  * 84842 - CS390 z/OS2.5 IST2391I  IQP4RMR  PCIE SERVICE        *
  * FAILURE ON TRLE IUT127B1                                     *
  * 85607 - SMCRv2 - vary obey add interface does not add SMCR   *
  * interface to the running stack.                              *
  * 85498 - Delete RKey V2 response LLC message has RKeys set to *
  * 0 when number of RMBs is non-zero                            *
  * 85281 - RoCEv2 Client GID List                               *
  * 85115 - Display error message when PNETIDs of Hipersockets   *
  * and OSAs match                                               *
  * 85696 - AB/S0C4 0038 EZBSRUTL(HIP6250 21.098)+004F08         *
  * 85417 - Wrong number of SMC Exclude filters in NMI/SMF       *
  * 85643 - Update SMF mappings to document fields as deprecated *
  * in V2R5                                                      *
  * 85614 - Updates to SMF records and Books for SMC Filters     *
  * 85447 - R210319Q +9 InOpDump by ISTLLCWI: ISTLLCWI InOpCode  *
  * 010 for resource 2EA2  for Device O6ETHI1P                   *
  * 85402 - OS NETSTAT display error for Routeable RoCE SMCv2 on *
  * z15                                                          *
  * 85120 - R210219QD AB/S04C5 2004  TCPSVT V2R5 : Job(TCPSVT )  *
  * EZBITKOB(HIP6250 21.033)+0010D6 S4C5/74F520                  *
  * 85851 - Direct connections failing with SMCReason: 00005224  *
  * - Internal error (cannot determine next hop)                 *
  * 85708 - R210409O +20 GJCIDUMP 01 ZO 590I TCPSVT SMCR RCV     *
  * 85682 - Updates to SMF records and Books for SMCR IP address *
  * fields                                                       *
  * 85977 - R210430O IST2406I SMC-R LINK FAILURE ON TRLE         *
  * IUT10132 CODE = 08105013 direct connection indirect link     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply PTF                                                    *
  ****************************************************************
  85270 - Netstat ALL/-A displays an incorrect value for smcreason
  field for IPv6 TCP connections. The problem is a structure used
  locally was not being initialized before being filled in in the
  IPv6 path. This caused the processing to use invalid, residual
  data in some cases.
  85397 - Reason code was not being set in some cases for SMCv1
  (SMC-Dv1 or SMC-Rv1).
  85436 - In SMF119 subtype 41, the PNETID field was being
  incorrectly displayed for SMC-Rv2 link groups, the SMC version
  was not being displayed for version 1, SMC-Rv2 fields were not
  being displayed in link statistics, and the string constants for
  the OS type needed to be updated. In SMF119 subtype 4, PFID
  needed to be displayed in hex instead of decimal. In SMF119
  subtype 44, the IP address field was being incorrectly formatted
  in the case of the RNIC being associated with multiple
  addresses.
  85423 - A vary obey configuration with an SMCEXCLUDE list clears
  out the existing SMCPERMIT list when an SMCPERMIT block was not
  specified in the vary obey configuration. Additionally, netstat
  config/-f displays the configured SMC filter addresses in the
  wrong format.
  84842 - Message IST2391I issued due to PCIe fixed storage
  exhaustion during extremely heavy SMC-R workloads.   This is
  occuring because the SMC Send (STG) buffers are accumulating
  faster than the write completion code is cleaning them up.
  85607 - An SMC-Rv2 only RNIC does not restart when:
  1 - The RNIC is stopped.
  2 - The OSA that is associated with the RNIC is stopped.
  3 - The OSA definition is deleted by Vary Obey
  4 - The OSA definition is added by Vary Obey.
  85498 - The last 4 bytes of the Delete RKey Response LLC message
  was not being zeroed out. The packet trace of the Delete RKey
  Response LLC message attempted to display all deleted RKeys
  though the message actually contains only up to 8 error RKeys.
  85281 - SMC-Rv2 server did not have enough information to select
  the most optimal route to the client. This often caused
  conditions where a Link Group was established but without the
  most optimal "High Availability" characteristics.
  85115 - Hipersockets and OSA interfaces cannot use SMCD
  communication if they share a PNetID, but there was no message
  indicating this when a common PNetID was configured, making
  problem analysis difficult.
  85696 - Incorrect basing of the RNIC PIF in the processing of
  the SMC-Rv2 GID list. Also modification needed to be made in the
  selection of a directly attached SMC-Rv2 peer during initial
  link activation.
  85417 - Wrong number of SMC Exclude filters in NMI/SMF, the
  number of exclude filters displayed were wrong for IPv6. Also
  found another defect during the unit testing where the IPv6
  addresses are not showing in the NMI/SMF reports if there?s no
  IPv4 addresses.
  85643 - V2R5 deprecated fields not clearly documented
  85614 - Missing NMTP_PICOSecChanged flags
  85447 - The user has some OSAs that are qualified to use HSCI
  and some that are not. A batch of EE messages are sent. The
  first part of the batch of messages is routed to an OSA not
  qualified for HSCI and they are built into layer 3 packets and
  queued for later sending. The rest of the messages are routed to
  an OSA that is qualified for HSCI and they are built into layer
  2 packets and queued for later sending. Later, the packets are
  all sent together and and INOPDUMP occurs in ISTLLCWI with
  INOPCODE 010 due to the mixture of layer 2 and layer 3 packets.
  85402 - TCP connection balancing between SMC-Rv2 links (within a
  Link Group) is failing on the client because of the short Load
  Balancing timer. This timer is only one second and now with
  Possible Next Hop MAC resolution this value should be elongated.
  When the LG moves to SYMMETRICAL state we start an LB timer and
  from this we wait one second and attempt to Load Balance the TCP
  connections over the pair of links.
  85120 - Issue is that the temporary LMBE logic is being driven
  and there is no SMC-D link to the remote peer. There is a flaw
  in the existing logic that does not except the SMCL lock to
  already be held in exclusive mode when EZBSLGSC is invoked.
  Because there is no logic to realize that the SMCL and SMCLAP
  locks are being held exclusive the existing logic assumes that
  only the SMCL lock is being held shared (incorrectly) which can
  result in a locking hierarchy error.
  85851 - SMC-Rv2 server during first contact was not making the
  correct analysis to determine if an SMC-R link was directly
  attached. This caused failures with a code of x'5224'.
  85708 - SMC-Rv2 RMB storage is stranded if we attempt to free
  the RMB but the LG is in the process of attempting to activate
  another alternate link. Attempting to alter the LG state from
  Asymmetric to Symmetrical.
  85682 - Various NMI and SMF IP address control block field
  formats for SMC-Rv2 needed to be updated for consistency.
  85977 - SMC-Rv2 server during first contact was not making the
  correct analysis to determine the route between end-points. This
  resulted in failures with a failure code of 08105013.
  

Problem conclusion

• This APAR resolves problems listed under Problem Description.
  85270 - Code has been updated to first clear the local structure
  before filling it in in the IPv6 path in ezbtcict.
  85397 - Code has been updated to ensure in all cases the reason
  code for SMCv1 is set.
  85436 - All formatting issues were corrected.
  85423 - Code was changed to keep the previous value for
  SMCPERMIT list if it is not specified in a vary obey
  configuration. The netstat config/-f display was updated to show
  the SMC filter addresses in the correct format.
  84842 - The RoCE Express2 device driver has been modified to
  enhance the write completion (WC) logic.  The new logic uses a
  WC SRB model instead of the former STIMERM (IRB/TCB) model.
  This along with lock changes now allows
  the write completion logic for each RNIC to efficiently and
  cost-effectively cleanup the SMC-R staging buffers under heavy
  workloads.
  85607 - TCP/IP code is amended so that the Vary Obey of the V2
  capable OSA will restart an RNIC.
  85498 - The last 4 bytes of the Delete RKey Response LLC message
  are zeroed out now. The packet trace of the Delete RKey Response
  LLC message was modified to display up to 8 error RKeys and the
  error count.
  85281 - Code was enhanced to have the SMC-Rv2 client pass its
  local GID information to the server. This is done on both the
  Confirm CLC message and the Request Add Link request (both
  transmitted to the server). This list of GIDs will have the
  active links's GID as the first in the array of GIDs and the
  remainder of the list will be alternate GIDs sorted in the
  client's view as the most desirable GIDs to be utilized. z/OS CS
  will transmit no more than 4 GIDs but will support receiving up
  to 8 GIDs from the peer.
  85115 - Two new messages EZD2058I and EZZ850I were added to
  indicate that SMC-D would be disabled on an initializing HS/OSA
  interface when it's found that a PNetID already has an interface
  of the opposite type (OSA or HS) associated with it.
  85696 - Added logic to fix RNIC basing issue. Also altered logic
  in the selection of a route that indicates a directly attached
  SMC-Rv2 peer.
  85417 - Change the code to assign right number of exclude and to
  display IPv6 addresses if there?s no IPv4 addresses
  85643 - Documentation added for fields deprecated in V2R5.
  85614 - Code was changed to add NMTP_PICOSecChanged  flags for
  permit and exclude.
  85447 - TCP/IP code is amended to ensure that a batch of EE
  messages all are built as layer 3 packets if the first message
  of the batch is built as a layer 3 packet.
  85402 - For SMC-Rv2 we need to set the Load Balancing timer
  during LG activation on the client and server. The timer should
  be longer than used for SMC-Rv1 and so has been elongated to
  five seconds. Additionally code is added to the liveness timer
  exit (happens every 2 minutes) and determines if the TCP
  connections need to be balanced in an existing LG.
  85120 - Current logic attempts to make sure there is not a
  timing window in the creation of a new SMC-D link (make sure we
  are not attempting to create parallel links). To do this it
  attempts to drop the SMCL lock in shared mode and re-obtain it
  in exclusive mode.  When EZBSRGSC is invoked internally (during
  CM_Setup_Cnf processing) both the SMCL and SMCLAP locks are
  being held exclusive and when we free the SMCL lock and then try
  to re-obtain we cause a locking hierarchy error.  A lower
  leveled lock cannot be obtained in the same class while holding
  a higher leveled lock in the same class. We are holding level 2
  SMCLAP lock and therefore not permitted to obtain level 1 SMCL
  lock in the same class
  85851 - Code was enhanced to have the SMC-Rv2 server to
  correctly analyze whether the peers are directly connected.
  When looking at the CLC proposal information then the client's
  SMCRIPADDR must be in the same subnet as the server's OSA. When
  looking up routing information then either the same subnet is
  observed or the Gateway address is nulls to indicate the route
  is directly attached.
  85708 - Code was enhanced to have the Link group liveness timer
  exit look for stranded RMB storage and free this storage. RMBs
  that are on the PendingDeleteRmbList and all Rkeys associated
  with the RMB have been deleted.
  85682 - Various NMI and SMF IP address control block field
  formats for SMC-Rv2 were updated.
  85977 - Code was enhanced to correctly utilize a multi-path
  route for the "First Contact" SMC-Rv2 link. Additionally logic
  was analyzed on the server to look at all alternate GIDs for
  determining if peers are directly attached.
  

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:

  UI75478

Modules/Macros

• EZACFMS1 EZBIEPRO EZBIFOUT EZBSCUTL EZBNMGSL EZBSMRNS EZBPTSMC
  EZBNMGIF EZBSRLLC EZBNMRHC EZB2SMRL EZASMF   EZBIFIND EZBCTFME
  EZBSMBSD EZB2SMRG EZBSRUT2 EZBTCICT EZBSMBTP EZASMF77 EZBNMMPA
  EZBXFDYN EZBNMMPC EZBNMGRN EZBNMGTP EZBNMFTP EZACFMSG EZBTIGBL
  EZBNMRHA EZB2SMR  EZBSMSGS EZBDGCTR EZBIFIUM EZBSLUTL EZACDNE0
  EZB2SMC  EZBSRUTL EZBSRWCX EZBITMST
  

Fix information

• Fixed component name

  TCP/IP MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R250 PSY UI75478

     UP21/05/27 P F105

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.