IEE132I

Explanation
A START command invoked a cataloged procedure.
While allocating the device specified on the command, the system detected
an error.

System action
The system rejects the command.

Operator response
Contact the system programmer. Enter the command
again, as directed by the system programmer.

System programmer response
Do the following:
 Look in the system output (SYSOUT) data set for messages associated
with this START command. These messages describe errors found in the
source JCL or in the overriding JCL statements generated from the
START command.If the MSGCLASS for Started Tasks is a DUMMY class,
you may need to change it to a real message class temporarily in order
to get the JES Job Log for the failing START command. Do this in one
of the following ways:
Add the desired MSGCLASS to the START command.  For example, add:S procedurename,MSGCLASS=A

Change the MSGCLASS for all STCs using a $TJOBCLASS command, and
then change the MSGCLASS back to what it was.  For example:First change the MSGCLASS using the $TJOBCLASS command:$TJOBCLASS(STC),MSGCLASS=A

Now run the failing started task.
Finally, change the MSGCLASS back to what it was using a $TJOBCLASS
command:$TJOBCLASS(STC),MSGCLASS=Z

If the command fails again, search problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM® Support
Center.

Once the failing JCL statements are identified, correct those
JCL statements in the procedure or job, or any catalog entries which
caused the error messages to be issued. Ask the operator to enter
the command again. 

Source
Master scheduler

Module
IEESB605

Routing code
2,10,*

Descriptor code
3