SB37 abend during the allocation of the files

Products

• Allocate DASD Space and Placement

Issue/Introduction

For some reason batch jobs are not creating datasets in the proper pools.  Because datasets are not allocating to the proper volumes, the EOV processing is not being invoked and jobs are failing on B37 abends.  

Noticed that a number of these jobs are getting the following message 

VAM0033 CANNOT GET UNITS FOR UNIT NAME 3390   

HCD was activated recently. 

Cause

 

Resolution

 

VAM0033

CANNOT GET UNITS FOR UNIT NAME <xxxxxxxx>
Reason:
The unit name specified a generic or esoteric name for which there were no corresponding units. This should only occur when your ASR is setting the &UNIT variable to a unit name that has not been defined in the Eligible Device Table (EDT) of your system.
Action:
Update your ASR to only change & UNIT to a unit name that has been defined to your EDT.

When a new HCD is activated, a VAM REFRESH command should be performed immediately to rebuild the internal EDT and be in synch with the new EDT .