Operator console form:

>>-jobname--Illegal JOB card--reason---------------------------><

>>-jobname--illegal JOB card--reason---------------------------><

>>-jobname--Invalid JOB statement--reason----------------------><

JESYSMSG message form:

>>-reason------------------------------------------------------><

While parsing JCL statements, JES2 detected an error on the JOB 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:

account field incorrect

JES2 requires both an account number and a room number. This requirement is due to the ACCTFLD=REQUIRED on the JOBDEF initialization statement. Check for a missing or incorrect account number or room number.

ERROR DETECTED BY EXIT nnn OR error detected by exit nnn

The listed exit has detected an error on the JOB statement. See processing in that exit to determine the cause of the error.

MULTIPLE JOB CARDS DETECTED

Under normal conditions, multiple job statements are allowed. For example, they are allowed from an internal reader (a SUBMIT from ISPF EDIT). However, JES2 does not permit multiple job statements in the following situations:

• An NJE job stream from VM RSCS or from another JES2 node that uses /*XMIT.
• Started jobs that use IEFJOBS support, where only one JOB card is permitted in the started member.

If the problem is a started job, for example, and this message is preceded by $HASP100 ON STCINRDR, see z/OS MVS JCL Reference for more information.

value of accounting string is too long

The accounting string positional operand is longer than the maximum value allowed.

value of programmer name is too long

The programmer name positional operand is longer than the maximum value allowed.

value of keyword= exceeds n characters

The value provided for the specified keyword exceeds the maximum value allowed.

value of keyword= has too many operands

The specified keyword is a list for which too many values have been specified.

value of keyword= parameter is greater than nnn

The specified keyword has a value larger than the maximum allowed for the keyword.

value of keyword= parameter is not numeric

The specified keyword is required to be numeric.

value of keyword= parameter is not valid

The value provided for the specified keyword is not valid.

value of keyword= parameter is null

The specified keyword cannot be specified as null.

value of CLASS= parameter is an inactive class

The specified class is not valid because the class is inactive.

Value of UJOBCORR has embedded blanks

The user portion of the job correlator cannot contain embedded blanks, and an embedded blank was provided.

Value of UJOBCORR has invalid characters

The user portion of the job correlator contains characters other than alphanumeric, national (@, #, $), or underscore (_) characters.

Value of UJOBCORR has greater than 32 characters

The user portion of the job correlator is limited to 32 characters, and more than 32 characters were supplied.

default class cccccccc is not valid

The job class used for the job by default is not valid.

default class cccccccc is not active

The job class used for the job by default is not active.

CLASS cccccccc is not valid

The job class cccccccc is not valid.

CLASS cccccccc is an inactive class

The job class cccccccc is not active.

keyword= not valid for this job type

The keyword, and value, are not allowed for a started task.

SYSTEM and SYSAFF cannot both be specified

SYSTEM= and SYSAFF= are mutually exclusive keywords.

SYSTEM specified more than once

SYSTEM= cannot be specified more than once.

SYSAFF not valid, begins with "-" on second or later value

"-" is allowed only before the first member name.

SYSAFF of –ANY not valid

It is not valid to remove all members from SYSAFF by using "-ANY".

SYSTEM= names of JGLOBAL and JLOCAL must not appear with other names

The JES3 generic names of JGLOBAL and JLOCAL cannot be specified with other SYSTEM names.

SYSTEM of –ANY not valid

It is not valid to remove all systems from consideration by using "-ANY".

SYSTEM not valid, begins with "-" on second or later value

"-" is allowed only before the first system name.

SYSTEM= values of JGLOBAL and JLOCAL are ignored

JGLOBAL and JLOCAL are used in a JES3 environment. They are tolerated in a JES2 environment, but provide no function. This situation results in:

• The message ID and the reason text is the only text written
• The message appears only in the JESYSMSG data set
• The condition is treated as a warning, not an error.