PM78128: DB2 10 SUPPORT FOR END OF RESTART AUTOMATIC LPL RECOVERY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 New Function to trigger automatic LPL recovery at the end of
  restart.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of DB2.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: NEW DB2 z/OS for V10R1 FUNCTION SUPPORT *
  *                      FOR END OF RESTART AUTOMATIC LPL        *
  *                      RECOVERY.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Prior to this APAR, auto-LPL function was supported only during
  DB2 mainline operation. However, with this APAR, LPL recovery
  will automatically be triggered, at the end of DB2 restart, for
  the objects that were added to LPL during the restart. This will
  avoid or minimize any application failures due to object in LPL.
  This auto-LPL recovery will not be triggered if (1) the object
  is ZPARM deferred (2) DB2  started in maintenance mode (3) DB2
  started by RESTORE SYSTEM Utility (4) object is associated with
  either indoubt or postponed abort transaction.
    The end of restart LPL recovery
  logic is the same as today's mainline LPL recovery logic. i.e.
  it will issue existing LPL/GRECP recovery messages to indicate
  the start and end of LPL recovery of each object.
    The auto-LPL recovery, if needed, will also be
  triggered at the end of Restart Light. This way DB2 will
  automatically recover as many LPL objects are possible before
  DB2 is terminated after it was started in Light mode.
  

Problem conclusion

• This new function will trigger auto-LPL recovery at the end of
  restart, whenever the object is added to LPL by restarting DB2
  member.
  

Temporary fix

Comments

APAR Information

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

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

  UK95832

Modules/Macros

• DSNB1CPP DSNB1LPL DSNIAGBR DSNIERST DSNIIMPD DSNTRSTE DSNXERST
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK95832

     UP13/07/31 P F307

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.