z/OS JES2 Messages
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


$HASP111

z/OS JES2 Messages
SA32-0989-01

$HASP111

Explanation

Read syntax diagramSkip visual syntax diagram
>>-jobname--Invalid /*ROUTE card--reason------------------------>

>--jobname--Invalid /*ROUTE XEQ card--reason-------------------->

>--jobname--INVALID PRINT/PUNCH ROUTE--------------------------><

While parsing JCL statements, JES2 detected an error on the /*ROUTE statement. The problem encountered is identified by reason.

In the message text:
jobname
The name of the affected job.
The reason is one of the following strings:
destination not valid
The destination that is specified on the /*ROUTE statement is not valid, or this user does not have access to the destination.
missing positional operand
The destination operand was not specified.
not valid for this job type
A ROUTE XEQ card was specified for a started task.
PRINT, PUNCH, OR XEQ required
The first positional operand on a /*ROUTE statement must be one of the values listed.
Note: A jobid can precede $HASP111. See JES2 message format.

System action

Start of changeThe message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion unless the message is a warning only.End of change

Operator response

None

Programmer response

See z/OS MVS JCL Reference for correct forms of the /*ROUTE statement. Correct the JCL error and rerun the job.

Module

HASCINJR, HASCSRIP, HASPRDR

Routing Code: 7

Descriptor Code: 4

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014