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


$HASP114

z/OS JES2 Messages
SA32-0989-01

$HASP114

Explanation

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

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

>--jobname--INVALID EXECUTION NODE-----------------------------><

While parsing JCL statements, JES2 detected an error on the /*XEQ or /*ROUTE XEQ 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:
execution node not valid
The node specified on the XEQ statement is not a valid NJE node or DESTID of a valid node.
missing positional operand
The required node name operand was not specified on the JCL statement.
Note: A jobid can precede $HASP114. 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 the correct format of the /*XEQ control statement. Correct the control statement 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