Explanation
A START command invoked a cataloged procedure or
job. The system detected one of the following error conditions:
- The member specified in the START command does not exist.
- The cataloged procedure contains incorrect JCL statements.
- The job contains incorrect JCL statements.
System action
The system rejects the command.
Operator response
Contact the system programmer. When the system
programmer directs, enter the command again.
System programmer response
Do the following:
- Look in the system output (SYSOUT) for messages associated with
this command. These messages describe any 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, then it may be
necessary to change it temporarily to a “real” message
class in order to get the SYSOUT for the failing START command. This
can be accomplished in either of two ways:
- Add the desired MSGCLASS to the START command. For example:
- S procedurename,MSGCLASS=A
- Change the MSGCLASS for all STCs via a $TJOBCLASS command and
then change the MSGCLASS back to what it was. For example:
- $TJOBCLASS(STC),MSGCLASS=A
- Run the failing started task
- $TJOBCLASS(STC),MSGCLASS=Z
Once the failing JCL statements are identified, correct those
JCL statements in the procedure or job. Ask the operator to enter
the command again.
- If the command was entered correctly, run the IEBPTPCH utility
to print the cataloged procedure or job that was to be invoked by
the START command. Check for, and correct, any incorrect JCL statements
in the procedure or job. After making corrections, ask the operator
to enter the command again.
- If the command continues to fail, search problem reporting data
bases for a fix for the problem. If no fix exists, contact the IBM® Support
Center.
Source
Module
Routing code
Descriptor code