OA43189: MSGIGD1012I DATA SET ALLOCATION FAILED WHEN USING UNIT=AFF AND ATTEMPTING TO MIGRATE FROM ONE TAPE LIBRARY TO ANOTHER.

APAR status

• Closed as fixed if next.

Error description

• Customer is migrating from one tape library to another.
  They have many jobs specifying UNIT=AFF and have changed all
  of their ACS routines to redirect all new allocations to the
  new tape library. However, SMS currently will not allow UNIT=AFF
  new allocations to be directed to a different ATL or MTL.  In
  other words, UNIT=AFF MUST stay in the same ATL.
  same ATL.
  
  The issue (lots of old JCL with UNIT=AFF where the old dataset
  is in one ATL and they want the new allocation coded in JCL with
  UNIT=AFF to go into the new different ATL). In other words you
  cannot break unit affinity which should be allowed.
  
  Various errors can occur depending on how your ACS routines are
  coded which include:
  msgigd1012I data set allocation failed.
  When assigning multiple storage groups to the data set which has
  UNIT=AFF receive msgcbr4195I LACS retry error CODE=140169
  If the input storage group is added and put into DISNEW status,
  msgigd3330I CBRXLCS error and msgigd306i rc12 rsn46 is issued.
  

Local fix

• Contact L2
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: HDZ1D10 USERS AND ABOVE                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: SEE ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  SUMMARY: SMS DID NOT ALLOW UNIT=AFF NEW ALLOCATIONS TO BE
  DIRECTED TO A DIFFERENT TAPE STORAGE GROUP FROM THE AFF'ED DATA
  SET.
  

Problem conclusion

Temporary fix

Comments

• CONTROL NUMBER: SM01810
  
  This APAR is being closed FIN with concurrence from the
  submitting customer. This means that a Solution to this APAR
  is expected to be delivered from IBM in a release (if any)
  to be available within the next 36 Months.
  
  The problem is fixed in z/OS DFSMS V2R2.
  

APAR Information

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

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

Fix information

Applicable component levels