OA48123: ABEND213 RC04 OR RC2C MAY BE SEEN AFTER ALLOCATING A GDG SINGLE REQUEST WHILE HSM VOLUME MIGRATION TO TAPE IS UNDERWAY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Currently, when allocating a GDG single dataset by relative
  generation number, Allocation will first will make a call
  to Catalog to locate the fully qualified dataset name and
  make a second call to retrieve the volser.
  We will then issue a SYSDSN enqueue request on the fully
  qualified dataset name and may wait if it is unavailable.
  .
  During HSM migration, HSM holds the SYSDSN enqueue.  After
  migration, the volser status in Catalog will change to
  MIGRAT.
  Therefore, the volser Allocation previously retrieved from
  the catalog is no longer valid.
  .
  Allocation needs to request the SYSDSN enqueue  before
  calling Catalog to retrieve volume information to ensure we
  get the correct volser if there is an HSM migration
  underway.
  

Local fix

• -
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All HBB7790 and above installations.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND213 RC04 or RC2C may be issued     *
  *                      after allocating a data set while the   *
  *                      data set is being migrated.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When allocating a generation data set (GDS) or an alias,
  Device Allocation resolves the real data set name and volume
  information using the Catalog.  The data set is serialized after
  resolving the data set name.  This results in a window where
  the volume information has been resolved but the data set is
  not yet serialized.
  
  Should the volume information change for these types of data
  sets during this window, most likely because the data set is
  migrated, the system will continue to use the stale data set
  information to allocate the data set.  This can result in
  ABEND213 RC04 or RC2C.
  
  This is most likely to occur when the ALLOCxx option SYSTEM
  BATCH_RCLMIGDS(PARALLEL) is in effect.
  

Problem conclusion

• Device Allocation processing is changed to serialize the data
  set name for aliases and GDSs prior to resolving the volume
  information for the data set.
  

Temporary fix

Comments

• ×**** PE15/10/09 FIX IN ERROR. SEE APAR OA49107  FOR DESCRIPTION
  ×**** PE16/04/21 FIX IN ERROR. SEE APAR OA50350  FOR DESCRIPTION
  

APAR Information

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

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

  UA78910 UA78918

Modules/Macros

• IEFAB452 IEFAB454 IEFAB456 IEFAB457 IEFAB459
  IEFAB461 IEFAB462 IEFAB466 IEFAB469 IEFCTFMT
  

Fix information

• Fixed component name

  ALLOCATION

• Fixed component ID

  5752SC1B4

Applicable component levels

• R7A0 PSY UA78910

     UP15/09/29 P F509

• R790 PSY UA78918

     UP15/09/29 P F509

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.