This section describes the previous log messages for Job Execution Control that do not have message labels.
[Description]
An internal error occurred.
[Parameter]
error: Error contents
[System Action]
Aborts processing.
[User Response]
Collect the information about server functions by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The user name of the user who executed the command contains one or more invalid characters.
[System Action]
Aborts processing.
[User Response]
Check the user name that can use the command, and re-enter the command using a valid user name.
[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.
[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.
[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.
[Description]
The command was not executed as a Jobscheduler job.
[System Action]
Aborts processing.
[User Response]
Register the command in a Jobscheduler job and execute it.
[Description]
Access to the remote machine failed.
[Parameter]
cmdline: Command that failed to access the remote machine
error code: Error code output when failed to access to the remote machine
[System Action]
Aborts processing.
[User Response]
Ensure that the remote machine can be accessed, and re-enter the command.
[Description]
Failed to access the remote machine.
[Parameter]
reason: Error message
[System Action]
Aborts processing.
[User Response]
Refer to the error message to check if it is possible to access the remote machine, and take the required action.
[Description]
The file could not be read or written to.
[Parameter]
file path: Path of the file that failed to be read or written to
[System Action]
Aborts processing.
[User Response]
Ensure that the file path exists, you have privileges for the file, and the disk has free space. Then re-enter the command.
[Description]
Conversion of the character set has failed.
[Parameter]
error code: Error code output when failed to convert the character set
[System Action]
Aborts processing.
[User Response]
One of the following is possible: After taking the appropriate action, re-enter the command.
Can the character set that was specified on the local server be used on a remote machine? Change to a character set that is usable.
Have you sent and executed LANG for the local server in accordance with the ssh settings? Review the ssh settings.
[Description]
Failed to create the key pair.
[Parameter]
error: Error contents
[System Action]
Aborts processing.
[User Response]
Eliminate the cause of the error by referring to the error contents, and re-enter the command.
[Description]
Failed to delete the file.
[Parameter]
file path: File path
[System Action]
Aborts processing.
[User Response]
Check the specified file path.
[Description]
Failed to lock the file.
[Parameter]
file path: File path
error code: Error code output when file lock failed
[System Action]
Aborts processing.
[User Response]
Eliminate the cause of the error by referring to the error contents, and re-enter the command.
[Description]
Failed to output the log.
[Parameter]
error: Error contents
[System Action]
Aborts processing.
[User Response]
Eliminate the cause of the error by referring to the error contents, and re-enter the command.
[Description]
Failed to set the permissions.
[Parameter]
file path: File path
[System Action]
Aborts processing.
[User Response]
Check the specified file path.
[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.
[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.
[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"
[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.
[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.
[Description]
This command cannot be executed concurrently.
[System Action]
Aborts processing.
[User Response]
Wait until the same command completes, and re-execute the command.
[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.
[Description]
One of the key pair files does not exist.
[System Action]
Aborts processing.
[User Response]
Delete the corresponding key pair, and create the key pair again.
[Description]
The command contains an invalid parameter.
[Parameter]
option: Option corresponding to the invalid parameter
[System Action]
Aborts processing.
[User Response]
Correct the parameter, and re-enter the command.
[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.
[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.
[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.
[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.
[Description]
The message means one of the following:
The corresponding key pair has already been created.
The file already exists in the specified output destination.
[Parameter]
file path: File path
[System Action]
Aborts processing.
[User Response]
If the key pair has already been created, the key pair cannot be created again. Delete the key pair, and execute the command again.
If the file already exists in the specified output destination, change the specified file path, and execute the command again.
[Description]
The key pair file does not exist.
[Parameter]
file path: File path
[System Action]
Aborts processing.
[User Response]
Create a key pair, and re-enter the command.
[Description]
Environment variable MJRMTJOB_JAVA_HOME value is incorrect.
[System Action]
Aborts processing.
[User Response]
Correct the value of the system environment variable MJRMTJOB_JAVA_HOME, and restart the Job Execution Control service.
[Description]
The specified user does not exist.
[Parameter]
user name: User name
[System Action]
Aborts processing.
[User Response]
Specify the name of the user that exists, and re-enter the command.
[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.
[Description]
The correct mjkeygen.exe command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct mjrmtjob command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[Description]
The correct mjrmtjob.exe command syntax is shown.
[User Response]
Specify command parameters in the correct format.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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]
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.
If this error cause recurs, collect the information about Job Execution Control by using the Maintenance Information Collection Tool and contact Fujitsu technical support
[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.
[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.
[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]
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.
If this error cause recurs, collect the information about Job Execution Control by using the Maintenance Information Collection Tool and contact Fujitsu technical support.
[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.
[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.
