PK18245: FLAB IS BEING MARKED WITH A 0 AND THEN SHUNTED, A RETRY IS DONE AND FINDS 0 REASON FOR SHUNTING, DFHFC0002 CODE X'0BEA'

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Task fails during syncpoint processing, and it gets shunted.
  Part of the shunt process is we call FCRC to do the file control
  stuff. This will flag the FLAB (because we updated a file) to
  show it is to be retained across the shunt/unshunt.
  Two FLABS, one with a 0 and the other with a flab_indoubt and
  when a retry is executed an DFHFC0002 code X'0BEA' occurs
  because of the 0 reason.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHFC0002 with error code x'0BEA', CICS *
  *                      terminates.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In the reported problem, DEBUGTOOL was active.  An application
  performed recoverable work against a recoverable resource but
  suffered a failure during syncpoint processing, a shunted UOW
  was created.  In doing so, a 'retained' flag was set in the
  FLAB.
  
  An attempt was made to UNSHUNT the UOW and in doing so, CICS
  created a new task that mirrored the previous (failing) task
  environment.  In doing so, 2 FLAB's were chained to this new
  task.  The first was associated with DEBUGTOOL (because DFHDPXM
  references file DFHDPFMP during transaction attach for pattern
  matching) and the second was for the vsam dataset that actually
  suffered the error during syncpoint processing.  When DFHFCRC
  was driven it tested the flab associated with the DEBUGTOOL,
  found it had no 'retain' flags set and issued DFHFC0002 with
  an error code of x'0BEA'.
  
  Keywords:  msgDFHFC0002 FC0002
  

Problem conclusion

• DFHDPXM has been modified and will ignore the fact DEBUGTOOL
  is active when rebuilding the task environment during unshunt.
  

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:

  UK12627 PK47035

Modules/Macros

•    DESDPXM  DFHDPXM
  

Fix information

• Fixed component name

  CICSTS 3.1 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK12627

     UP06/03/17 P F603

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.