PK38104: ALLOW RECALL OF THE MIGRATED DBRMLIB/ OR LOADLIB FROM BND006 THRU BND036 PROGRAMS. TO SATISFY REQUIREMENT MR0122076341.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• This APAR is taken to satisfy the rquest made via Marketing
  Requirement number MR0122076341:
  .
  "For all reports, it would be an improvement if a job submitted
  would wait for a migrated data set to be recalled.  When a
  customer tried searching DBRMLIBs that had migrated for example,
  in BNDA030, rather than being able to submit the job, they got a
  JCL error.  They had to manually go into 3.4 and recall all
  migrated data sets.  In the case where you are concatenating
  many libraries, many of which may be migrated, this is very
  inconvenient.  Just as DB2 waits for data sets to be recalled
  for a period of RECALLD (often set between 2 - 3 minutes), it
  would be helpful if Bind Manager could do the same."
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Bind Manager.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR is taken to satisfy the       *
  *                      request made via Marketing              *
  *                      Requirement number MR0122076341:        *
  *                      "For all reports, it would be an        *
  *                      improvement if a job submitted would    *
  *                      wait for a migrated data set to be      *
  *                      recalled.  When a customer tried        *
  *                      searching DBRMLIBs that had migrated    *
  *                      for example, in BNDA030, rather than    *
  *                      being able to submit the job, they got  *
  *                      a JCL error.  They had to manually go   *
  *                      into 3.4 and recall all migrated data   *
  *                      sets.  In the case where you are        *
  *                      concatenating many libraries, many of   *
  *                      which may be migrated, this is very     *
  *                      inconvenient.  Just as DB2 waits for    *
  *                      data sets to be recalled for a period   *
  *                      of RECALLD (often set between 2 - 3     *
  *                      minutes), it would be helpful if Bind   *
  *                      Manager could do the same."             *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

Temporary fix

Comments

• APPLY the PTF.
  

APAR Information

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

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

  UK21628

Modules/Macros

•    BNDJ006
  

Fix information

• Fixed component name

  DB2 BIND MANAGE

• Fixed component ID

  5655E4301

Applicable component levels

• R230 PSY UK21628

     UP07/01/30 P F701

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.