IBM Support

PM80709: DFHSM0133 SOS DUE TO RMOFRMLK 'S, PREVIOUS SHUTDOWN HUNG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CICS shutdown hangs and region must be cancelled. Subsequent
    restarts all fail due to SOS condition, DFHSM0133. CICS must be
    started Initial to recover.
    .
    The last CICS shutdown message indicated that CICS was quiescing
    the RM domain:
    .
    DFHRM0131 RESYNCHRONIZATION REQUIRED WITH IRC RESOURCES
    .
    The next expected messages for the RM domain would be these two
    which were never issued:
    .
    DFHRM0204  There are no indoubt, commit-failed or backout-failed
      UOWs.
    DFHRM0130  Recovery manager has successfully quiesced.
    .
    Domain manager confirms that most domains are waiting for the RM
    domain to quiesce. The RM shutdown task is a CSXM task that is
    suspending/waking up every 10 seconds out of module DFHRMSL7,
    proc RMSL7_SLEEP_A_WHILE. Flag KEYPOINT_SCHEDULED is set to YES,
    so DFHRMSL7 believes that an activity keypoint is still in
    progress, and so waits for it to complete before doing a warm
    keypoint.
    .
    The joblogs showed that a CSKP task abended. After CKSP abended,
    there are no more messages indicating successful keypoints
    were taken, or that the log tail was trimmed. Expected messages
    would have been:
    .
    DFHRM0205 AN ACTIVITY KEYPOINT HAS BEEN SUCCESSFULLY TAKEN.
    DFHLG0743 TAIL OF LOG STREAM xxxxxx.DFHLOG DELETED AT BLOCK ID..
    .
    After CSKP abended, the KEYPOINT_SCHEDULED flag is left turned
    on, but CSKP is never resarted, no further keypoints are taken,
    and so the system log gets very large resulting in the
    subsequent SOS at startup. At startup, the SM domain shows that
    most of the storage is allocated to ECDSA as RMOFRMLK 's.
    .
    Additional Symptom(s) Search Keyword(s):
    KIXREVxxx
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS shutdown hung and had to be        *
    *                      cancelled and restarted with            *
    *                      START=INITIAL.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem presented as a hung CICS shutdown.  The user
    cancelled CICS but any restart attempt ( with the exception of
    START=INITIAL ) failed with CICS going short on storage.
                                                                   .
    Shutdown hung because the RM ( Recovery Manager ) domain could
    not shutdown cleanly.
                                                                   .
    During the run of CICS prior to the shutdown attempt, a CSKP
    task had been abended by ACF2 and in doing so, a flag
    ( keypoint_scheduled ) had been left on indicating that CSKP was
    running. Because of this, CSKP did not run again so no activity
    keypointing occurred. In addition this prevented a warm keypoint
    from being taken during CICS shutdown. CICS was unable to find
    an intact keypoint chain on the log and this eventually led to
    the CICS system going short on storage during restart.
    

Problem conclusion

  • DFHRMSL7's recovery routine has been amended to set
    keypoint_scheduled to off.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM80709

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-16

  • Closed date

    2013-02-25

  • Last modified date

    2013-04-02

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

    PM78788

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

    UK92007 UK92008

Modules/Macros

  •    DFHRMSL7
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R600 PSY UK92007

       UP13/03/08 P F303

  • R700 PSY UK92008

       UP13/03/08 P F303

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":"4.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":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 April 2013