PI07227: MULTIPLE CPSM SYSLINKS CREATED BETWEEN SAME MASES USING THE SAME PROTOCOL CAUSES UNEXPECTED RESULTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A CPSM SYSLINK definition is created between two MASes, MAS1
  and MAS2. It refers to model CONN and SESS definitions.
  
  You then decide to change which connection or session models
  are used, so you create a second SYSLINK definition between the
  same two MASes. You then remove the original SYSLINK
  definition.
  
  While the updates to the CPSM EYUDREP repository are correct,
  the active in-storage definition for the SYSLINK is not. CPSM
  should not have allowed the second SYSLINK to be created
  between the same MASes without first removing the original
  definition.
  
  Additional Symptom(s) Search Keyword(s): KIXREVxxx
  

Local fix

• REMOVE the original SYSLINK definition first, then create a new
  one.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V5R1M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:    You create a CPSM SYSLINK definition *
  *                      between two MASes, referring to proto-  *
  *                      type CONNDEF and SESSDEF definitions.   *
  *                      You then decide to change connection or *
  *                      session models, so you create a second  *
  *                      SYSLINK definition between the same two *
  *                      MASes, using different prototype defi-  *
  *                      nitions. You then remove the original   *
  *                      SYSLINK definition.  While the updates  *
  *                      to the CPSM data repository are correct *
  *                      the wrong definition for the SYSLINK is *
  *                      removed from the association matrix.    *
  *                      When one or both of the MASes are re-   *
  *                      started, the connection between them is *
  *                      created with the attributes of the ori- *
  *                      ginal prototypes.                       *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all CMASes must be recycled to pick    *
  *                 up the new code.  Note that regions do not   *
  *                 need to be brought down and restarted at     *
  *                 the same time.                               *
  ****************************************************************
     When a MAS is started for which BAS is to install resources,
  the connection matrix is scanned for all SYSLINK resources for
  which the MAS is the primary or secondary system.  The scan is
  based on the assumption that there will only be one SYSLINK
  with a given LINKTYPE for each pair of MASes.  However the key
  for the SYSLINK includes both the CONNDEF (or IPCONDEF) and the
  SESSDEF (or TCPDEF).  If two SYSLINKs are created between a
  pair of MASes, with different prototype definitions, the REMOVE
  action will remove the first association entry found, without
  checking to see if the prototype definitions match.
     If the CMAS has not been restarted since the new SYSLINK was
  created between the MASes, the new association will be removed.
  When SYSLINKs are installed at MAS initialization, the original
  SYSLINK will be processed.  If the CMAS is restarted before re-
  starting the MASes, the Association Matrix will be rebuilt from
  the contents of the data repository, and the correct attributes
  will be used to install the connection.
  

Problem conclusion

• Module EYU0BMZR (BMZR - BAS Remove Association Elements) was
  modified to compare all key fields of the association element
  for a SYSLINK, rather than just the primary and secondary MASes
  and the SYSLINK LINKTYPE, to identify the association element
  to be removed.  Module EYU0BMLR (BMLR - BAS Remove SYSLINK) was
  modified to pass the full SYSLINK resource to BMZR, rather then
  just the link type.
  

Temporary fix

• *********
              * HIPER *
              *********
  FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PI07224

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

  UI14396

Modules/Macros

• EYU0BMLR EYU0BMZR EYU9BAR3 EYU9BAR4 EYU9BAR6 EYU9BARU
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R80M PSY UI14396

     UP14/01/24 P F401

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.