IEF702I

Explanation
The system could not allocate one or more devices
to a step.
Possible causes are:The UNIT parameter(s) in a DD statement, or combination of DD
statements, specified a device collection and requested more than
the number of devices available within the collection. This can occur
due to a volume serial number in conflict between DD statements, such
as when stacking multiple data sets onto one or more tape volumes
within a single step. This can also occur because, under certain conditions,
the number of devices available within a collection can be reduced.Any devices in the collection that are boxed are unavailable. 
Any devices in the collection that already contain the data set
being created (possibly an uncataloged duplicate data set) are unavailable.

For DASD, the required volume is not online (perhaps no longer
exists) and either volume mounting is not allowed or there are no
offline devices in the specified or defaulted UNIT name.
The required volume is online but outside the requested UNIT name
and there are no offline devices within the UNIT name.
The required volume is online and within the requested UNIT name,
but is on a different device type (e.g., 3380 vs 3390).
For DASD, the request is for a new non-SMS-managed data set but
a volume serial number was not supplied and no volumes in the UNIT
name are mounted STORAGE.
The request is for a new non-SMS-managed data set, but all of
the devices within the requested UNIT name are SMS-managed.
For tape, all devices within the UNIT name are either offline
or allocated, and waiting for offline and/or allocated devices is
not allowed.
JES3 selected a device which is in use by a system function (UCBNALOC).
The JES3 tape definitions are incorrect.

In the message text: jobname
The name of the job.
procstep
The name of the step in the procedure.
stepname
The name of the job step.
ddname
The name of the DD statement.
+ xxx
The relative position of a data set within a concatenation of
data sets, including all data sets implicitly concatenated (through
GDG ALL or OPTCD=B requests). See z/OS MVS JCL User's Guide for
more information on GDG ALL or OPTCD=B requests when used within a
set of concatenated data sets. The first data set of a concatenation
would be +000, but the value +000 is never shown.

System action
The system ends the job.

System programmer response
If the device(s) should have been
available based on the configuration defined to the system, search
problem reporting data bases for a fix for the problem. If no fix
exists, contact the IBM® Support Center.

Programmer response
Check the UNIT parameter(s) to make sure that the device collections
can supply the number of devices needed, taking into account the conditions
noted. If necessary, change the UNIT parameters.
Ensure that the desired volume serial number was specified and
spelled correctly.  Also ensure that the volume is online, within
the correct esoteric, and that the device is of the proper type.
Ensure that at least one volume within the requested UNIT name
has sufficient space and is mounted STORAGE, or specify a volume serial
number.
To create a non-SMS-managed data set, select a non-SMS-managed
UNIT name.
Change the dynamic allocation to allow waiting for offline devices,
allocated devices or both offline and allocated devices.
Wait until the system function (for example, SWAP) has completed.
Verify that the JES3 tape definitions (SETNAME, HWSNAME, DEVICE)
are correct.

Resubmit the job.

Source
Allocation

Module
IEFAB479, IEFAB482, IEFAB485, IEFAB486,
IEFAB4FJ

Routing code
11/Note 36

Descriptor code
-