PM49747: EXIT(XBMIN) NOT DRIVEN FOR INPUT WHEN FIELD IS ERASED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• EXIT(XBMIN) not driven for input when field is erased by the
  user, either with Erase End Of File or multiple delete keys
  until all characters has been removed, the exit is not driven
  for this field even if it is defined with VALIDN=USEREXIT.
  In a VTAM trace, this "empty" field is transmitted as "SBA" and
  no data. SO, the field is present in the datastream (but it
  has a zero length).
  
  From customization Guide:
  
  
  The XBMIN exit is called, if enabled, when all the following are
  true:
  
  1 - A RECEIVE MAP command has been successfully processed.
  2 - The map referenced in the command contains at least one
  field   specified as VALIDN=USEREXIT.
  3 - At least one USEREXIT field has been returned in the inbound
  datastream and has been mapped into the application data
  structure.
  In our case circumstance 1+2+3 is fulfilled, but the exit is not
  driven.
  When we look in the exit (the sample exit sent with CICS), the
  exit is coded to handle a zero length on the input.
  The only situation when a zero value can be received for
  BMXACTLN is when the user erases an input field.
  

Local fix

• NO
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: BMS Global User EXIT XBMIN is not       *
  *                      driven for input when a field is        *
  *                      erased.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Basic Mapping Support BMS exit XBMIN is not driven when a
  user clears a field in the map with Erase End Of Field or
  multiple delete keys. The exit is not driven for this field even
  though it is defined with VALIDN=USEREXIT and there is a
  corresponding Set Buffer Address SBA with no data in the
  incoming datastream.
  
  Additional keywords: DFH$BMXT BMXACTLN
  

Problem conclusion

• CICS has been changed so that the XBMIN exit is now driven when
  a user erases a field defined with VALIDN=USEREXIT, using EOF or
  multiple delete keys. The exit is passed a valid parameter list
  with UEPBMTAB addressing the field element table. The field
  element corresponding to the erased field has BMXACTLN, the
  actual length of the data received, 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:

  PM52596

Modules/Macros

•    DFHMCPA$ DFHMCPE  DFHMCPE$ DFHMCP1$ DFHMCX
  DFHMIN   DFHM32   DFHM32A$ DFHM321$
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R500 PSY UK74933

     UP12/01/07 P F201

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.