This section describes the previous log messages for Job Execution Control that start with MJS
[Description]
The startup request processing of the work unit indicated by the WU name was launched for Interstage.
[Parameter]
WU name: Name of the work unit that launched startup processing.
User name: Owner name of the work unit
[Description]
The startup processing of the work unit indicated by the WU name was completed for Interstage.
[Parameter]
WU name: Name of the work unit that completed startup processing.
[Description]
The stop request processing of the work unit indicated by the WU name was received.
[Parameter]
WU name: Name of the work unit that launched stop processing.
[Description]
The stop request processing of the work unit indicated by the WU name was launched for Interstage.
[Parameter]
WU name: Name of the work unit that launched stop processing.
[Description]
The stop processing of the work unit indicated by the WU name was completed for Interstage.
[Parameter]
WU name: Name of the work unit that completed stop processing.
[Description]
An attempt was made to launch the specified work unit, but Interstage was not installed in the system, and the work unit could not be launched.
[System Action]
Stops work unit startup processing.
[User Response]
Check whether the system that launches the work unit is improperly specified in the jobscheduler definition. Correct it if improper. If necessary, contact your system administrator to confirm the Interstage installation conditions.
[Description]
An unrecoverable error occurred in Interstage during work unit startup processing, and the work unit indicated by the WU name was not launched. An Interstage error message will be displayed on the line following this message.
[Parameter]
WU name: Name of the work unit that failed startup processing.
[System Action]
Stops work unit startup processing.
[User Response]
Contact your system administrator.
[System Administrator Response]
Remedy the cause of the Interstage error according to the Interstage error message.
[Description]
An unrecoverable error occurred in Interstage during work unit status monitor processing, and the system could not continue to monitor the status of the work unit indicated by the WU name. An Interstage error message will be displayed on the line following this message.
[Parameter]
WU name: Name of the work unit that failed in status monitor processing.
[System Action]
Stops the work unit status monitor processing, and ends the online job abnormally. No action is taken for the work unit, however.
[User Response]
Contact your system administrator.
[System Administrator Response]
Remedy the cause of the Interstage error according to the Interstage error message. If necessary, use Interstage commands to check the status of the work unit or stop the work unit.
[Description]
An unrecoverable error occurred in Interstage during work unit stop processing, and the work unit indicated by the WU name was not stopped. An Interstage error message will be displayed on the line following this message.
[Parameter]
WU name: Name of the work unit that failed in stop processing.
[System Action]
Stops the work unit stop processing, and ends the online job abnormally. No action is taken for the work unit, however.
[User Response]
Contact your system administrator.
[System Administrator Response]
Remedy the cause of the Interstage error according to the Interstage error message. If necessary, use Interstage commands to check the status of the work unit or stop the work unit.
[Description]
The work unit has been terminated abnormally in Interstage.
[Parameter]
WU name: Name of the work unit that terminated abnormally
[System Action]
Stops the work unit status monitor processing, and ends the online job abnormally.
[User Response]
Interstage message "EXTP4400" is output to SYSLOG. See that message and its description. If this error is unrecoverable, contact your system administrator.
[System Administrator Response]
Interstage message "EXTP4400" is output to SYSLOG. Seeing that message and its description, take the appropriate action.
[Description]
The work unit monitor stop processing, which was requested to Interstage, was started. The work unit stop request is not issued.
[Parameter]
WU name: Name of the work unit that stopped monitor processing.
[Description]
The work unit monitor stop processing, which was requested to Interstage, was completed. The work unit stop request is not issued.
[Parameter]
WU name: Name of the work unit that stopped monitor processing.
[Description]
An attempt to start the job step "jobstep name" has failed.
[Parameter]
jobstep-name: Job step name.
[System Action]
Aborts processing.
[User Response]
Check whether the specified job file name is correct.
[Description]
This message notifies the date and time when network control processing started.
[Parameter]
mm/dd: Date when the job started
hh:mm:ss: Time when the job started
[Description]
This message notifies the date and time when network control processing ended.
[Parameter]
mm/dd: Date when the job ended
hh:mm:ss: Time when the job ended
[Description]
The line with the server has been connected.
[Parameter]
hostname: Name of the server that connected the line
[Description]
The line with the server has been disconnected.
[Parameter]
hostname: Name of the server that disconnected the line.
[Description]
File transfer was performed.
[Parameter]
Access name of the transferred file
The server sent the file to the client.
The server received the file from the client.
Outputs the size of the transferred file. When the transfer size is above 1 kilobyte, it is rounded up in kilobytes.
When the transfer size is above 1 kilobyte, "KB" appears; otherwise, "BYTES" appears.
[Description]
This message notifies the date and time when the job started in the server.
[Parameters]
hostname: Name of the server that connected the line
mm/dd: Date when the job started in the server
hh:mm:ss: Time when the job started in the server
[Description]
This message notifies the date and time when the job ended in the server, as well as the end code.
[Parameters]
hostname: Name of the server that disconnected the line.
mm/dd: Date when the job ended in the server
hh:mm:ss: Time when the job ended in the server
nnnn: End code of the job in the server
[Description]
An attempt was made to receive the file, but the file was not found on the server. If the server that receives the network job is a Windows server, there is a possibility that if the desktop heap was depleted, it may not have been possible to create the file.
[Parameters]
accessname: Access name of the file to be received
hostname: Name of the server from which the file was to be received
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[Description]
An attempt was made to receive the file, but the file was not found on the server.
[Parameters]
hostname: Name of the server from which the file was to be received.
filename: Name of the file to be received
[System Action]
Stops file receive processing. The job ends with end code "0x40000008".
[Description]
Cannot receive the file with the access name "accessname" because the file specified in the File operand is a directory.
[Parameters]
accessname: Access name of the file to be received
hostname: Name of the server that attempted to receive the file
[System Action]
Stops file receive processing. The job ends with end code "0x40000008".
[Description]
Cannot receive the file with the access name "accessname" because the directory specified to receive the file is not found.
[Parameters]
accessname: Access name of the file to be received
hostname: Name of the server that attempted to receive the file
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[Cause]
There are the following causes:
An invalid path is specified in the file operand of the JCL receive command.
When the "Restrict so that only users included in the swadmin group can start demand jobs, start jobnet Job execution control attributes or use Jobscheduler command functions." check box in the Define Operation Manager Shared Parameter dialog box is checked, and a general user not registered in the swadmin group accessed Job or Queue on the job selection window in the Systemwalker Operation Manager window.
[User Response]
Correct the invalid path specified in the file operand of the JCL receive command, and rerun the job.
Ask your system administrator to register the user in the swadmin group, or specify a user included in the swadmin group.
[Description]
An attempt was made to send the file, but the file was not found on the server to which the job was submitted.
[Parameter]
access: Access name of the file to be sent.
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the file name specified in the JCL file control statement or the file name set in the environment variable "MJ_INPUTFILES", and rerun the job.
[Description]
An attempt was made to send a file, but it failed because no access privileges were permitted.
[Parameter]
accessname: Access name of the file to be sent
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the file name specified in the JCL file control statement or the file name set in the environment variable "MJ_INPUTFILES", and rerun the job.
[Description]
The number of retry operations to correct a line error exceeded the specified value.
[Parameter]
command: Network job control command that performed retry operations for the line error.
[System Action]
Aborts processing. The job ends with end code "0x40000016".
[User Response]
Contact your system administrator. After the action was completed, return the job.
[System Administrator Response]
Check the state of the server and line, and remedy the error cause.
[Description]
The network job was denied. The following reasons are assumed:
The "username" account is not registered in the server "hostname". The account name is case-sensitive.
In the server indicated by hostname, the job execution was denied due to the definition information setting in the Define Trust Host window.
The job execution was denied due to the setting of the "Operation Manager user restrictions" in the server indicated by hostname.
[Parameters]
username: Owner name of the job
hostname: Host name of the server that rejected the execution of the job
[System Action]
Aborts processing. The job ends with end code "0x40000913".
[User Response]
The "username" account is not registered in the host of the server "hostname". Consult your system administrator.
In the server indicated by hostname, the job execution may be inhibited due to the definition information setting in the Define Trust Host window. Consult your system administrator.
In the server indicated by hostname, the job execution may be inhibited due to the setting of "Operation Manager user restrictions". Consult your system administrator.
[System Administrator Response]
Register the "username" account in the server "hostname".
In the server indicated by hostname, set the definition information in the Define Trust Host window appropriately so that the network job from the job submitting host can be executed.
In the server indicated by hostname, if the username account is a user who can be granted the job execution privilege in the operation, let the user belong to the swadmin group.
[Description]
The option specified in mjsrjob.exe is defined in an invalid format.
[System Action]
Aborts processing. The job ends with end code "0x40000012".
[User Response]
Correct the option, and rerun the job.
[Description]
The execution command is specified in an invalid format.
[Parameter]
command: Name of the command that was specified in an invalid format.
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the execution command, and rerun the job.
[Description]
The host name is not specified in the CONNECT command.
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Specify the host name, and rerun the job.
[Description]
The client cannot recognize the host name specified in the CONNECT command.
[Parameter]
hostname: Name of the host that attempted to connect the line.
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the host name, and rerun the job.
[Description]
The file name is not assigned to the access name specified at file transfer.
[Parameter]
accessname: Access name of the file to be transferred.
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the JCL or execution command, and rerun the job.
[Description]
The line with the server is not connected.
[Parameter]
command: Execution command other than DISCONNECT
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Add the CONNECT command, and rerun the job.
[Description]
Batch job request processing failed in the execution server.
[System Action]
Aborts processing. The job ends with end code "0x40000016".
[User Response]
This message is output in the following cases.
The job owner does not have the access privilege for the actual directory indicated by symbolic link /var/spool/mjes of the execution server (when the execution server is a UNIX server).
The execution server status is any of the following.
The system load is high.
he swap area is insufficient.
The hard disk space is insufficient.
The primary domain controller (PDC) or backup domain controller (BDC) in the domain to which the execution server belongs was stopped or restarted (when the execution server is a Windows server).
The IP address for the name of the local host is set to "127.0.0.1" in the hosts file of the schedule server.
Ask your system administrator to check the system state. After the system state was improved, rerun the job.
[System Administrator Response]
Assign the access privilege of the job owner (read, write and execute privileges) to the actual directory (which should be confirmed by tracing back to the highest level in the directory) indicated by the symbolic link (/var/spool/mjes) of the execution server.
Check whether the server is under the conditions described in [User Response], and take the appropriate action. If this error recurs while the system state was improved, collect the information about Job Execution Control by using the Maintenance Information Collection Tool and contact Fujitsu technical support.
Do not stop or restart the PDC or BDC of the domain to which the execution server belongs while the network job is operating.
The PDC and BDC should be stopped or restarted in the time frame in which the network job is not operating.
Ensure that the IP address configured as the name of the local host in the hosts file of the schedule server is one that other servers can also connect to.
[Description]
The specified queue is not available. The queue that has the same queue name as that of the submitted job is not found in the execution server, and the default queue is not defined.
[Parameter]
queue: Queue name of the submitted job
[System Action]
Aborts processing. The job ends with end code "0x40000016".
[User Response]
Correct the queue name, and rerun the job.
[Description]
MJSIN is not specified in JCL.
[System Action]
Aborts processing. The job ends with end code "0x40000012".
[User Response]
Specify MJSIN, and rerun the job.
[Description]
Cannot secure the required space because the region area is insufficient.
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Contact your center administrator.
[Description]
The file specified in MJSIN does not contain executable command.
[System Action]
Stops processing. The job ends with end code '0x40000008'.
[User Response]
Specify the file containing executable command in MJSIN, then rerun the job.
[Description]
Invalid executable command name.
[System Action]
Stops processing. The job ends with end code '0x40000008'.
[User Response]
Correct the executable command, then rerun the job.
[Description]
An input-output error occurred during access to the file specified in accessname.
[Parameter]
code: OS error code
[System Action]
Abort processing. The job ends with end code '0x40000008'.
[User Response]
Check whether the correct file is specified. If necessary, correct the error and rerun the job. If the correct file is specified, an error may occur in an external storage device. Contact your system administrator.
[System Administrator Response]
Check "code" or message MJS884S, following this message. Then 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]
Only the CONNECT command can be specified on the first line of the execution command.
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the executable command, then rerun the job.
[Description]
The default queue was used because no queue name was specified in the EXECUTE command; however, the default queue name was not defined in the execution server.
[Parameter]
queuename: Queue name of the submitted job
[System Action]
Aborts processing. The job ends with end code '0x40000016'.
[User Response]
Specify the queue name, and rerun the job.
[Description]
The specified queue is not available because the number of submittable jobs exceeds the limit in the execution server.
[Parameter]
queuename: Queue name of the submitted job
[System Action]
Ends the job. The job ends with end code '0x40000016'.
[User Response]
Execute one of the following:
Specify another queue, and rerun the job.
After a while, rerun the job.
[Description]
An attempt was made to send a file, but the specified file name is a directory.
[Parameter]
access: Access name of the file to be sent
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the file name specified in the JCL file control statement or the file name set in the environment variable "MJ_INPUTFILES", and rerun the job.
[Description]
An attempt was made to receive the file, but the directory was not found on the server.
[Parameter]
access: Access name of the file to be received
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the file name specified in the JCL file control statement or the file name set in the environment variable "MJ_OUTPUTFILES", and rerun the job.
[Description]
An attempt was made to receive a file, but it failed because no access privileges were permitted.
[Parameter]
access: Access name of the file to be received
[System Action]
Aborts processing. The job ends with end code "0x40000008".
[User Response]
Correct the file name specified in the JCL file control statement or the file name set in the environment variable "MJ_OUTPUTFILES", and rerun the job.
[Description]
The specified job file could not be found on the execution server. This may have occurred for the following reasons:
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 environmental variable "PATH".
The file extension is not specified with the job file name.
An attempt was made to execute a job file in the execution server, but "Transmission of execution command" in the Standard information sheet of the Add-Job window was checked.
The Job Execution Control service on the execution server cannot determine whether the job file exists.
[Parameter]
jobfile: Job file name that was not found in the execution server
[System Action]
Aborts processing. The job ends with end code "0x40000016".
[User Response]
Take one of the following corrective measures on the specified job file 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 system environment variable "PATH" and reboot the OS. [Windows version]
Modify the file name so that it contains the extension, and submit the job again. [Windows version]
To execute a job file in the execution server, do not check "Transmission of execution command" in the Standard information sheet of the Add-Job window.
Assign permissions (read access) for the job file to the logon account of the Job Execution Control service running on the execution server and submit the job again.
[System Administrator Response]
Take the appropriate action described in [User Response]. If this error recurs while the correct job file is specified, collect the information about Job Execution Control by using the Maintenance Information Collection Tool and contact Fujitsu technical support.
[Description]
The file "filename" was not code-converted because--
the file contains an invalid code; or
a system error occurred and code conversion failed.
[Parameter]
filename: Name of the file that failed in code conversion. One of the following files is output:
JOBFILE/ STDOUT/ STDERR
[System Action]
Re-transfer the file from the beginning as a binary file, and continue processing.
[Description]
Could not confirm the execution continuation mode, and failed to connect to the remote server.
[System Action]
Stops running the job. The job ends with end code "0x40000008".
[User Response]
Contact the system administrator. After the system administrator takes corrective action, rerun the job.
[System Administrator Response]
This error occurs during an attempt to open or read a management file under a job execution control spool. Determine and remove the cause of the disk I/O error. If the cause of the error is unknown, collect the information about Job Execution Control by using the Maintenance Information Collection Tool and contact Fujitsu technical support.
[Description]
Failed to rerun the network job after the system failed.
[System Action]
Aborts processing. The job ends abnormally with end code "0x40000132".
[User Response]
Rerun the job.
[Description]
Failed in connection because the execution server had a lower version.
[System Action]
Stops running the job. The job ends with end code "0x40000008".
[User Response]
In a multi-subsystem configuration, subsystems 1 to 9 can submit a network job only to Systemwalker Operation Manager UNIX V5.2 or later or Windows V10.0L10 or later. When running a network job with a lower version, specify subsystem 0.
[Description]
The execution request was denied because a job specifying the request host was submitted to the distributed-execution queue on the schedule server.
The execution request was denied because any of the following jobs was submitted to the distributed-execution queue on the execution server:
A network job that is submitted by the requesting host
A job that is submitted by the requesting host using the distributed-execution function
A job that is submitted by the requesting host with the host name of another server specified using JCL and so on
[Parameters]
jobname: Job name
jobno: Job No.
[System Action]
Stops running the job. The job ends with end code "0x40000016".
[User Response]
Do not specify the request destination host if the request host is specified by the schedule server.
Specify a queue other than the distributed-execution queue on the execution server and resubmit the job. Alternatively, disable the distributed-execution function for the distributed-execution queue on the execution server and resubmit the job.
[Description]
A function that was not supported in a lower-version server was used to execute the network job, and the execution request was forcibly stopped for the lower-version server.
[Parameters]
jobname: Job name
jobno: Job No.
[System Action]
Stops running the job. The job ends with end code "0x40000020".
[User Response]
Review the command and parameter to run the job, change them to the appropriate values, and rerun the job.
Register the user required to start the job in the schedule server.
If a job is submitted to an execution server with subsystems that runs V13.2.0 or earlier, it is not possible to send an execution request from an arbitrary subsystem on the schedule server to an arbitrary subsystem on the execution server. When performing network job operations where any server is running V13.2.0 or earlier, do not specify the "-rsys" option.
[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. The job ends with end code "0x40000024".
[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 mjsnetN port number for the specified subsystem number has not been specified.
N: Subsystem number
[System Action]
Stops processing. The job ends abnormally with end code "0x40000132".
[Corrective Measures]
Submit the command again, specifying the mjsnetN port number for the subsystem number.
[Description]
Failed to open the transfer file.
[Parameter]
code: OS error code
[System Action]
Stops file transfer processing. The job ends with end code "0x40000008".
[User Response]
Check the transfer file and execution command, and rerun the job. If the execution command is correct, contact your system administrator.
[System Administrator Response]
Check "code" or message MJS884S, following this message. Then 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]
An input-output error occurred during an attempt to transfer the file specified in "accessname".
[Parameters]
accessname: Access name of the currently transferred file
code: OS error code
[System Action]
Stops file transfer processing. The job ends with end code "0x40000008".
[User Response]
Correct an error if any. If you cannot identify the error, contact your system administrator.
[System Administrator Response]
Check "code" or message MJS884S, following this message. Then 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]
Space shortage occurred during an attempt to receive the file specified in "accessname".
[Parameters]
accessname: Access name of the file to be transferred
hostname: Name of the host that caused space shortage
[System Action]
Stops file transfer processing. The job ends with end code "0x40000008".
[User Response]
Reserve sufficient disk space, and rerun the job.
[Description]
Cannot send the file with the access name "accessname" because the directory specified to transfer the file is not found.
[Parameters]
accessname: Access name of the file to be transferred
hostname: Access name of the server that attempted to transfer the file
[System Action]
Stops file transfer processing. The job ends with end code "0x40000008".
[User Response]
Correct the FILE operand of the SEND command, and rerun the job.
[Description]
Cannot send the file with the access name "accessname" because the file specified in the FILE operand is a directory.
[Parameters]
accessname: Access name of the file to be transferred
hostname: Host name of the server that attempted to transfer the file
[System Action]
Stops file transfer processing. The job ends with end code "0x40000008".
[User Response]
Correct the FILE operand of the SEND command, and rerun the job.
[Description]
The error indicated by "code" occurred during file transfer processing.
[Parameters]
code: OS error code that was output during file transfer.
When code is FFFFFF6B, the possible causes are as follows.
The Job Execution Control spool directory in the execution server is exhausted.
An application that performs virus checking or mirroring in the execution server referenced the job information file.
The privileges of /var/opt/FJSVJMCMN and the directories and files under it in the connection destination server as well as the directories at the higher levels do not include the execution privilege of the user who is logging into Systemwalker Operation Manager. [UNIX version]
[System Action]
Stops file transfer processing. The job ends with end code "0x40000008".
[User Response]
Contact your system administrator.
[System Administrator Response]
Check "code". Then remedy the error cause.
When code is FFFFFF6B, take one of the following corrective measures according to the cause of the error.
Reserve enough available space in the Job Execution Control spool directory.
Set the applications that perform virus checking or mirroring so that they do not access the Job Execution Control spool directory and the directories under it.
Add the user's execution privilege to /var/opt/FJSVJMCMN and the directories and files under it in the connection destination server as well as the directories at the higher levels. [UNIX version]
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 line error has occurred.
There are the following causes:
The server is faulty or failed during processing.
The service on the server is not running.
The TCP/IP service is faulty or failed during processing.
TCP/IP has not been installed.
TCP/IP definition is invalid.
[Parameters]
Job name
Job No.
Server name
Processing that caused this error
The following shows the correspondence between error codes and processes.
2: CONNECT
3: READ
4: WRITE
5: DISCONNECT
Detail error code
The table below lists the detail error codes as well as the description of each detail error code.
Detail error code of the host that submitted the job | Description | Action | |||||||
|---|---|---|---|---|---|---|---|---|---|
Windows | Solaris/DS | HP-UX | AIX | Linux | |||||
2726 | -- | TCP/IP is not installed in the server that is subjected to job submission. | Install the TCP/IP protocol in the server that is subjected to job submission. | ||||||
2736 | 005f | 00d8 | 0039 | -- | Job submission failed on the execution server because a Japanese character was used in the job name in the following environment:
| Do not use Japanese characters in job names if either the submitting server or the execution server is a UTF-8 environment because operation is not guaranteed. | |||
2742 | -- | A failure was detected in the network subsystem. | -- | ||||||
2745 | 0082 | 00e7 | 0048 | 0067 | The virtual circuit was abandoned due to timeout or other failure. | Check the following causes, and take the appropriate action.
| |||
2746 | 0083 | 00e8 | 0049 | 0068 | The virtual circuit was reset on the remote side. | ||||
2747 | -- | Failed in socket processing because the system buffer space was insufficient or the queue was full. | Check the state of TCP/IP communication on the job submission server. | ||||||
2751 | 0094 | 00f2 | 0051 | 0071 | There is no route for accessing the host. | Check that the route from the job submission server to the execution server exists in the network communication (TCP/IP communication) path. | |||
274C | 0091 | 00ee | 004e | 006e | The tried connection failed, and timeout occurred. The execution server itself is stopped or the job execution control service or daemon on the execution server is stopped. | Check the state of the network communication (TCP/IP communication) between the job submission and execution servers. Start the job execution control service or daemon on the execution server. | |||
274D | 0092 | 00ef | 004f | 006f | The connection request was refused forcibly. Otherwise, the port number of the job submission server does not match that of the execution server. | Check the state of the network communication (TCP/IP communication) between the job submission and execution servers. The port number (Note) for job execution control of the job submission server must match that of the execution server in the services file. The service name is "mjsnet" or "mjsnetN". "N" indicates a subsystem number (1 to 9). To reflect the changed port number for the execution server, restart the job execution control service or daemon of the execution server. | |||
277A | -- | The desktop heap space is insufficient in the job submission server. | Reduce the number of jobs executed simultaneously. | ||||||
2AF9 | 0001,7531(*) | The host "hostname" is not found. | Check whether the specified server name is correct. | ||||||
2AFA | 0002, 7532(*) | A temporary error occurred in host name resolution processing. The local host requested host name resolution to the DNS server, but could receive no response. | Check whether the DNS server itself is unable to perform processing due to high load. | ||||||
--- | 0004,0020, 00B7(*) | The line was disconnected between the job submission and execution servers. The system on the line or execution server is in high load state. | Contact your center administrator to check the system state. | ||||||
0000 | Timeout occurred because no response was returned from the execution server. | Check the state of the network communication (TCP/IP communication) between the job submission and execution servers. | |||||||
For more information on how to define the port number, see the Systemwalker Operation Manager Installation Guide.
[System Action]
Stops running the job. The job ends with end code "0x40000132".
[User Response]
Check whether the specified server name is correct.
Use the ping command to check that the specified server is available.
Contact your system administrator. After the system administrator's action was completed, rerun the job.
[System Administrator Response]
Check the error cause with code2, and remedy the error cause.
code2 is the result of conversion of the following value into a hexadecimal value. Values marked with an asterisk (*) in the table above are set by job execution control.
[Windows version]: | Value obtained by WSAGetLastError() |
[UNIX version]: | errno |
Therefore, the above values are useful for investigations even if the output value is not listed in the table for code2 under [Parameter].
[Description]
The service or daemon required to operate the network function has not started in the host specified as a server.
[Parameter]
hostname: Server name
[System Action]
The job ends abnormally with end code "0x40000016".
[User Response]
Start the "Systemwalker MpMjesN" service, then rerun the job.
N: Subsystem number (in multi-subsystem configuration)
[Description]
An unrecoverable error occurred in the network function that was active on the server.
[Parameters]
jobname: Job name
jobno: Job No.
hostname: Server name
code: Indicates the contents of the error.
[System Action]
The job ends abnormally with end code "0x40000132".
[User Response]
Contact your system administrator. After the system administrator's action was completed, rerun the job.
[System Administrator Response]
Check "code" or message MJS884S, following this message. Then 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]
This error message indicates an OS error.
[Parameter]
msgtext: OS error message text
[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]
The job execution was suspended because the execution server failed.
[System Action]
Aborts processing. The job ends with end code "0x40000132".
[User Response]
Restart the execution server and rerun the job.
