PI12630: MISCELLANEOUS FIXES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• 1) If a large number of objects are being recovered (>50K), the
  agent may not process the generated recovery plans and/or
     JCL properly due the required memory overhead and the
     clients may not display the generated JCL/recovery plans in
     a memory constrained environment. The code was modified to
     process the recovery plans and the generated JCL in constant
     space.
  2) SQL error occurred with SQL code = -913 when deleting
     multiple specifications at the same time using ARY3.1
     browser client
  3) The length of the archive log prefix retrieved from zparm is
     incorrect which causes an issue when determining the new
     name of the copied archive log dataset during Disaster
     Recovery.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Recovery Expert for z/OS.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. If a large number of objects are     *
  *                       being recovered (>50K), the agent may  *
  *                       not process the generated recovery     *
  *                       plans and/or JCL properly due the      *
  *                       required memory overhead and the       *
  *                       clients may not display the generated  *
  *                       JCL/recovery plans in a memory         *
  *                       constrained environment. The code was  *
  *                       modified to process the recovery plans *
  *                       and the generated JCL in constant      *
  *                       space.                                 *
  *                      2. SQL error occurred with SQL code =   *
  *                       -913 when deleting multiple            *
  *                       specifications at the same time using  *
  *                       ARY3.1 browser client.                 *
  *                      3. The length of the archive log        *
  *                       prefix retrieved from zparm is         *
  *                       incorrect which causes an issue when   *
  *                       determining the new name of the        *
  *                       copied archive log dataset during      *
  *                       Disaster Recovery.                     *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

Modules/Macros

• ARYZSPEC
  

Fix information

• Fixed component name

  DB2 REC EXPERT

• Fixed component ID

  5697H7400

Applicable component levels

• R310 PSY UI16009

     UP14/03/22 P F403

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.