PI13831: CPSM EYU9XDBC USER COMPLETION CODE=0016. EYUXD0904E, EYUXD0906E AND EYUXD0910E MESSAGES SEEN

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You run a BATCHREP job using EYU9XDBC. It terminates with
  .
  USER COMPLETION CODE=0016
  ABEND=S000 U0016 REASON=00000000
  .
  The same job runs successfully when run on other LPARs to
  connect to other CMASes. In the CMAS EYULOG, you see EYUXD0807I
  signon and signoff messages, but nothing in between.
  .
  If you have DAT level 18 trace turned on, you will see trace
  entries similar to the following in the CMAS:
  .
  12345 XDNR XLOP XDNR DAT Lv-18 18000 ATCBPost
  12345 XDNR XLOP XDNR DAT Lv-18 18000 PreExec  <-- for CONNECT
  12345 XDNR XLOP XDNR DAT Lv-18 18000 PostExec <-- for CONNECT
  12345 XDNR XLOP XDNR DAT Lv-18 18000 ATCBWait
  12345 XDNR XLOP XDNR DAT Lv-18 18000 ATCBPost
  .
  Your batch job output will have the following error messages:
  .
  EYUXD0904E  PERFORM OBJECT command failed.
              Response = INVALIDPARM      Reason = THREAD
  EYUXD0906E  An attempt to submit a batched repository update to
              run in CMAS CMAS123 failed.
  EYUXD0904E  FEEDBACK       command failed.
              Response = INVALIDPARM      Reason = THREAD
  EYUXD0910E  An attempt to obtain feedback information failed.
  Additional Symptom(s) Search Keyword(s): KIXREVSVR
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V4R2M0 Users                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: A batch API program may fail with a     *
  *                      response of INVALIDPARM (1028) and a    *
  *                      reason of THREAD (1280) when the Data   *
  *                      Repository component data cache for the *
  *                      CMAS to which the API program connected *
  *                      extends to two dataspaces, DAT1 and     *
  *                      DAT2.                                   *
  *                                                              *
  *                      If the failure occurs, then all batch   *
  *                      API programs that connect to that CMAS  *
  *                      will also fail.  A CPSM warm start of   *
  *                      the CMAS (the CMAS is restarted while   *
  *                      MASes and/or batch API programs that    *
  *                      were connected to it remain active) may *
  *                      not resolve the problem.  A CPSM cold   *
  *                      start of the CMAS (the CMAS is          *
  *                      restarted after all MASes and batch API *
  *                      programs that were connected to it are  *
  *                      terminated) will resolve the problem.   *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all batch API programs must be         *
  *                 restarted, pointing to the SEYUAUTH library  *
  *                 updated by the PTF.  Note that the restarts  *
  *                 do not need to occur at the same time.       *
  ****************************************************************
  When a batch API program issues a CONNECT command to connect to
  a CMAS or CICSplex, a four byte thread token is associated with
  the connection and returned to the API program.  The API
  program provides this thread token when issuing subsequent
  commands for the connection.
  
  When a subsequent command is issued, method EYU0ABM0 (ABM0),
  running in the batch address space, will validate that the
  thread token passed in the command is for a valid connection
  issued by the address space.  If not, it returns the response
  and reason of INVALIDPARM/THREAD to the API program.
  
  When the Data Repository component data cache extends to two
  dataspaces, the validation performed by ABM0 may be incorrect.
  This will cause any command issued after a CONNECT to fail with
  INVALIDPARM/THREAD, even when the thread token is for a valid
  connection.
  

Problem conclusion

• The validation code in ABM0 has been updated to process
  correctly regardless of whether the Data Repository data cache
  consists of one or two dataspaces.
  

Temporary fix

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

Comments

APAR Information

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

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

  PI13874 UI16527

Modules/Macros

• EYU0ABM0
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R70M PSY UI16527

     UP14/03/29 P F403 ½

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.