3.10.2 Messages without Message Labels

This section describes the previous log messages for Job Execution Control that do not have message labels.

-R resource name must be ended with "sh" or "ex" after a "," character.

See "3.9 Messages Output by Job Execution Control Command".

Defined resource exceeds upper limit.

[Description]

The maximum number of resource control statement definitions has been exceeded.

[System Action]

Stops job submit processing.

[User Response]

Delete unnecessary resource control statements definitions, and then submit the job again.

Error in sequence describing JCL control statement.line=<row>.

[Description]

JCL control statements have been entered in the wrong order.

[Parameter]

row: Line number of the JCL control statement where the error occurred

[System Action]

Stops job submit processing.

[User Response]

Correct the order of the JCL control statements, and then submit the job again.

Exclusive operand specified.

[Description]

Operands that cannot be combined have been specified.

[System Action]

Stops job submit processing.

[User Response]

Delete any unnecessary operands and then submit the job again.

Failure in retrieving printer data.

[Description]

Information for the printer specified in the JCL prt operand could not be obtained.

[System Action]

Stops job submit processing.

[User Response]

Check whether the printer can be used.

Insufficient space for storing jobstep structure. line=<row>.

[Description]

There is insufficient management spacefor the job step.

[Parameter]

row: Line number of the JCL control statement where the error occurred

[System Action]

Stops job submit processing.

[User Response]

Resubmit the job after making the number of job steps 186 or fewer.

Insufficient space for path name. line=<row>.

[Description]

There is insufficient management space for the path control statement.

[Parameter]

row: Line number of the JCL control statement where the error occurred

[System Action]

Stops job submit processing.

[User Response]

Resubmit the job after modifying the following so that each is no more than 4,096 bytes:

"Total length of the paths specified in path control statements for the entire job" + "Number of path control statements for the entire job"
For each single job step, "Total length of the paths specified in path control statements for job steps" + "Number of path control statements for job steps"

Insufficient space for file name. line=<row>.

[Description]

There is insufficient management space for the file control statement.

[Parameter]

row: Line number of the JCL control statement where the error occurred

[System Action]

Stops job submit processing.

[User Response]

Resubmit the job after either reducing the number of file control statements or making the file names shorter.

Multiple definitions for same resource name.

[Description]

The resource name is duplicated in the resource control statement.

[System Action]

Stops job submit processing.

[User Response]

Delete unnecessary resource control statements with the resource name duplicated, and then submit the job.

No valid JCL control text.

[Description]

The necessary JCL control statements are omitted.

[System Action]

Stops job submit processing.

[User Response]

Specify the missing JCL control statements, and then rerun the job.

prt parameter is not specified.

[Description]

The prt operand is omitted in the specified JCL parameter.

[System Action]

Stops job submit processing.

[User Response]

Specify the prt operand in the specified parameter, and rerun the job.

Queue <queuename> does not exist.

See "3.9 Messages Output by Job Execution Control Command".

[Windows]Request is rejected by Systemwalker MpMjes service.

See "3.9 Messages Output by Job Execution Control Command".

Request timed out.

See "3.9 Messages Output by Job Execution Control Command".

Same jobstep name is already defined.

[Description]

The same job step name is defined in multiple job steps.

[System Action]

Stops job submit processing

[User Response]

Change the duplicated job step name to a different one, and rerun the job.

Specified printer no. exceeds the upper limit.

[Description]

Too many printers are specified in the prt operand of JCL.

[System Action]

Stops batch processing.

[User Response]

Delete the unnecessary printers specified in the prt operand, and rerun the job.

Specified printer not found.

[Description]

The specified printer is not found in the prt operand of JCL.

[System Action]

Stops job submit processing.

[User Response]

Specify the printer name registered in the print manager in the prt operand, and rerun the job.

The step name of skip operand is undefined. line=X.

[Description]

The job step name is not found for the skip destination specified in the skip operand of the stepstart control statement.

[Parameter]

X: Line number

[System Action]

Stops job submit processing.

[User Response]

Correct the job step name specified in the skip parameter of the stepstart control statement, and rerun the job.

Users are restricted by the user control list for job execution.

[Description]

The job failed to be submitted because the user specified by job execution privileges is not listed in the user control list for job execution.

[System Action]

Stops processing.

[User Response]

For job execution privileges, specify one of the user names listed in the user control list for job execution

Refer to "Job Execution Privileges" in the Systemwalker Operation Manager Installation Guide for details on job execution privileges.

Value violating the rules cannot be specified in JCL operand. line=<row>.

[Description]

The value specified for the JCL control statement operand is invalid.

[Parameter]

row: Row number of the JCL control statement where an error occurred

[System Action]

Job submission is canceled.

[User Response]

Execute the job after specifying a valid value to the operand.

Write-Open error in inline file.

[Description]

A write-open error occurred in the Job Execution Control operation file (inline file).

[System Action]

Job submission is canceled.

[User Response]

Check whether there is any available space on the spool directory of the Job Execution Control, and execute the job after confirming that there is enough space to create a temporary file.

System: An exception occurred while processing the job-name(jobno.hostname). Exception code: code. There may be a problem in the application or the system environment. Find out the cause of this exception. Refer to Systemwalker Operation Manager Troubleshooting Guide.

[Description]

The job ended with an exception. The executed application or system environment may have a problem.

[Parameters]

job-name: Job name specified to submit the job

jobno: Job number assigned by Job Execution Control

hostname: Name of the host that submitted the job

code: End code of the job (Exception code)

[System Action]

Aborts processing. The job ends with end code "code".

[User Response]

Check the exception cause.

System: An exception occurred while processing the job-name(jobno.hostname). Application name: app-name. Exception code: code. There may be a problem in the application or the system environment. Find out the cause of this exception. Refer to Systemwalker Operation Manager Troubleshooting Guide.

[Description]

The job ended with an exception. The executed application or system environment may have a problem.

[Parameters]

job-name: Job name specified to submit the job

jobno: Job number assigned by Job Execution Control

hostname: Name of the host that submitted the job

app-name: Name of the application that caused the exception

code: End code of the job (Exception code)

[System Action]

Aborts processing. The job ends with end code "code".

[User Response]

Check the exception cause.

System: An exception occurred while processing the jobstep jobstep. Application name: app-name. Exception code: code. There may be a problem in the application or the system environment. Find out the cause of this exception. Refer to Systemwalker Operation Manager Troubleshooting Guide.

[Description]

The job step ended with an exception. The executed application or system environment may have a problem.

[Parameters]

jobstep: Job step name specified in JCL

app-name: Name of the application that caused the exception

code: End code of the job (Exception code)

[System Action]

Aborts processing. The job ends with end code "code".

[User Response]

Check the exception cause.

System: An exception occurred while processing the jobstep jobstep. Exception code: code. There may be a problem in the application or the system environment. Find out the cause of this exception. Refer to Systemwalker Operation Manager Troubleshooting Guide.

[Description]

The job step ended with an exception. The executed application or system environment may have a problem.

[Parameters]

jobstep: Job step name specified in JCL

code: End code of the job (Exception code)

[System Action]

Aborts processing. The job ends with end code "code".

[User Response]

Check the exception cause.

Job Execution Control : Failed in starting job <jobname(jobno.hostname)> <reason>

[Description]

Failed to start the job "jobname(jobno.hostname)".

[Parameters]

jobname: Job name

jobno: Job No.

hostname: Host name

reason: Error message

[System Action]

Stops the job. This error will not affect other jobs.

[User Response]

Check the end code of the job that could not be started, using a job log or the mjsview command. Refer to the description of the end code in the Systemwalker Operation Manager Reference Guide, and remedy the error cause.

[System Administrator Response]

If this error cause recurs, collect the information about Job Execution Control by using the Maintenance Information Collection Tool and contact Fujitsu technical support

Job Execution Control: The job job-name(jobno.hostname) has been cancelled by the user or due to stop of the Job Execution Control service. Exit code: 0x40000222

[Description]

The job was ended forcibly by forced-end processing or because the job execution control service stopped.

[Parameters]

job-name: Job name specified to submit the job

jobno: Job number assigned by Job Execution Control

hostname: Name of the host that submitted the job

[System Action]

Aborts processing. The job ends with end code "0x40000222".

[User Response]

Rerun the job if necessary.

Job Execution Control: The job job-name(jobno.hostname) has been cancelled because its processing time exceeded the maximum. Exit code: 0x40000322

[Description]

The job was ended forcibly because the execution lapse time exceeded the limit value.

[Parameters]

job-name: Job name specified to submit the job

jobno: Job number assigned by Job Execution Control

hostname: Name of the host that submitted the job

[System Action]

Aborts processing. The job ends with end code "0x40000322".

[User Response]

Rerun the job if necessary.

Job execution control:Failure in starting jobstep <jobstep-name>.<reason>

[Description]

Failed to start the job step "jobstep-name".

[Parameters]

jobstep-name: Job step name

reason: Error message

[System Action]

Stops the job. This error will not affect other jobs.

[User Response]

Check the end code of the job step that could not be started, using a job log or the mjsview command. Refer to the description of the end code in the Systemwalker Operation Manager Reference Guide, and remedy the error cause.

[System Administrator Response]

If this error cause recurs, collect the information about Job Execution Control by using the Maintenance Information Collection Tool and contact Fujitsu technical support.

Job Execution Control: The jobstep jobstep has been cancelled by the user or due to stop of the Job Execution Control service. Exit code: 0x40000222

[Description]

The job step was ended forcibly by forced-end processing or because the job execution control service stopped.

[Parameter]

jobstep: Job step name specified in JCL

[System Action]

Aborts processing. The job ends with end code "0x40000222".

[User Response]

Rerun the job if necessary.

Job Execution Control: The jobstep jobstep has been cancelled because its processing time exceeded the maximum. Exit code: 0x40000322

[Description]

The job step was ended forcibly because the execution lapse time exceeded the limit value.

[Parameter]

jobstep: Job step name specified in JCL

[System Action]

Aborts processing. The job ends with end code "0x40000322".

[User Response]

Rerun the job if necessary.