Error message
MJS830E BATCH JOB REQUEST PROCESS IS FAILED |
Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Check all applicable actions below to resolve the issue.
Action 1
Points to check
Does the job owner have the required permissions (read, write, execute) for the directory indicated by <execution server symbolic link>/var/spool/mjes (when the execution server is UNIX)?
Cause
If the job owner does not the required permissions for the directory indicated by <execution server symbolic link>/var/spool/mjes, network jobs cannot be received from other servers.
Action method
Grant the job owner the required permissions (read, write, execute) for the directory (the top level directory must be checked first) indicated by <execution server symbolic link>/var/spool/mjes.
Action 2
Points to check
Does the execution server have one of the following statuses?
Heavy system load
Insufficient swap area
Insufficient hard disk space
Cause
If the execution server has the status shown in "Points to check" above, network jobs cannot be received from other servers.
Action method
If the execution server has the status shown in "Points to check" above, improve the status of the execution server.
Action 3
Points to check
Has the primary domain controller (PDC) or backup domain controller (BDC) of the domain to which the execution server belongs been stopped or restarted (when the execution server is Windows)?
Cause
If the PDC or BDC is stopped or restarted while the job request is being processed on the execution server, a user authentication processing error occurs in the PDC or BDC and the job request processing fails.
Action method
Do not stop or restart the PDC or BDC of the domain to which the execution server belongs while the network job is running.
Stop or restart the PDC or BDC during a period when the network job is not running.
Action 4
Check the content described in "Action" of "5.2.2 When Antivirus Software is used, the Job Ends Abnormally [Windows versions]", and then take action.
Action 5
Points to check
Is the host name or IP address specified in the request host correct?
Cause
The host resolved from the host name or IP address specified in the execution server is different to the assumed host, therefore the job file specified in the host is not found.
Action method
Check if the following settings are valid:
Request host in the Standard information tab of the Add/Change - Job window
Default host name in the Standard information tab of the Job Net Properties window
Host name specified in the -rh option of the qsub command
hosts file
Action 6
Points to check
Has the IP address of the schedule server been set to 127.0.0.1 in the hosts file of the schedule server?
Cause
When the status of the schedule server is as indicated in "Points to check", communications from the execution server to the schedule server are unable to be performed correctly, which may result in a job that is operating on the execution server to be considered not needed and then being deleted.
Action method
Refer to "4.16.9 "Systemwalker Operation Manager" Remains Displayed in the Main Window" for information on setting the correct IP address for the schedule server in the hosts file of the schedule server.
