$HASP107

jobname

Explanation

>>-jobname--NON-VALID--statement--STMT,--reason----------------><

OR

>>-jobname--Non-valid--statement--STMT,--reason----------------><

 While parsing JCL statements, JES2 detected
an error on the xxxxxxxx statement. The problem
encountered is identified by reason.
 In
the message text:  jobname
The name of the affected job.
statement
The JCL statement affected.

 reason is one of the following: KEYWORD LENGTH NOT VALID
A keyword longer than 8 characters was encountered.
VALUE FOR xxxxxxxx KEYWORD NOT VALID
The value for the keyword listed is syntactically not valid (for
example, unbalanced parentheses or apostrophes might exist).
UNEXPECTED KEYWORD DETECTED – xxxxxxxx
An unknown keyword was encountered on the statement.
UNEXPECTED POSITIONAL OPERAND DETECTED
A positional operand was encountered where one was not expected.
Typically this is caused by a missing '=' or improper apostrophes.
VALUE FOR POSITIONAL OPERAND NOT VALID
A syntactically invalid positional operand was detected.
value for DLM keyword not valid
The syntax of the delimiter keyword value is incorrect.

Note: A job identifier may precede
$HASP107. See JES2 message format.

System action
 The message is written to the JCL data set and
JES2 ends input service processing for the job. The job is queued
for output processing.

Operator response
 None.

Programmer response
 See z/OS MVS JCL Reference for
correct forms of the listed statement. Correct the JCL error and rerun
the job.

Module
 HASCSRIP
 Routing
Code: 7
 Descriptor Code: 4