This section describes the messages output by Job Execution Control commands.
[Description]
Multiple opt chars options were specified in the batch file.
[Parameter]
opt chars: Character string of the option
[System Action]
Aborts processing.
[User Response]
Specify the option only once, and re-enter the command.
[Description]
Multiple opt chars options were specified on the command line.
[Parameter]
opt chars: Character string of the option
[System Action]
Aborts processing.
[User Response]
Specify the option only once, and re-enter the command.
[Description]
The specified dispatch priority exceeds level 4.
The specified dispatch priority exceeds level 19.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority between levels 0 and 4, and re-enter the command.
Specify the dispatch priority between levels -20 and 19, and re-enter the command.
[Description]
The dispatch priority is not specified with a numerical value.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority between levels 0 and 4, and re-enter the command.
Specify the dispatch priority between levels -20 and 19, and re-enter the command.
[Description]
The specified dispatch priority is less than zero (0).
The specified dispatch priority is less than -20.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority between levels 0 and 4, and re-enter the command.
Specify the dispatch priority between levels -20 and 19, and re-enter the command.
[Description]
The -jft option is not specified together with the -rh option.
[System Action]
Aborts processing.
[User Response]
Specify the -jft option together with the -rh option, and re-enter the command.
[Description]
The -jo option is not specified together with the -env option.
[System Action]
Aborts processing.
[User Response]
Specify the -jo option together with the -env option, and re-enter the command.
[Description]
The specified elapsed-time limit exceeded the maximum 99999999.
[System Action]
Aborts processing.
[User Response]
Specify the elapsed-time limit between 1 and 99999999, and re-enter the command.
[Description]
The elapsed-time limit is not specified with a numerical value.
[System Action]
Aborts processing.
[User Response]
Specify the elapsed-time limit between 1 and 99999999, and re-enter the command.
[Description]
The specified elapsed-time limit is too low.
[System Action]
Aborts processing.
[User Response]
Specify the elapsed-time limit between 1 and 99999999, and re-enter the command.
[Description]
The specified dispatch priority exceeded the maximum 63.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority between levels 0 and 63, and re-enter the command.
[Description]
The dispatch priority is not specified with a numerical value.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority with a digit between levels 0 and 63, and re-enter the command.
[Description]
The -R option cannot specify the number of resources for a resource name not defined in the resource definition file.
[System Action]
Stops processing.
[Corrective Measures]
Add a definition to the resource definition file.
Alternatively, specify "sh" or "ex" instead of the number of resources and run the command again.
[Description]
More than one resource with the same name was specified with the -R option. The -R option cannot be used to specify multiple resources with the same name.
[System Action]
Stops processing.
[Corrective Measures]
Run the command again with each resource name specified only once.
If a job uses multiple resources with the same name, specify the number of resources to be used after the comma following the resource name.
[Description]
After a "," character, resource names must end with "sh", "ex" or the number of resources used (between 1 and 1024).
[System Action]
Stops processing.
[User Response]
Specify "sh", "ex" or the number of resources used (between 1 and 1024) after the "," character, and then run the command again.
[Description]
The specified retry count exceeded the maximum 20.
[System Action]
Aborts processing.
[User Response]
Specify the retry count between 1 and 20, and re-enter the command.
[Description]
The specified retry count is not specified with a numerical value.
[System Action]
Aborts processing.
[User Response]
Specify the retry count between 0 and 20, and re-enter the command.
[Description]
The specified retry count is less than the minimum 0.
[System Action]
Aborts processing.
[User Response]
Specify the retry count between 1 and 20, and re-enter the command.
[Description]
An invalid queue name was specified.
[Parameter]
queuename: Queue name
[System Action]
Aborts processing.
[User Response]
Correct the queue name, and re-enter the command.
[Description]
"value" exceeds the maximum value "max value".
[Parameter]
value: Value
max value: Maximum value of "value"
[System Action]
Aborts processing.
[User Response]
Specify "value" within the maximum value, and re-enter the command.
[Description]
"value" does not follow "opt chars".
[Parameter]
value: Value
opt chars: Character string of the option
[System Action]
Aborts processing.
[User Response]
Add a value following the option, and re-enter the command.
[Description]
Symbol "=" was not found in the character string specified in the parameter.
[System Action]
Aborts processing.
[User Response]
Specify the parameter in format "attribute=value", and re-enter the command.
[Description]
The specified character string (chars) does not begin with a hyphen "-".
[Parameter]
chars: Character string
[System Action]
Aborts processing.
[User Response]
Specify a character string beginning with a hyphen "-", and re-enter the command.
[Description]
An illegal value is specified in the maxexec parameter.
[System Action]
Aborts processing.
[User Response]
Specify a value between 1 and 99 for the job multiplicity specified for the maxexec parameter.
Specify a value between 1 and 999 for the job multiplicity specified for the maxexec parameter.
[Description]
All the specified queues do not exist.
[System Action]
Aborts processing.
[User Response]
Correct the queue name, and re-enter the command.
[Description]
Process trees cannot be displayed for jobs that have not been executed in trace mode.
[Parameter]
job-name: The name of the job specified when the job was submitted
jobno: Reception number allocated to the job by Job Execution Control
hostname: Name of the host where the job was submitted
[System Action]
Aborts processing.
[Corrective Measures]
Re-enter the command, specifying the job that has been executed in trace mode.
[Description]
Process trees cannot be displayed for network jobs.
[Parameter]
job-name: The name of the job specified when the job was submitted
jobno: Reception number allocated to the job by Job Execution Control
hostname: Name of the host where the job was submitted
[System Action]
Aborts processing.
[Corrective Measures]
Re-enter the command, specifying a local job.
[Description]
Process trees cannot be displayed for jobs that are not currently executing.
[Parameter]
job-name: The name of the job specified when the job was submitted
jobno: Reception number allocated to the job by Job Execution Control
hostname: Name of the host where the job was submitted
[System Action]
Aborts processing.
[Corrective Measures]
Re-enter the command, specifying a job that is currently executing.
[Description]
A system error occurred The detailed error code is <error code>.
[Parameter]
error code: Error code
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
This process has timed out because the management file running on distributed job execution was being accessed by another process.
[System Action]
Aborts processing.
[User Response]
After a while, re-execute the process.
[Description]
The specified command line length exceeds 2048 bytes.
[System Action]
Aborts processing.
[User Response]
Specify the command line within 2048 bytes.
[Description]
A confliction occurs between the opt chars options.
[Parameter]
opt chars: Character string of the option
[System Action]
Aborts processing.
[User Response]
Correct the option, and re-enter the command.
[Description]
The specified dispatch priority exceeds level 4.
The specified dispatch priority exceeds level 19.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority between levels 0 and 4, and re-enter the command.
Specify the dispatch priority between levels -20 and 19, and re-enter the command.
[Description]
The specified dispatch priority is less than 0.
The specified dispatch priority is less than -20.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority between levels 0 and 4, and re-enter the command.
Specify the dispatch priority between levels -20 and 19, and re-enter the command.
[Description]
The specified elapsed-time exceeds the limit 99999999.
[System Action]
Aborts processing.
[User Response]
Specify the elapsed-time limit between 1 and 99999999, and re-enter the command.
[Description]
The specified elapsed-time limit is less than 1.
[System Action]
Aborts processing.
[User Response]
Specify the elapsed-time limit between 1 and 99999999, and re-enter the command.
[Description]
Cannot obtain information for environment variables from the environment variable setting file.
[System Action]
Aborts processing.
[User Response]
Correct the contents of the environment variable setting file, and re-enter the command.
[Description]
Failed to copy the script file (batch or JCL file).
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
Check whether a space is sufficient in the disk that contains the job execution control spool. If necessary, secure a sufficient space, and re-enter the command.
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
A system error occurred. "function-name" indicates the error location; "code" indicates the error code.
[Parameter]
function-name: Name of the function that caused the error
code: Error code
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
Find the OS error from this message, and correct it. If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Memory allocation has failed.
[System Action]
Aborts processing.
[User Response]
Wait a while and rerun the job.
[System Administrator Response]
Either extend the physical memory or change the swap settings.
[Description]
The audit log could not be output because a problem occurred when an attempt was made to load the library used to output the audit log.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check whether the following files exist. If they do, one or more of the files may have become corrupted. In such cases, either reinstall Systemwalker Operation Manager or contact a Fujitsu SE.
[Windows version]
Systemwalker installation directory\MPWALKER.JM\bin\mpaudito.dll
[Solaris version/AIX version/Linux version]
/opt/systemwalker/lib/libmpaudito.so
/opt/systemwalker/lib/libmpaudito_nt.so
[HP-UX version]
/opt/systemwalker/lib/libmpaudito.sl
/opt/systemwalker/lib/libmpaudito_nt.sl
[Description]
The audit log could not be output because a problem occurred when an attempt was made to open the audit log output file.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check that there is sufficient free space.
Check that the directory where the audit log is to be output exists.
Check the permissions/rights associated with the directory where the audit log is to be output. If user restriction definitions are not used, the directory must be able to be written to by General Users/Everyone.
The audit log output file may be corrupt. Back up the damaged file and then delete it.
If a problem has occurred on the disk where the audit log is to be output, it may be necessary to replace or restore the hard disk.
The audit log output file and directory can be specified using the mpsetlogsend_omgr command. Refer to the Systemwalker Operation Manager Reference Guide for details on the mpsetlogsend_omgr command.
[Description]
Failed to read the distributed execution control file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If this error recurs, the distributed execution control file may be destroyed.
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The host group is not defined.
[System Action]
Aborts processing.
[User Response]
If the host group definition is required, contact your system administrator.
[Description]
The number of specified host groups exceeded the maximum 64.
[System Action]
Aborts processing.
[User Response]
Specify host groups within 64.
[Description]
The host group <hostgroup> does not exist.
The host group was deleted or omitted in the operational information definition.
[Parameter]
hostgroup: Host group
[System Action]
Aborts processing.
[User Response]
Check whether the specified host group name is correct.
[Description]
The user does not have the privilege to use the -u option.
[System Action]
Aborts processing.
[User Response]
To use the -u option, specify a user included in the Administrators group or superuser account.
[Description]
An invalid value was specified in the opt chars option.
[Parameter]
opt chars: Invalid option
[System Action]
Aborts processing.
[User Response]
Correct the option, and re-enter the command.
[Description]
An invalid argument was specified.
[System Action]
Aborts processing.
[User Response]
Correct the argument, and re-enter the command.
[Description]
The job file with an invalid extension was specified as a job file.
[System Action]
Aborts processing.
[User Response]
Specify the job file with the correct extension, and re-enter the command.
[Description]
An invalid host name was specified.
[System Action]
Aborts processing.
[User Response]
Correct the host name, and re-enter the command.
[Description]
An invalid job number was specified.
[System Action]
Aborts processing.
[User Response]
Correct the job number, and re-enter the command.
[Description]
An invalid option was specified.
[System Action]
Aborts processing.
[User Response]
Correct the option, and re-enter the command.
[Description]
An invalid parameter was specified in "specified-parameter".
[Parameter]
specified-parameter: Invalid parameter
[System Action]
Aborts processing.
[User Response]
Correct the parameter, and re-enter the command.
[Description]
An invalid queue name was specified in "queuename".
[Parameter]
queuename: Invalid queue name
[System Action]
Aborts processing.
[User Response]
Correct the queue name, and re-enter the command.
[Description]
The remote subsystem number is incorrect.
[System Action]
Aborts processing.
[Corrective Measures]
Re-enter the command, specifying a remote subsystem number between 0 and 9.
[Description]
An invalid sub-system number was specified (for multiple subsystems operation)
[System Action]
Aborts processing.
[User Response]
Specify the correct sub-system number and re-enter the command.
[Description]
An invalid value was specified after the opt chars option.
[Parameter]
opt chars: Character string of the option
[System Action]
Aborts processing.
[User Response]
Correct the value following the option, and re-enter the command.
[Description]
The running lapse time of the job exceeded the specified running plan time.
[Parameter]
jobname: Job name
time: Defined running plan time
[System Action]
Continues the job.
[System Administrator Response]
Forcibly terminate the job if necessary.
[Description]
The value of the JC_COMMENT environment variable exceeds the allowable size.
[System Action]
Aborts processing.
[User Response]
Re-enter the command by specifying the JC_COMMENT environment variable within 511 bytes long.
[Description]
The specified job "jobname(jobno.hostname)" does not exist.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[User Response]
Correct the job name and so on, and re-enter the command.
[Description]
The running job "jobname(jobno.hostname)" has been canceled.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[Description]
The attribute of job "jobname(jobno.hostname)" has been changed.
[Parameters]
jobname: Job name
jobno: Job No.
hostname: Host name
[Description]
Job "jobname(jobno.hostname)" has been deleted.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[Description]
Job "jobname(jobno.hostname)" has been held.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[Description]
Job "jobname(jobno.hostname)" is already queued in "queuename".
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
queuename: Queue name
[System Action]
Aborts processing.
[User Response]
Correct the queue name, and re-enter the command.
[Description]
Job "jobname(jobno.hostname)" has been released.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[Description]
Job "jobname(jobno.hostname)" is already held.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[Description]
Job "jobname(jobno.hostname)" is held by the user included in the Administrators group.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[Description]
Job "jobname(jobno.hostname)" is held by superuser.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[Description]
The specified job "jobname(jobno.hostname)" is in the hold state.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[User Response]
Release the job, and re-enter the command.
[Description]
Job "jobname(jobno.hostname)" is not in the hold state.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[Description]
Job "jobname(jobno.hostname)" is running.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[Description]
Job "jobname(jobno.hostname)" is running, and it cannot be held.
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[Description]
Job "jobname(jobno.hostname)" has moved to "queuename".
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
queuename: Queue name
[Description]
Job "jobname(jobno.hostname)" has been queued in "queuename".
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
queuename: Queue name
[Description]
Job "jobname(jobno.hostname)" of user "username" has moved to "queuename".
[Parameter]
jobname: Job name
jobno: Job No.
hostname: Host name
hostname: User name
queuename: Queue name
[Description]
The specified job "jobname" is duplicated.
[Parameter]
jobname: Job name
[System Action]
Aborts processing.
[User Response]
Add a job number, and re-enter the command.
[Description]
The path name of the job file is too long.
[System Action]
Aborts processing.
[User Response]
Specify the path name of the job file within 260 bytes.
[Description]
The job has not been queued.
[System Action]
Aborts processing.
[User Response]
Take an appropriate action according to the previous message, and re-enter the command.
[Description]
The specified job name is too long.
[System Action]
Aborts processing.
[User Response]
Specify the job name within 64 bytes.
[Description]
The default queue is not defined.
[System Action]
Aborts processing.
[User Response]
Correct the queue name, and re-enter the command.
Ask your system administrator to define the default queue.
[System Administrator Response]
Define the default queue.
[Description]
The specified number of executable jobs exceeds 99.
The specified number of executable jobs exceeds 999.
[System Action]
Aborts processing.
[User Response]
Specify the maximum number of executable jobs between 1 and 99, and re-enter the command.
Specify the maximum number of executable jobs between 1 and 999, and re-enter the command.
[Description]
The specified number of executable jobs is less than 1.
[System Action]
Aborts processing.
[User Response]
Specify the maximum number of executable jobs between 1 and 99, and re-enter the command.
Specify the maximum number of executable jobs between 1 and 999, and re-enter the command.
[Description]
The specified number of submitted jobs exceeds 999.
[System Action]
Aborts processing.
[User Response]
Specify the maximum number of submitted jobs between 1 and 999, and re-enter the command.
[Description]
The specified number of submitted jobs is less than 1.
[System Action]
Aborts processing.
[User Response]
Specify the maximum number of submitted jobs between 1 and 999, and re-enter the command.
[Description]
Failed to receive a message during communication with the "Systemwalker MpMjesN" service.
N: Subsystem number (in multi-subsystem configuration)
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Failed to send a message during communication with the "Systemwalker MpMjesN" service.
N: Subsystem number (in multi-subsystem configuration)
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The dispatch priority is not specified.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority, and re-enter the command.
[Description]
The dispatch priority is not specified.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority, and re-enter the command.
[Description]
The user name is not specified.
[System Action]
Aborts processing.
[User Response]
Correct the user name, and re-enter the command.
[Description]
The Job Execution Control daemon is in process of the start command.
[System Action]
Aborts processing.
[User Response]
After the Job Execution Control daemon start process was completed, re-enter the command if necessary.
[Description]
The Job Execution Control daemon is in process of the stop command.
[System Action]
Aborts processing.
[User Response]
After the Job Execution Control daemon stop process was completed, re-enter the command if necessary.
[Description]
The Job Execution Control daemon is not running.
[System Action]
Aborts processing.
[User Response]
Start the Job Execution Control daemon, and re-enter the command.
[Description]
Cannot receive the file with the access name "accessname" because the directory specified to receive the file is not found.
[Parameter]
accessname: Access name of the file to be received
hostname: Name of the server that attempted to receive the file
[Cause]
If this message is output after "Queue" in the Systemwalker Operation Manager window is clicked, there is the following possibility. [UNIX version]
The file system containing /var/opt/FJSVJMCMN in the connection destination server lacks the available space.
[System Action]
Aborts processing.
[User Response]
Take the following corrective measures.
Reserve enough available space in the file system containing /var/opt/FJSVJMCMN in the connection destination server.
Move /var/opt/FJSVJMCMN in the connection destination server to a file system with enough available space and creates a symbolic link to /var/opt/FJSVJMCMN from its movement destination. (Note)
Note) When moving "FJSVJMCMN", take care so that the directory under FJSVJMCMN and the file access privilege are not altered.
[Description]
The operation was denied according to the "Operation Manager user restrictions" setting of the server indicated by hostname.
[Parameter]
username: User name
hostname: Host name of the server that defined the execution of the job
[User Response]
The operations under "Job" or "Queue" in the Job selection window of the Systemwalker Operation Manager client may not be permitted.
[System Administrator Response]
If the account indicated by username in the server indicated by hostname is a user who can be granted the privilege for executing jobs, let the user belong to the swadmin group.
[Description]
Failed to create the MpMjesN subsystem environment.
N: Subsystem number (in multi-subsystem configuration)
[Parameter]
code: OS error code
[System Action]
Aborts processing.
[System Administrator Response]
Check "code", and remedy the error cause. Re-enter the command.
[Description]
Failed to delete the MpMjesN subsystem environment.
N: Subsystem number (in multi-subsystem configuration)
[Parameter]
code: OS error code
[System Action]
Process continues.
[System Administrator Response]
Check "code", and remedy the error cause. Re-enter the command.
[Description]
The value of the MSGM_USERNAME environment variable exceeds the allowable size.
[System Action]
Aborts processing.
[User Response]
Specify the MSGM_USERNAME environment variable within 64 bytes, and re-enter the command.
[Description]
Multiple comments were specified.
[System Action]
Aborts processing.
[User Response]
Specify the comment only once, and re-enter the command.
[Description]
Multiple -cu options were specified.
[System Action]
Aborts processing.
[User Response]
Specify the -cu option only once, and re-enter the command.
[Description]
Multiple -d options were specified.
[System Action]
Aborts processing.
[User Response]
Specify the -d option only once, and re-enter the command.
[Description]
Multiple -dp options were specified.
[System Action]
Aborts processing.
[User Response]
Specify the -dp option only once, and re-enter the command.
[Description]
Multiple job files were specified.
[System Action]
Aborts processing.
[User Response]
Specify the job file only once, and re-enter the command.
[Description]
Multiple -l options were specified.
[System Action]
Aborts processing.
[User Response]
Specify the -l option only once, and re-enter the command.
[Description]
Multiple -p options were specified.
[System Action]
Aborts processing.
[User Response]
Specify the -p option only once, and re-enter the command.
[Description]
Multiple -sys options were specified. (in multi-subsystem configuration).
[System Action]
Aborts processing.
[User Response]
Specify the -sys option only once, and re-enter the command.
[Description]
Multiple -u options were specified.
[System Action]
Aborts processing.
[User Response]
Specify the -u option only once, and re-enter the command.
[Description]
Multiple -x options were specified.
[System Action]
Aborts processing.
[User Response]
Specify the -x option only once, and re-enter the command.
[Description]
Multiple -z options were specified.
[System Action]
Aborts processing.
[User Response]
Specify the -z option only once, and re-enter the command.
[Description]
Neither the -dp option nor the -p option is specified.
[System Action]
Aborts processing.
[User Response]
Specify either or both of the -dp and the -p options, and re-enter the command.
[Description]
The job file name is not suffixed by an extension.
[System Action]
Aborts processing.
[User Response]
Suffix an extension to the job file name, and re-enter the command.
[Description]
No job is specified.
[System Action]
Aborts processing.
[User Response]
Specify a job, and re-enter the command.
[Description]
No operand is specified.
[System Action]
Aborts processing.
[User Response]
Specify an operand, and re-enter the command.
[Description]
No parameter is specified in the command.
[System Action]
Aborts processing.
[User Response]
Specify a parameter, and re-enter the command.
[Description]
The queue name is not specified.
[System Action]
Aborts processing.
[User Response]
Specify a queue name, and re-enter the command.
[Description]
The specified queue name is not found, and the default queue is not specified.
[System Action]
Aborts processing.
[User Response]
Specify a queue name to submit the job, and re-enter the command.
Ask your system administrator to define the default queue.
[System Administrator Response]
Define the default queue.
[Description]
Queue "queuename" is not found.
[Parameter]
queuename: Queue name
[System Action]
Aborts processing.
[User Response]
Correct the queue name, and re-enter the command.
[Description]
The project owner or the executing user is not registered in the user information managed by the OS.
In the case of a network job, the executing user is not registered in the user information managed by the OS of the schedule server.
[System Action]
Aborts processing.
[User Response]
Specify the executing user who is registered in the user information managed by the OS correctly.
Register the project owner or the executing user in the user information managed by the OS.
[Description]
The job could not be submitted because it was not included in the swadmin group.
[System Action]
Aborts processing.
[System Administrator Response]
If the user is one who can be granted the privilege for executing jobs in the operation, let the user belong to the swadmin group before re-submitting the job.
[Description]
The job could not be moved to any queue.
[System Action]
Aborts processing.
[User Response]
Review the queue name, and re-enter the command.
[Description]
The number of submitted jobs exceeds the limit.
[System Action]
Aborts processing.
[User Response]
Reduce the number of queued jobs, and re-enter the command.
[Description]
The specified comment exceeded the maximum length.
[System Action]
Aborts processing.
[User Response]
Specify the comment within 511 bytes, and re-enter the command.
[Description]
The character string specified in the parameter ends with symbol '='.
[System Action]
Aborts processing.
[User Response]
Add a value following symbol '=', and re-enter the command.
[Description]
Failed to open a pipe during communication with the "Systemwalker MpMjesN" service.
N: Subsystem number (in multi-subsystem configuration)
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The specified dispatch priority exceeds level 63.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority between levels 0 and 63, and re-enter the command.
[Description]
The specified dispatch priority is less than 0.
[System Action]
Aborts processing.
[User Response]
Specify the dispatch priority between levels 0 and 63, and re-enter the command.
[Description]
The specified queue "queuename" is not found.
[Parameter]
queuename: Queue name
[System Action]
Aborts processing.
[User Response]
Correct the queue name, and re-enter the command.
[Description]
The attribute of the specified queue "queuename" has been changed.
[Parameter]
queuename: Queue name
[Description]
Queue "queuename" has been started.
[Parameter]
queuename: Queue name
[Description]
Queue "queuename" has been stopped.
[Parameter]
queuename: Queue name
[Description]
The specified queue "queuename" is already started.
[Parameter]
queuename: Queue name
[System Action]
Aborts processing.
[Description]
The specified queue "queuename" is already stopped.
[Parameter]
queuename: Queue name
[System Action]
Aborts processing.
[Description]
The queue information file is not found.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The queue is inactive.
[System Action]
Aborts processing.
[User Response]
Submit the job in another active queue.
Ask your system administrator to activate the queue.
[System Administrator Response]
Activate the queue.
[Description]
The request was rejected by Job Execution Control daemon.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The request was rejected by the "Systemwalker MpMjesN" service.
N: Subsystem number (in multi-subsystem configuration)
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
A request timeout occurred.
[System Action]
Aborts processing.
[User Response]
After a while, re-enter the command.
[Description]
The parameter is not specified with a numerical value.
[System Action]
Aborts processing.
[User Response]
Specify the parameter with a numerical value, and re-enter the command.
[Description]
The job could not be submitted because it was not included in the swadmin group.
[System Action]
Stops starting the Job Execution Control service.
[System Administrator Response]
Rerun the job with the user that is included in the swadmin group.
[Description]
A system error occurred in function-name. The error code is "code".
[Parameter]
function-name: Name of the function that caused the error
code: Error code
The following reasons are assumed.
When the qstat command is executed:
If srvstat() is output as the function-name and 13 is output as the code, the command execution was denied according to the "Operation Manager user restrictions" setting.
When the qjstat command is executed:
If FindFirstFile() is output as the function-name and -1 is output as the code, the symbolic link to the Job Execution Control spool directory does not exist. [UNIX version]
If readjobinfo() is output as the function-name, a file created by the user exists in the queue name directory under the Job Execution Control spool directory. [UNIX version]
[System Action]
Aborts processing.
[User Response]
Notify the system administrator of the error message.
[System Administrator Response]
Take one of the following corrective measures according to the cause of the error.
When the qstat command is executed:
If the user in question can be granted the privilege for executing jobs in the operation, let the user belong to the swadmin group.
When the qjstat command is executed:
Set the symbolic link to the Job Execution Control spool directory for an existing directory. [UNIX version]
With the standby system in a cluster environment, this phenomenon occurs due to the impossibility of referencing the shared disk. This is not malfunction and requires no corrective action.
The symbolic link to the spool directory should be as follows.
/var/spool/mjes
(With subsystem n: /var/spool/mjes/mjesn)
Delete the file created by the user in the queue name directory or move the file from a location under the Job Execution Control spool directory to another location. [UNIX version]
The queue name directory is as follows.
/var/spool/mjes/mjespool/queuename
queuename: Queue name
(With subsystem n: /var/spool/mjesn/mjespool/queuename)
Find the OS error from this message, and correct it. If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The "Systemwalker MpMjesN" service is not running.
N: Subsystem number (in multi-subsystem configuration)
[System Action]
Aborts processing.
[User Response]
Start the "Systemwalker MpMjesN" service, then re-enter the command.
[Description]
The "Systemwalker MpMjesN" service is in process of the start command.
N: Subsystem number (in multi-subsystem configuration)
[System Action]
Aborts processing.
[User Response]
After the "Systemwalker MpMjesN" service start process was completed, re-enter the command if necessary.
[Description]
The "Systemwalker MpMjesN" service is in process of the stop command.
N: Subsystem number (in multi-subsystem configuration)
[System Action]
Aborts processing.
[User Response]
After the "Systemwalker MpMjesN" service stop process was completed, re-enter the command if necessary.
[Description]
The "Systemwalker MpMjesN" service is running, and it is not deleted.
N: Subsystem number (in multi-subsystem configuration)
[Parameter]
code: OS error code
[System Action]
Aborts processing.
[System Administrator Response]
Start the "Systemwalker MpMjesN" service, then re-enter the command.
[Description]
Failed to delete the "Systemwalker MpMjesN" service.
N: Subsystem number (in multi-subsystem configuration)
[Parameter]
code: OS error code
[System Action]
Continues processing.
[System Administrator Response]
Check "code", and remedy the error cause. Re-enter the command.
[Description]
Failed to retrieve the "Systemwalker MpMjesN" service.
N: Subsystem number (in multi-subsystem configuration)
[Parameter]
code: OS error code
[System Action]
Aborts processing.
[System Administrator Response]
Check "code", and remedy the error cause. Re-enter the command.
[Description]
Failed to register the "Systemwalker MpMjesN" service.
N: Subsystem number (for multiple subsystems)
[Parameter]
code: OS error code
[System Action]
Aborts processing.
[System Administrator Response]
Check "code", and remedy the error cause. Re-enter the command.
[Description]
The elapsed time of the job exceeds the limit of the queue "queuename".
[Parameter]
queuename: Queue name
[System Action]
Aborts processing.
[User Response]
Specify the elapse time of the job within the limit value of the queue, and re-enter the command.
Change the queue to submit the job.
[Description]
The environment for the specified subsystem number is not found (in multi-subsystem configuration).
[System Action]
Aborts processing.
[User Response]
Specify an existing subsystem number, and re-enter the command.
[Description]
The execution request was rejected because a job specifying an execution destination subsystem was submitted to a distributed execution queue.
[System Action]
Aborts processing.
[User Response]
Submit the job again, specifying a queue other than a distributed execution queue or a load distribution queue.
[Description]
The execution request was rejected because a job specifying an execution destination subsystem number was submitted to a load distribution queue.
[System Action]
Aborts processing.
[User Response]
Submit the job again, specifying a queue other than a distributed execution queue or a load distribution queue.
[Description]
A JCL job was submitted to the distributed execution queue, and the execution request was refused.
[System Action]
Stops job running.
[User Response]
Specify a queue other than the distributed execution queue, and rerun the job.
[Description]
An empty job file was specified.
[System Action]
Aborts processing.
[User Response]
Specify an appropriate job file.
[Description]
The job is currently running, and the stop request was rejected.
[Parameter]
Aborts command processing.
[System Administrator Response]
After the running job stopped, re-enter the command if necessary.
[Description]
Only a normal job can be submitted to the distributed execution queue.
[System Action]
Aborts processing.
[User Response]
Rerun the job to a normal queue.
[Description]
A JCL job was submitted to the distributed-execution queue, and the execution request was refused.
The execution request was denied because a network job was submitted to the distributed-execution queue.
[System Action]
Stops job running.
[User Response]
Specify a queue other than the distributed-execution queue, and rerun the job.
When submitting jobs to the distributed-execution queue, note the following:
In the Standard information sheet of the Add/Change-Job window, do not enter a host name in the Request host field
Do not specify the -rh option in the qsub command.
[Description]
The job "jobname" cannot be moved to the distributed execution queue.
[Parameter]
jobname: Job name
jobno: Job No.
[System Action]
Stops job move processing.
[User Response]
Specify a queue other than the distributed execution queue, and re-execute the qmove command.
[Description]
Cannot move the job "jobname" that resides in the distributed execution queue.
[Parameter]
jobname: Job name
jobno: Job No.
[System Action]
Stops job move processing.
[User Response]
Specify a queue other than the distributed execution queue, and re-execute the qmove command.
[Description]
Can no longer add hosts because the number of allowable constitute hosts reaches the maximum.
[System Action]
Aborts processing.
[User Response]
For replacement, delete a constitute host to add a new one.
[Description]
The number of resources specified with the -R option is larger than the upper limit specified in the resource definition file.
[System Action]
Stops processing.
[Corrective Measures]
Specify the number of resources that does not exceed the upper limit specified in the resource definition file and then run the command again.
[Description]
There is only one constitute host, and hosts can be no longer deleted.
[System Action]
Aborts processing.
[User Response]
All the constitute hosts cannot be deleted. For replacement, add a new constitute host to delete a one.
To temporarily stop job running, use the gstop command.
[Description]
Could not acquire the resource.
[System Action]
Aborts processing.
[User Response]
After a while, re-enter the command.
[Description]
The specified constitute host does not exist. Specify an existing one.
[System Action]
Aborts processing.
[User Response]
Check that the specified host name is correct, and re-execute the command. Specify a constitute host name for the host name.
[Description]
The specified job execution forecast time is higher than the value of the -lt option.
[System Action]
Aborts processing. The job is not submitted.
[User Response]
The job execution forecast time must be less than the value of the -lt option. Correct the job execution forecast time or the value of the -lt option.
[Description]
The specified host group does not exist. Specify an existing one.
[System Action]
Aborts processing.
[User Response]
Check whether the specified host group is correct, and re-execute the command. For the host group, specify the one defined in the operational information.
[Description]
A host name is duplicated in the specified host group, and it cannot be added.
[System Action]
Aborts processing.
[User Response]
Check whether the specified host name is correct. To add a host, specify a host name not registered in a host group, or delete the duplicated host names.
[Description]
The same host group name was specified. The host group name cannot be duplicated.
[System Action]
Aborts processing.
[User Response]
The host group name cannot be duplicated.
[Description]
An invalid time was specified in the ld option.
[System Action]
Aborts processing.
[User Response]
Specify the time limit in the HHMM format.
[Description]
<username> indicates a user that is included in the swadmin group or that has administrator privileges.
[Parameter]
hostname: User name
[System Action]
Aborts processing.
[User Response]
Rerun the job using the user account of a user that is included in the swadmin group or that has administrator privileges.
[Description]
Too many jobs are specified.
[System Action]
Aborts processing.
[User Response]
Specify the number of jobs within 100, and re-enter the command.
[Description]
Could not check user privileges.
[System Action]
Aborts processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not create a command line file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not create any environment file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not create any job directory.
The following reasons are assumed:
The disk containing the Job Execution Control spool lacks the available space.
The command execution was denied according to the "Operation Manager user restrictions" setting.
The symbolic link to the Job Execution Control spool is not created correctly in the environmental setup of the cluster system. [UNIX version]
The directory under the Job Execution Control spool has turned into files due to a failure in the file system of the OS. [UNIX version]
[System Action]
Aborts processing.
[User Response]
Notify the system administrator of the error message.
[System Administrator Response]
Reserve enough available space.
If the user can be granted the privilege for executing jobs in the operation, let the user belong to the swadmin group.
Create an appropriate symbolic link by referring to the following manual. [UNIX version]
The section "Moving Resources to the Shared Disk" of the Systemwalker Operation Manager Cluster Setup Guide for UNIX
Create the following Job Execution Control directories manually by setting the owner to root, the group to other and the access privilege to 777. [UNIX version]
/var/spool/mjes/mjespool/_neti
(With subsystem n: /var/spool/mjes/mjesn/mjespool/_neti)
/var/spool/mjes/mjespool/_inpt
(With subsystem n: /var/spool/mjes/mjesn/mjespool/_inpt)
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not create any job information file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not copy the script file (batch or JCL file).
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Cannot retrieve the current working directory.
[System Action]
Aborts processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Cannot retrieve the host name.
[System Action]
Aborts processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Cannot retrieve the user name.
[System Action]
Aborts processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The specified job file is not found.
The following reasons are assumed:
The filename used in the job file specification was erroneous.
No job file exists in the specified directory.
The directory storing the job file is not registered in the environment variable "PATH".
The file extension is not specified with the job file name.
An attempt was made to transfer a job file in the schedule server to the execution server and execute the file, but "Transmission of execution command" is not checked in the Standard information sheet of the Add job window.
[System Action]
Aborts processing.
[User Response]
For the specified job file name, take one of the following corrective measures according to the cause of the error.
Submit the job again by specifying the correct file name.
Store the job file in the specified directory and submit the job again.
Perform one of the following actions and submit the job again.
Specify the full path for the job file in the "Command" field.
Specify the full path for the directory storing the job file in the "Directory" field.
Specify the directory storing the job file in the environment variable "PATH" of the system environment variable and reboot the OS. [Windows version]
Modify the file name so that it contains the extension, and submit the job again. [Windows version]
Before transferring the job file in the scheduler server to the execution server for executing the file, check "Transmission of execution command" in the Standard information sheet of the Add Job window.
[Description]
Could not retrieve the default queue name.
[System Action]
Aborts processing.
[User Response]
Specify a queue name, and re-enter the command.
Ask your system administrator to define the default queue.
[System Administrator Response]
Define the default queue.
[Description]
Cannot retrieve the environment variable "MJ_INPUTFILES".
[System Action]
Aborts processing.
[User Response]
Correct the settings of the environment variable "MJ_INPUTFILES", and then submit the command again.
[Description]
Cannot retrieve the environment variable "MJ_OUTPUTFILES".
[System Action]
Aborts processing.
[User Response]
Correct the settings of the environment variable "MJ_OUTPUTFILES", and then submit the command again.
[Description]
Could not retrieve the local host name.
[System Action]
Aborts processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not retrieve job information.
The following reasons are assumed:
A file created by the user exists in the queue name directory under the Job Execution Control spool directory. [UNIX version]
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
Take the following corrective measure.
Delete the user-created file in the queue name directory or move the file from the Job Execution Control spool directory to another location. [UNIX version]
The queue name directory is as follows.
/var/spool/mjes/mjespool/queuename
queuename: queue name
(With subsystem n: /var/spool/mjesn/mjespool/queuename)
[Description]
Could not retrieve the job number.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not retrieve the local host name.
[System Action]
Aborts processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not retrieve queue information. The following reasons are assumed:
Job Execution Control attempted to access the queue information file but the file was being accessed by another application.
"Job/Queue" in the job selection window was selected or the qstat command was executed while Job Execution Control was referencing the queue information internally.
A file created by the user exists in the queue name directory under the Job Execution Control spool directory. [UNIX version]
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
Take one of the following corrective measures according to the cause of the error.
Check that there are applications that may access the files in the Job Execution Control spool directory and, if any such file is found, take an action so that they will not access the files in the Job Execution Control spool directory while Job Execution Control is running.
After completing startup of the Systemwalker MpMjes service or after completion of the startup/stop of the Job Execution Control operation, select "Job/Queue" in the job selection window or execute the qstat command.
Delete the user-created file from the queue name directory or move it from the Job Execution Control spool directory to another location. [UNIX version]
The queue name directory is as follows.
/var/spool/mjes/mjespool/queuename
queuename: queue name
(With subsystem n: /var/spool/mjesn/mjespool/queuename)
[Description]
Could not retrieve system information.
If this message is output after execution of the qstat command, the cause may be as follows.
The symbolic link to the Job Execution Control spool directory does not exist. [UNIX version]
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
Take the following corrective measure.
Set the symbolic link to the Job Execution Control spool directory for an existing directory. [UNIX version]
The symbolic link to the spool directory should be as follows.
/var/spool/mjes
(With subsystem n: /var/spool/mjes/mjesn)
With the standby system in a cluster environment, this phenomenon occurs due to the impossibility of referencing the shared disk. This is not a malfunction and requires no corrective action.
[Description]
Failed to create a JCL file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
System information read failed.
The following reasons are assumed:
Systemwalker Operation Manager has never been started up since installation of Systemwalker Operation Manager.
Systemwalker Operation Manager has never been started up since creation of the subsystem environment.
[System Action]
Aborts processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
Take one of the following corrective measures according to the cause of the error.
Start up Systemwalker Operation Manager.
Start up Systemwalker Operation Manager in the relevant subsystem.
[Description]
Could not open the script file (batch or JCL file).
The following reasons are assumed:
The script file does not have the read privilege setting for it.
[Parameter]
filename: Script file name
[System Action]
Aborts processing.
[User Response]
If no read privilege has been set to the script file, set the read privilege to the logon account of the Systemwalker MpMjes service and submit the job again.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not open the queue information file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not read the registry.
[System Action]
Aborts processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
Check whether--
the following key exists under HKEY_LOCAL_MACHINE and has the command user's read privilege; or
\SOFTWARE\Fujitsu\MpWalker\CurrentVersion\MpMjes\SOFTWARE\Fujitsu\MpWalker\CurrentVersion\MpMjes\Parameters
the following key under HKEY_LOCAL_MACHINE contains the "MjesSpool" and "MjesBin" values.
\SOFTWARE\Fujitsu\MpWalker\CurrentVersion\MpMjes\Parameters
Check that the actual directory referred to by the symbolic link exists. [UNIX version]
/var/spool/mjes (spool directory for Job Execution Control)
[Description]
Could not read the queue information file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not rename the job directory.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not store the current working directory in the environment file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not write the environment variable in the environment file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
Could not write the job information file.
[System Action]
Aborts processing.
[User Response]
If this error recurs, contact your system administrator.
[System Administrator Response]
Check whether a space is sufficient in the disk that contains the job execution control spool. If necessary, secure a sufficient space, and re-enter the command.
If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
An unexpected error occurred
[System Action]
Aborts processing.
[System Administrator Response]
Collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The user "username" does not belong to the Administrators group.
[Parameter]
username: User name
[System Action]
Aborts processing.
[User Response]
Ask your system administrator to operate the command.
[System Administrator Response]
Operate the command instead of the specified user.
[Description]
The user "username" is not a superuser.
[Parameter]
username: User name
[System Action]
Aborts processing.
[User Response]
Ask your system administrator to operate the command.
[System Administrator Response]
Operate the command instead of the specified user.
[Description]
The user "username" is not an owner of the job "jobname(jobno.hostname)".
[Parameter]
username: User name
jobname: Job name
jobno: Job No.
hostname: Host name
[System Action]
Aborts processing.
[User Response]
Ask your system administrator to operate the command.
[System Administrator Response]
Operate the command instead of the specified user.
[Description]
An invalid opt chars option was specified on the line indicated by "line number" in the batch file.
[Parameter]
opt chars: Option
line number: Line number in batch file
[User Response]
Correct the option if necessary, and re-enter the command.
[Description]
A job name beginning with a half-size digit was specified, and it was prefixed by "J".
[Parameter]
jobname: Job name
[User Response]
Correct the option if necessary, and re-enter the command.
[Description]
Too many arguments were specified in the command line or script file line.
[Parameter]
line: Command line or script file line
chars: Ignored argument
[User Response]
Specify the number of arguments within 63 if necessary, and re-enter the command.
[Description]
There are no administrator privileges.
[Parameter]
code: Error code
[System Action]
Aborts processing.
[User Response]
Re-enter the command as the user included in the Administrators group.
See "Command line is too long."
[Description]
Failed to open the ServiceActive database of the service control manager.
[Parameter]
code: OS error code
[System Action]
Aborts processing.
[System Administrator Response]
Check "code", and remedy the error cause. If the error cause is unclear, collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
[Description]
The subsystem number is incorrect. (in multi-subsystem configuration).
[System Action]
Aborts processing.
[User Response]
Specify the correct subsystem number, and re-enter the command.
[Description]
The subsystem number is incorrect. (in multi-subsystem configuration).
[System Action]
Aborts processing.
[User Response]
Specify the correct subsystem number, and re-enter the command.
See "The timelimit specified with -ld is invalid."
[Description]
The job "jobname" cannot be moved to the distributed execution queue.
[System Action]
Stops job move processing.
[User Response]
Specify a queue other than the distributed execution queue, and re-execute the qmove command.
[Description]
Failed to retrieve a domain name.
[Parameter]
code: OS error code
[System Action]
Aborts processing.
[User Response]
Check "code", and remedy the error cause.
See "The JCL job was submitted to distributed execution queue so that the execution request was refused."
See "The job which the request host was specified was submitted to distributed execution queue, so that the execution request was refused."
[Description]
Cannot move the job "jobname" that resides in the distributed execution queue.
[System Action]
Stops job move processing.
[User Response]
Specify a queue other than the distributed execution queue, and re-execute the qmove command.
[Description]
The message code is not found for the error message.
[Parameter]
code: Message code
[System Action]
Stops or continues processing depending on error locations.
[System Administrator Response]
Collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact Fujitsu technical support.
