PI41979: CICS TRANSACTION CBAM FAILS ABENDAEXZ WHEN BROWSING AN EMPTY BTS CONTAINER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Using CBAM, on the screen where the processes are listed, they
  tab to the "Conts" column and select a process to display its
  containers.
  This results in "DFHAC2206 Transaction CBAM failed with abend
  AEXZ." message on the screen and a AEXZ dump.
  The trace in the dump shows an INQUIRE CONTAINER returning a
  DISASTER response. The failure is a GETMAIN Exception
  INVALID_GET_LENGTH for BACRDATA storage because the length is
  zero.
  The problem was recreated by doing a PUT CONTAINER to a BTS
  container with zero length. The PUT completes normally, but
  browsing the  process/activity containers later in CBAM will
  produce the GETMAIN failure with INVALID_GET_LENGTH and abend
  AEXZ.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: AbendAEXZ when issuing INQUIRE          *
  *                      CONTAINER commands against a BTS        *
  *                      container.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The CBAM transaction was being used to browse CONTAINERS on a
  BTS repository file. CBAM issued a BABR INQUIRE_CONTAINER
  command. This found that the length of the current container was
  zero bytes, but still attempted to issue a GETMAIN for zero
  bytes of storage to return the container contents to the caller.
  
  .
  From CICS TS V5.1 onwards it is no longer possible for CICS
  internal GETMAIN requests to reserve zero bytes of storage. This
  attempt to do so therefore resulted in SMGF_EXCEPTION, reason
  code SMGF_INVALID_GET_LENGTH. This resulted in BABR_DISASTER on
  the INQUIRE_CONTAINER call, and a transaction abend AEXZ.
  Additional Keywords: INVALID_GET_LENGTH SM0302
  

Problem conclusion

• DFHBABR has been updated to avoid the GETMAIN request for zero
  bytes of storage, if the container length is found to be zero
  during an INQUIRE_CONTAINER request. The DATALENGTH and SET
  storage address returned to the issuing application will both be
  set to zero.
  

Temporary fix

• 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:

  UI30065

Modules/Macros

• DFHBABR
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R900 PSY UI30065

     UP15/08/23 P F508

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.