IBM Support

PM78069: ABEND0C4 IN DFSCON20 DURING AN EMERGENCY RESTART. CTBCNT CONTAINS ZEROES.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abend 0c4 in DFSCON20 during /ERE while processing a type12
    log record. The 0c4 is due to the fact that CTBCNT contains
    zeroes and the CTB should point to the LTERM (CNT) while
    terminating a conversation.
      The abend is the result of the fact that the /Assign command
    that connected the LTERM to the NODE was not processed across
    the restart. This assign failed because at the point where
    the 02 log record was processed, the CTB4RESP bit was still on.
      The node and lterm were static blocks and prior to the 02 log
    record there was a 4021 with CTB4RESP set and this was followed
    by a CVCT and a 16 for signoff and a 63 for logoff. It was
    not a valid condition for the CTB4RESP to still be set.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V13 users entering Response mode     *
    *                 transactions, conversation transactions or   *
    *                 both, and issuing /ASSIGN commands in a VTAM *
    *                 environment.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABENDS0C4 in DFSCON20 during an         *
    *                      Emergency restart when CTBCNT           *
    *                      contains zeroes.                        *
    *                                                              *
    *                      This is a forward-fit of APAR PM77485.  *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    An ABEND0C4 occurs in DFSCON20 during /ERE while processing a
    type12 log record.  The abend is due to the fact that CTBCNT
    contains zeroes.  The CTB should point to an LTERM (CNT) when
    the conversation is terminating.
    
    The abend is the result of the fact that the /Assign command
    that connected the LTERM to the NODE was not processed across
    the restart.  When the 02 log record for the Assign was
    processed during restart, DFSICL70 detected that CTB4RESP bit
    was still on and rejected the command. CTB4RESP should have
    been reset during session termination.  Since the Assign
    command was not processed correctly, this led to the subsequent
    abend.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    DFSCRPD0 has been modified to reset CTB4RESP when processing
    a 63 termination log record.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM78069

  • Reported component name

    IMS V13

  • Reported component ID

    5635A0400

  • Reported release

    302

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-11-28

  • Closed date

    2012-12-18

  • Last modified date

    2013-10-04

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

    PM77485

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

    UK90482

Modules/Macros

  •    DFSCRPD0
    

Fix information

  • Fixed component name

    IMS V13

  • Fixed component ID

    5635A0400

Applicable component levels

  • R302 PSY UK90482

       UP13/01/08 P F301 Ž

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"302","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020