PM76865: IRLM MESSAGE SHOWING IRLM SUBSYS NAME IS ADDED IN IRLM RESTART SO THAT SUBSYS NAME CAN BE IDENTIFIED TO PREVENT A USER ERROR.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • IRLM MESSAGE SHOWING IRLM SUBSYS NAME IS ADDED IN IRLM RESTART
    SO THAT SUBSYS NAME CAN BE IDENTIFIED TO PREVENT A USER ERROR.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 V10 users.                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 data sharing member restart failure *
    *                      MSGDSNT384I issued by DB2 for timeout   *
    *                      doing restart.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    DB2 zparm IRLMSID may be incorrectly entered which could be
    different than IRLMNM in the irlm startup proc that is started
    by DB2. This may result in failure to identify to correct IRLM
    followed by DB2 restart timeout and ABND=04E-00E30081. Message
    DSNT384I is also issued. From messages, it is not clear which
    IRLM subsystem was being started.
    Need a new message to indicate IRLM subsystem id for the IRLM
    which is restarted with DB2 auto-restart.
    

Problem conclusion

  • A new message DSNT820I is being introduced with this APAR to
    identify the IRLM subsystem id (IRLMSID) which is going to be
    started by DB2 auto-restart.
    
    DB2 Messages book will be adding following documentation:
    
    DSNT820I
    
    DB2 IS STARTING IRLM SUBSYSTEM=irlm_id
    
    Explanation:
      DB2 auto-restart is attempting to automatically start IRLM
      with IRLM subsystem name as set in IRLMSID in the DSNZPARM
      used at the startup.
    
      irlm_id = IRLM subsystem ID set in macro DSN6SPRM which was
      in the DSNZPARM
    
    System action:
      none
    
    Operator response:
      none.
    
    System programmer response:
      none
    
    Problem determination:
     IRLMNM parm given in the IRLM startup procedure (IRLMPRC in
     DSNZPARM) should be the same as IRLMSID in the DSNZPARM used
     at startup. If DB2 restart had failed, please refer to the
     documentation for DSNT384I.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76865

  • 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

    2012-11-09

  • Closed date

    2013-04-01

  • Last modified date

    2013-05-03

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

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

    UK93078

Modules/Macros

  •    DSNFMDIR DSNFTDIR DSNTLIDE
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK93078

       UP13/04/18 P F304

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM76865

Modified date:

2013-05-03

Translate my page

Machine Translation

Content navigation