IBM Support

PM81913: CATMAINT/CATENFM PROCESSING MAY BE IMPACTED IF CATENFM HALTENFM IS USED INCORRECTLY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CATMAINT/CATENFM processing may be impacted if CATENFM HALTENFM
    is used incorrectly
    .
    KEYWORD added: DB2MIGV10/K
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Users of the DSNTIJNH CATENFM job.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The DSNTIJNH job was used while in      *
    *                      NFM and this prevented later            *
    *                      CATMAINT and CATENFM processing.        *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    The ACOMHALT process from the DSNTIJNH job is only applicable
    while a subsystem is going through the ENFM process. It should
    not affect CATMAINT or CATENFM processing outside of an active
    ENFM process. In the reported case it was interfering with a
    subsystem's attempt to enter the CM* mode.
    
    The DSNTIJNH job is used to halt the DSNTIJEN ENFM process.
    When used, the ENFM process will stop after the current ENFM
    step completes.
    
    If the DSNTIJNH job is used while in NFM then it may prevent
    other CATMAINT or CATENFM processing.
    
      In the reported problem, a DSNTIJNH job was run while in NFM
    and then a DSNTIJCS job was run to put the subsystem into CM*.
    The DSNTIJCS job failed with a return code=6 and the following
    MSGDSNU777I message being displayed in the job output:
    
    DSNU777I -DB2A 042 10:43:44.73 DSNUECMI - CATENFM UTILITY STATUS
             - SKIPPING STEP BECAUSE HALT WAS SPECIFIED.
    
    The subsystem remained in NFM.
    
    The same problem would occur if the DSNTIJES job was run to
    have a subsystem enter the ENFM* mode.
    

Problem conclusion

  • Code has been modified to correct the aforementioned problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM81913

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-01

  • Closed date

    2013-02-19

  • Last modified date

    2013-04-02

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

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

    UK91829

Modules/Macros

  • DSNUECMI DSNUECM0 DSNUECM4
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK91829

       UP13/03/07 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 April 2013