PK33546: REPOSITORY SYNCHRONIZATION TAKES A LONG TIME CMAS NAME IS LESS THAN 5 CHARACTER CPLTEXCP

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You have migrated from R220 of CPSM to R310.  When your CMAS's
  come up and perform repository sync, it takes up to 20 minutes.
  This occurs every time that the CMAS's are restarted.  In R220
  the CMAS's would connect and resync in seconds.
  The job output doesn't show any error messages during this time,
  and the AUXTRACE shows that a long resync is required.
  The trace shows TIMEOUT traces from CSLT (POINTID 16) where the
  MAL being shipped to CPSC fails with a KERNERROR.  Followed by a
  CPLTEXCP (POINTID 69 LRT_CPSC2_FAIL).
  The failing Mal in the trace:
  EYUQCPSC IN
                  *FUN FUNCTION( MPSYNC )
                  *CHR DEBUG( CPSCSyn2 )
                  *CHR CMASNAME( W91A     )
                  *BIN TYPE( 00000004 )
                   CHR PLEXNAME(          )
               OUT
                  *RSP RESPONSE( KERNERROR )
                  *RSN REASON( KERR_EXET )
  ____
  The CMAS name is 4 characters long.
  

Local fix

• Renaming the CMAS's to a five character name will allow them
  to resynch normally.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex/SM V3R1M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Various errors may occur when using a   *
  *                      CMAS name that is less than five (5)    *
  *                      characters in length in a CMAS network. *
  *                                                              *
  *                      Errors seen include, but are not        *
  *                      limited to, the following:              *
  *                                                              *
  *                      -  an abnormal delay during repository  *
  *                         synchronization (10 minutes or       *
  *                         longer between EYULOG messages       *
  *                         EYUCP0203I and EYUCP0204I) between   *
  *                         two CMASes when one or both of the   *
  *                         CMASes has a name that is less than  *
  *                         five characters in length.           *
  *                                                              *
  *                      -  invalid data returned when using the *
  *                         EUI, API, or WUI to request records  *
  *                         from a CMAS whose name is less than  *
  *                         five characters in length if that    *
  *                         CMAS is running a lower CPSM release *
  *                         or maintenance level.                *
  *                                                              *
  *                      Examination of the auxtrace datasets of *
  *                      a CMAS that is communicating with a     *
  *                      CMAS that has a name that is less than  *
  *                      five characters in length will show     *
  *                      exception trace entries written by      *
  *                      method EYU0CTSK (CTSK) with a debug     *
  *                      text of 'EXCEPT' and a trace point ID   *
  *                      of 21.                                  *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all CMASes and MASes must be           *
  *                 restarted.  Note that the restarts do not    *
  *                 need to occur at the same time.              *
  ****************************************************************
  When a CMAS receives data from another CMAS, the receiving CMAS
  may need to convert the data, if the sending CMAS is running a
  lower release of CPSM or a lower maintenance level.  To
  determine if conversion is required, method EYU0CTSK (CTSK) in
  the receiving CMAS calls method EYU0CPLC (CPLC) to retrieve the
  release/maintenance level information for the sending CMAS,
  passing either the name or SYSID of the sending CMAS as input.
  
  Most CPSM requests for data are a two stage process.  The
  originator sends the request as a parameter list (Method
  Argument List - MAL) for a program to be run in the target
  system.  Associated with the MAL is a prefix which identifies
  the CMAS the request is being sent to.  The MAL and its prefix
  are sent in a communication buffer, which has an identification
  header that contains the SYSID of the originating CMAS.  The
  partner CMAS passes the MAL to the required program, which
  collects the requested data and sets the proper return codes in
  the MAL.  The data and the MAL and its prefix are then placed
  into a communication buffer, containing the original
  identification header, which is returned to the originating
  CMAS.
  
  When the partner receives the request, CTSK retrieves the SYSID
  of the sender from the communications buffer header for its call
  to CPLC.  When the originator receives the results, CTSK cannot
  use the SYSID from the communications buffer.  Instead, it uses
  the MAL prefix, which contains either the name or the SYSID of
  the partner CMAS.  CTSK checks the fifth character of the CMAS
  identification in the MAL prefix, and if it is not greater than
  a blank, assumes that it is the SYSID of the partner.  If the
  partner's CMAS name is less than five characters in length, then
  the request to CPLC may specify a SYSID which is really a name,
  and the request will fail, causing various errors, including
  those specified above.
  

Problem conclusion

• A flag already exists in the MAL prefix to indicate whether the
  CMAS identification contained within is a name or SYSID.  Method
  EYU0CTSP (CTSP) has been updated to propagate that flag when it
  makes a copy of the MAL and its prefix that is used for some
  communication requests.  CTSK has been updated to check the flag
  to determine if the CMAS identification in the MAL prefix is a
  name or SYSID.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

• Various errors may occur when using a
  CMAS name that is less than five (5)
  characters in length in a CMAS network.
  
  Errors seen include, but are not limited
  to, the following:
  
  -  an abnormal delay during repository
     synchronization (10 minutes or
     longer between EYULOG messages
     EYUCP0203I and EYUCP0204I) between
     two CMASes when one or both of the
     CMASes has a name that is less than
     five characters in length.
  
  -  invalid data returned when using the
     EUI, API, or WUI to request records
     from a CMAS whose name is less than
     five characters in length if that
     CMAS is running a lower CPSM release
     or maintenance level.
  
  Examination of the auxtrace datasets of
  a CMAS that is communicating with a
  CMAS that has a name that is less than
  five characters in length will show
  exception trace entries written by
  method EYU0CTSK (CTSK) with a debug
  text of 'EXCEPT' and a trace point ID
  of 21.
  
  
  When a CMAS receives data from another CMAS, the receiving CMAS
  may need to convert the data, if the sending CMAS is running a
  lower release of CPSM or a lower maintenance level.  To
  determine if conversion is required, method EYU0CTSK (CTSK) in
  the receiving CMAS calls method EYU0CPLC (CPLC) to retrieve the
  release/maintenance level information for the sending CMAS,
  passing either the name or SYSID of the sending CMAS as input.
  
  Most CPSM requests for data are a two stage process.  The
  originator sends the request as a parameter list (Method
  Argument List - MAL) for a program to be run in the target
  system.  Associated with the MAL is a prefix which identifies
  the CMAS the request is being sent to.  The MAL and its prefix
  are sent in a communication buffer, which has an identification
  header that contains the SYSID of the originating CMAS.  The
  partner CMAS passes the MAL to the required program, which
  collects the requested data and sets the proper return codes in
  the MAL.  The data and the MAL and its prefix are then placed
  into a communication buffer, containing the original
  identification header, which is returned to the originating
  CMAS.
  
  When the partner receives the request, CTSK retrieves the SYSID
  of the sender from the communications buffer header for its call
  to CPLC.  When the originator receives the results, CTSK cannot
  use the SYSID from the communications buffer.  Instead, it uses
  the MAL prefix, which contains either the name or the SYSID of
  the partner CMAS.  CTSK checks the fifth character of the CMAS
  identification in the MAL prefix, and if it is not greater than
  a blank, assumes that it is the SYSID of the partner.  If the
  partner's CMAS name is less than five characters in length, then
  the request to CPLC may specify a SYSID which is really a name,
  and the request will fail, causing various errors, including
  those specified above.
  
  
  A flag already exists in the MAL prefix to indicate whether the
  CMAS identification contained within is a name or SYSID.  Method
  EYU0CTSP (CTSP) has been updated to propagate that flag when it
  makes a copy of the MAL and its prefix that is used for some
  communication requests.  CTSK has been updated to check the flag
  to determine if the CMAS identificaton in the MAL prefix is a
  name or SYSID.
  

APAR Information

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

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

  UK19865

Modules/Macros

•    EYU0CTSK EYU0CTSP
  

Fix information

• Fixed component name

  CPSM CICS 3.1

• Fixed component ID

  5655M1501

Applicable component levels

• R100 PSY UK19865

     UP06/11/22 P F611

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.