IBM Support

PI28784: DFHSM0002 APPLID A SEVERE ERROR (CODE X'0C16') HAS OCCURRED IN MODULE DFHSMMG.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You received following error message:
    .
    DFHSM0002 applid A severe error (code X'0C16') has occurred in
    module DFHSMMG.
    .
    From CICS trace table you can see the corresponding exception
    entry which identifies what the error is:
    .
    SM 0C16 SMMG *EXC*
          Invalid_length_on_getmain_for_TASK_class_storage
    .
    This is a timing issue. Task A was inquiring task B's storage
    through a EXEC CICS INQUIRE STORAGE request . During the
    process of this request, task B finished all its work and began
    to release itself including its storage. This result in a
    EXCEPTION response of the INQUIRE_TASK_STORAGE request, which
    finally caused the SM 0C16 EXCEPTION and a SM0002 dump.
    Following are some key trace entries of task A:
    .
    AP 00E1 EIP   ENTRY INQUIRE-STORAGE
    SM 0E01 SMMC2 ENTRY INQUIRE_TASK_STORAGE
          TRANSACTION_NUMBER(#task B)
    DS 0004 DSSR  ENTRY SUSPEND
    DS 0005 DSSR  EXIT  SUSPEND/OK
    SM 0E02 SMMC2 EXIT  INQUIRE_TASK_STORAGE/EXCEPTION
          REASON(INSUFFICIENT_STORAGE) NUMBER_OF_ELEMENTS(38004004)
    SM 0C01 SMMG  ENTRY GETMAIN  REMARK(EIQSKTSG)
          GET_LENGTH(80040040)
    SM 0C16 SMMG  *EXC*
          Invalid_length_on_getmain_for_TASK_class_storage
    .
    If you examine the CICS trace for Task B, you would find task B
    has terminated during the SUSPEND of task A.
    Additional Symptom(s) Search Keyword(s): KIXREVSCB, SM0002,
    DFHSM0002, 0C16, DFHSMMG
    .
    Note that depending upon what kind of storage is being
    GETMAINd, the exception trace entry may be slightly different.
    An SM 0C0E can also appear:
    .
      SM 0C0E SMMG
         *EXC* Invalid_length_on_getmain_for_USER_class_storage
    .
    The cause is the same though. Task-A does an
    INQUIRE_TASK_STORAGE for TASK-B, gets suspended waiting for the
    SMLOCK, and while it is suspended TASK-B terminates.
    .
    

Local fix

  • no
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHSM0002 invalid length on GETMAIN     *
    *                      when INQUIRE STORAGE against a task     *
    *                      that is terminating.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The CICS command 'EXEC CICS INQUIRE STORAGE' is used to inquire
    upon the storage information for a task. DFHSMMC2 is called to
    do the query which first releases the SM lock before calling
    Transaction Manager to locate the task's SMX. After DFHSMMC2
    gets the SMX, it tries to reacquire the SM lock back but is then
    suspended because the lock is already held by another task.
    Before DFHSMMC2 is resumed holding the lock, the task being
    inquired upon terminates and the SMX is no longer valid.
    DFHSMMC2 continues to use the invalid SMX and returns incorrect
    storage information.  CICS then issues a GETMAIN based on the
    incorrect values and fails with
    *EXC* Invalid_length_on_getmain_for_TASK_class_storage.
    Additional keywords: msgDFHSM0002 SM0002 OC16 0C4 S0C4 abendAEXZ
    

Problem conclusion

  • DFHSMMC2 has been changed to locate a task's SMX without
    releasing the SM lock.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI28784

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-31

  • Closed date

    2014-12-25

  • Last modified date

    2015-03-16

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

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

    PI30999 UI24171

Modules/Macros

  • DFHSMMC2
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R700 PSY UI24171

       UP15/01/07 P F501

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 May 2020