IBM Support

PK69827: SEVERE ERROR CODE X'0BF2' HAS OCCURRED IN MODULE DFHFCRC. ZERO_WORK_TOKEN

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DFHFC0002 A severe error code X'0BF2' has occurred in DFHFCRC.
    ZERO_WORK_TOKEN for a FUNCTION DELIVER_BACKOUT_DATA.  This is
    followed by a DFHRM0002 CICSHQAP A severe error code X'0456' has
    occurred in DFHRMR03. BAD_RESPONSE_FROM_CLIENT due to no token.
    If one task is running intersystem syncpoint and another task
    running system resync attempting to recover a session failure on
    a SEND_DO_COMMIT a timing condition causes the error to occur.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS terminates with severe error       *
    *                      DFHRM0002.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A task wrote to a recoverable file, and so had a FRAB control
    block created as the RMRO anchor block for the FC resource
    owner, and this FRAB addressed via a token within the rmux array
    for the task's RMUW control block. Later, the task issued an
    EXEC CICS SYNCPOINT command. Having prepared resources, a
    send_do_commit flow was sent to a remote system (the last
    agent) and CICS went indoubt with respect to the resolution of
    the syncpoint.
      At this point, a communication failure for the session was
    detected. CICS began preparing the UOW for shunting. At the
    same time, a CLQ2 task was attached for resync recovery
    processing of the session. The resync recovery concluded that
    the remote system had not committed, and so the UOW was
    instructed that it should be backed out.
      Before this could be honoured however, the indoubt failure
    of the UOW required that shunting be completed for it. CICS
    called the RMCs for shunt processing. It then wished to call
    interested RMROs with news of the shunted resolution of the
    UOW. However, because the state of the "status" field within
    the RMUW had been reset to rmuw_backward by the resync
    recovery processing, CICS believed it had to restore the
    RMRO token values from the new RMUW created earlier in the
    syncpoint. This led to null values being placed over the
    rmux array slots. Since the tokens were nullified, CICS did
    not invoke any RMROs for shunt processing.
      Upon completion of the shunt operation, CICS was able to
    honour the unshunt, and so backout the UOW. During backout, the
    file control recovery data was restored from the system log and
    presented to DFHFCRC for backout processing. However, since the
    RMUW had a null token value for FC processing, this was
    construed to be a severe error. DFHFCRC issued an exception
    trace "0BF2 FCRC *EXC* ZERO_WORK_TOKEN" and message DFHFC0002,
    "a severe error (code X'0BF2') has occurred in module DFHFCRC."
    This was returned to recovery management, which in turn issued
    DFHRM0002 "a severe error (code X'0456') has occurred in module
    DFHRMRO3." CICS was then terminated.
    KEYWORDS: 0002 FC0002 RM0002 msgDFHFC0002 msgDFHRM0002 FCRC
    RMRO3 status rmuw.status rmuw_in_doubt 0BF2 BF2 0456 456
    FCRC_TRACE_NO_WORK_TOKEN tid_rmro3_fatal_client_response
    

Problem conclusion

  • CICS has been changed to avoid copying back an rmux array token
    value from the new RMUW into the existing one, if the new array
    contains a null token value in that slot.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PK69827

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-07-31

  • Closed date

    2008-10-09

  • Last modified date

    2008-11-04

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

    PQ67551

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

    UK40525 UK40539

Modules/Macros

  •    DESRMOT  DESRMUO  DESRMUW  DESRMUWC DESRMUWT
    DESRMUW1 DESRMUW3 DESRMUW4 DFHRMOT  DFHRMOTA DFHRMOTM DFHRMOTT
    DFHRMUO  DFHRMUW  DFHRMUWA DFHRMUWB DFHRMUWC DFHRMUWD DFHRMUWE
    DFHRMUWF DFHRMUWH DFHRMUWI DFHRMUWJ DFHRMUWL DFHRMUWM DFHRMUWN
    DFHRMUWP DFHRMUWQ DFHRMUWS DFHRMUWT DFHRMUWU DFHRMUWV DFHRMUWW
    DFHRMUW0 DFHRMUW1 DFHRMUW3 DFHRMUXC DFHRMUXD DFHRMU1C DFHRMU1D
    DFHRMU1E DFHRMU1F DFHRMU1G DFHRMU1J DFHRMU1K DFHRMU1L DFHRMU1N
    DFHRMU1Q DFHRMU1R DFHRMU1S DFHRMU1U DFHRMU1V DFHRMU1W DFHRMU2D
    DFHRMWTA DFHRMWTI DFHRMWTM DFHRMWTT
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R400 PSY UK40525

       UP08/10/14 P F810

  • R500 PSY UK40539

       UP08/10/14 P F810

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 November 2008