PM03653: IT APPEARS DRF MAY BE REQUESTING AN ESOTERIC DRIVE THAT DOES NOT EXIST.

APAR status

• Closed as program error.

Error description

• IT APPEARS DRF MAY BE REQUESTING AN ESOTERIC DRIVE THAT DOES
  NOT EXIST.
  DRF continues processing after mount messages IEC501A.
  DRF should wait for a tape drive to become available.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users who have archived logs or image    *
  *                 copy data sets on tape.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When log data sets are archived by      *
  *                      HSM and are needed in recovery, DRF     *
  *                      may not wait for the log to be          *
  *                      restored resulting in a dynamic         *
  *                      allocation failure for the log data     *
  *                      set and a subsequent abend.  Also,      *
  *                      when multiple address spaces are        *
  *                      started to restore image copies and     *
  *                      there are not enough tape drives        *
  *                      available, the IEF238D message issued   *
  *                      does not include the WAIT option to     *
  *                      allow the job to wait on a tape drive   *
  *                      to become available.                    *
  *                                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  When input logs, change accumulation or image copy
  data sets have been archived or are on tape and no
  tape units are available, then DRF may experience
  dynamic allocation failures and subsequent abends.
  

Problem conclusion

• Code has been changed to set some new flags on the
  dynamic allocation request to allow the DRF job
  to wait on a data set which is being restored and
  also allow the customer to choose the wait option
  when a tape unit is not currently available.
  

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:

  UK53703

Modules/Macros

• FRXIDYN0 FRXRVGB  FRXYADY0
  

Fix information

• Fixed component name

  IMS DB RECOVERY

• Fixed component ID

  5655I4400

Applicable component levels

• R310 PSY UK53703

     UP10/01/23 P F001