PH63852: AFTER UPGRADE TO CPSM 6.1 API WITH CONNECT VERSION(550) FAILS WITH FAILED EXCEPTION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In the process of upgrading to CPSM 6.1, the MP CMAS was
  upgraded while other nonMP CMASs remain at CPSM 5.5.  Now when
  running REXX API application within the plex, it fails with
  RESPONSE=1029 (FAILED) REASON=1345 (EXCEPTION) when the API
  specifies CONNECT VERSION(550).  The batch job runs against the
  MP CMAS with the SEYUAUTH data set used in the MP. It fails
  when a SET DB2ENTRY command is issued.
  
  If Rexx job runs in a 5.5 CMAS with 5.5 MAS regions, specifying
  VERSION(550) the job runs fine.
  
  If Rexx job runs in a 6.1 CMAS with 6.1 MAS, specifying
  VERSION(550) receives the error on the SET DB2ENTRY request.
  
  If SET command is commented out the job runs fine.
  
  If we set VERSION(610) the job runs fine.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Trying to update a v6.1 DB2ENTRY table  *
  *                      entry from an API client running with   *
  *                      VERSION(0550) via the SET command fails *
  *                      with RESPONSE=1029=FAILED               *
  *                      REASON=1359=EXCEPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF to all CMASes in any order.    *
  ****************************************************************
  When trying to update a DB2ENTRY using the API SET command,
  where the CMAS is at 6.1 or above and the API client is earlier
  than 6.1, the set command fails with
  RESPONSE=1029=FAILED and REASON=1359=EXCEPTION.
  
  This is because the DB2ENTRY table was incorrectly modified at
  6.1 to add a new SHARELOCKS field. The SET command is defined
  to have a SETLOCKS field at all releases. When converting the
  DB2ENTRY record between releases method MOM2 (EYU0MOM2) tries
  to create a SHARELOCKS field where it doesn't exist.
  

Problem conclusion

• The DB2ENTRY resource table has been modified to indicate to
  the SET command that SHARELOCKS is a new field at 6.1.
  EYU0MOM2 will no longer attempt to build a SHARELOCKS field
  for the DB2ENTRY table for earlier releases.
  
  This means EYU0MOM2 does not attempt to build a DB2ENTRY
  SHARELOCKS field for releases earlier than 6.1.
  
  At the same time methods EYU0MOCM and EYU0MOM2 have been
  updated internally to return the MAL DIAGNOSTIC field and
  write a trace entry to improve serviceability.
  

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:

  UI99685 UI99686

Modules/Macros

• EYU0MOAC EYU0MOAV EYU0MOCS EYU0MOFB EYU0MOFL EYU0MOFS EYU0MOFT
  EYU0MOM2 EYU0MOMB EYU0MOPA EYU0MOPM EYU0MOSS EYU0MOTB EYU0MOTS
  EYU0MOXS EYU0MOXT EYU9MOTL EYUA0087 EYUC0087 EYUE0087 EYUL0087
  EYUP0087 EYUT0087 EYUY0087
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R40M PSY UI99686

     UP25/01/22 P F501

• R50M PSY UI99685

     UP25/01/22 P F501

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.