Top
Systemwalker Operation Manager  Message Guide
FUJITSU Software

2.11 Messages Starting with MpMjes

This section explains messages starting with MpMjes.

Those messages are output by Job Execution Control.

[Windows]MpMjes: ERROR: 200: Failure in starting session manager service.

[Description]

The system failed to start the session management service.

[System Action]

Interrupts start processing of the session management service among the programs that are started by the Systemwalker MpJmSrv service.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: INFO: 1000: Systemwalker MpMjes service started normally.

[Description]

The Systemwalker MpMjesN service was started successfully.

N: Indicates subsystem number (at multiple subsystems operation).

[Windows]MpMjes: INFO: 1001: Systemwalker MpMjes service was normally terminated.

[Description]

The Systemwalker MpMjesN service was terminated successfully.

N: Indicates subsystem number (at multiple subsystems operation).

[Windows]MpMjes: ERROR: 1005: Failure in starting the program for job' s history information/operation result functions.

[Description]

Failed to start the program for job history information/operation result functions.

[System Action]

Continues the Systemwalker MpMjesN service startup processing.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

There are the following possible causes.

  1. System resources are insufficient.

  2. mjscnsl.exe does not exist at the installation directory \MPWALKER.JM\bin.

[System Administrator Response]

Remove the error and restart the Systemwalker MpMjesN service.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: WARNING: 1006: Failure in opening job's operation result information file.

[Description]

Failed to open job operation result information file.

[System Action]

Continues the Systemwalker MpMjes service process.

N: Indicates subsystem number (at multiple subsystems operation).

Suspends writing job operation result information.

[Cause]

There are the following possible causes.

  1. There is no empty space in the file system.

  2. Another application such as EXCEL is accessing the job operation result information file.

[User Response]

If there is no empty space in the file system, reserve some empty space.

Terminate the application that is accessing the job operation result information file.

[System Administrator Response]

If there is no empty space in the file system, reserve some empty space.

Terminate the application that is accessing the job's operation result information file.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1007: System error occurred while processing the history information function/operation result function program.

[Description]

A system error occurred while processing the history information function/operation result function program.

[System Action]

Continues the Systemwalker MpMjesN service process.

N: Indicates subsystem number (at multiple subsystems operation).

History information function/operation result function will be disabled.

[Cause]

The following cause is assumed:

  1. System resources are insufficient.

[System Administration Response]

Remove the cause of the error and restart the Systemwalker MpMjesN service.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1008: Faluire in writing job's operation result information file.

[Description]

Failed to write job operation result information file.

[System Action]

Continues the Systemwalker MpMjesN service process.

N: Indicates subsystem number (at multiple subsystems operation).

Suspends writing job operation result information.

[Cause]

The following cause is assumed:

  1. There is no empty space in the file system.

[User Response]

If there is no empty space in the file system, reserve some empty space.

[System Administrator Response]

If there is no empty space in the file system, reserve some empty space.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: WARNING: 1009: The TCP port for the Network Job Monitor does not exist.

[Description]

No TCP port number is found for network job monitoring.

[System Action]

Continues the Systemwalker MpMjesN service start processing without operating the network job.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The following cause is assumed:

  • No TCP port number is defined for the subsystem.

[System Administrator Response]

Add TCP port number for network job monitoring corresponding to each sub-system, then restart the Systemwalker MpMjesN service.

However, in case of the following, this message does not affect business process, so you can ignore it:

  • Operations that do not submit network jobs

  • Settings are made so that network jobs are submitted from all the subsystems on the submit-side server to "subsytem0" on the execution server.

See "Assigning Subsystem Port Numbers [EE]" in the Systemwalker Operation Manager Installation Guide for how to set port numbers.

[Windows]MpMjes: ERROR: 1011: The continuous execution modes of each server are not unified.

[Description]

The continuous execution modes on each server are not identical.

[System Administrator Response]

Unify the continuous execution modes of each server. Refer to "Continuing Job Operations at Schedule Server System Down" in the Systemwalker Operation Manager Technical Guide for details. See "jmmode continuous execution mode switching command" in the Systemwalker Operation Manager Reference Guide for how to switch continuous execution mode.

[Windows]MpMjes: ERROR: 1012: Failure in writing to the job exit code file.

[Description]

Writing to the job exit code storage file failed.

[System Action]

Continues with the "Systemwalker MpMjesN" service processing.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

There is the following possible cause:

  • A file in the spool directory is currently being referenced by another application.

[User Response]

Quit all applications that are referencing the file in the spool directory.

By default, the spool directory is located in the following:

<Installation directory>mpwalker.jm\mpmjessv\mjespool

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1030: The filesystem of the Spool directory is not NTFS.

[Description]

The file system for the spool directory cannot be secured because it is not NTFS.

[System Action]

Cancels service startup of job execution control.

[System Administrator Response]

Change the spool directory to an NTFS disk and restart Job Execution Control. See "Defining the System Operating Information" in the Systemwalker Operation Manager Installation Guide for how to change the configuration.

[Windows]MpMjes: ERROR: 1031: The filesystem of the job execution history information directory is not NTFS.

[Description]

Security reinforcement failed since NTFS was not specified for the file system of the job execution history information directory.

[System Action]

Aborts startup of the Job Execution Control service.

[System Administrator Response]

Move the job execution history information directory onto the NTFS disk, then restart the Job Execution Control service. See "Defining the System Operating Information" in the Systemwalker Operation Manager Installation Guide for how to change the configuration.

[Windows]MpMjes: ERROR: 1032: The filesystem of the operation results data directory is not NTFS.

[Description]

Security reinforcement failed since NTFS was not specified for the file system of the running result information directory.

[System Action]

Aborts startup of the Job Execution Control service.

[System Administrator Response]

Move the job running result information directory onto the NTFS disk, then restart the Job Execution Control service. See "Defining the System Operating Information" in the Systemwalker Operation Manager Installation Guide for how to change the configuration.

[Windows]MpMjes: ERROR: 1033: Systemwalker MpMjesN failed in the security reinforcement.

[Description]

Startup with security reinforcement failed.

[System Action]

Aborts startup of the Job Execution Control service.

[Cause]

The security reinforcement failed because:

  1. the swadmin group was not found; or

  2. access privilege setting failed.

[System Administrator Response]

  1. Create the swadmin group.

  2. Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: WARNING: 1034: Systemwalker MpMjesN failed in the security release.

[Description]

Security release failed.

[System Action]

Starts up the Systemwalker MpMjes service with the security reinforcement performed.

[System Administrator Response]

The security release failed because:

  • Failed to cancel access privileges.

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1035: Systemwalker MpMjesN failed in the security reinforcement by load balancing definition.

[Description]

The initialization file contained the load balancing definition, so the service could not be started with the security reinforcement.

[System Action]

Aborts startup of the Job Execution Control service.

[System Administrator Response]

Delete the load balancing definition from the initialization file, then restart the Job Execution Control service. See "Initialization File (Job Execution Control)" in the Systemwalker Operation Manager Installation Guide for how to edit the initialization file.

[Windows]MpMjes: WARNING: 1632: Failed to load the audit log library.

[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.

Systemwalker installation directory\MPWALKER.JM\bin\mpaudito.dll

[Windows]MpMjes: WARNING: 1633: Failed to read the audit log file.

[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.

[Windows]MpMjes: WARNING: 1634: Execution server <hostname> was excluded from host group <hostgroup>.

[Description]

With distributed execution jobs, the job requested to the execution server cannot be processed. As the result, the execution server has been excluded from the distribution target.

[Parameter]

hostname: Name of the execution server that failed to process the requested job and was excluded from the distribution target.

hostgroup: Name of the host group that the excluded execution server belonged to.

[System Action]

The relevant execution server is excluded from the distribution target.

[System Administrator Response]

Eliminate the cause after checking the execution server status that failed to process the requested job. This may have occurred for the following reasons:

  • The power to the execution server is not turned on.

  • The job execution service is not running.

  • The network is disconnected.

[Windows]MpMjes: ERROR: 1635: mjesexit.bat/mjesexit.exe was not able to be called.code=xxxx

[Description]

Failed to call the demand job termination exit.

[Cause]

This may have occurred for the following reasons:

  • The demand job termination exit file does not exist.

  • The job termination exit file is not executable.

  • Failed to generate the process due to low memory.

[Parameter]

xxxx: System error code that is notified from the operating system.

[System Action]

Terminates calling process of the demand job termination exit.

[System Administrator Response]

Eliminate the cause according to the error code of the operating system, then restart the Job Execution Control daemon if necessary.

If this problem is not resolved, collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows]MpMjes: WARNING: 1636: Abnormalities were detected to mjesexit.bat/mjesexit.exe file.

[Description]

Failed to check the demand job termination exit file.

[Cause]

This may have occurred for the following reasons:

  • The demand job termination exit file is corrupted.

  • Cannot access the demand job termination exit file due to file system error.

[System Action]

Continues service startup processing, but the demand job termination exit is operated in invalid status.

[System Administrator Response]

Check whether the demand job termination exit file is correct, then eliminate the cause.

Restart the service after eliminating the cause.

Contact a Fujitsu technical support if the same message is output even after the service is restarted.

[Windows]MpMjes: ERROR: 1637: failed in allocate of the memory.

[Description]

Failed to allocate memory while retrieving a state of network job.

[System Action]

Aborts the process.

[User Response]

Wait a short time and try again.

[System Administrator Response]

Increase the physical memory or tune swap settings.

[Windows]MpMjes: ERROR: 1638: Process Information File open error occurred. Failed in the injection of the job.

[Description]

The network job submission process failed to open the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1639: Process Information File read error occurred. Failed in the injection of the job.

[Description]

The network job submission process failed to read the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1640: Process Information File write error occurred. Failed in the injection of the job.

[Description]

The network job submission process failed to write to the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1641: Process Information File close error occurred. Failed in the injection of the job.

[Description]

The network job submission process failed to close the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1642: Process Information File open error occurred. Job is carrying it out.

[Description]

The network job termination process failed to open the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1643: Process Information File read error occurred. Job is carrying it out.

[Description]

The network job termination process failed to read the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1644: Process Information File write error occurred. Job is carrying it out.

[Description]

The network job termination process failed to write to the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1645: Process Information File close error occurred. Job is carrying it out.

[Description]

The network job termination process failed to close the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[Windows] MpMjes: WARNING: 1646: Failed to write to the job execution history information file because the named pipe does not exist. The entry that failed to be output is: %1

[Description]

The named pipe did not exist at the time of job execution history information output. Therefore, the entry %1 was not output.

[Parameter]

%1: Job execution history information that failed to be output. This information uses the format of the mjsview log file output command (refer to "Execution Results/Output Format" under "mjsview Log File Output Command" in the Systemwalker Operation Manager Reference Guide for details).

[System Action]

Continues job execution.

[System Administrator Response]

When checking job execution history information, also check the log for the entry %1.

[Windows]MpMjes: WARNING: 1647: Failed to write to the job execution history information file because could not open the named pipe. The entry that failed to be output is: %1

[Description]

The named pipe could not be opened during job execution history information output. Therefore, the entry %1 was not output.

[Parameter]

%1: Job execution history information that failed to be output. This information uses the format of the mjsview log file output command (refer to "Execution Results/Output Format" under "mjsview Log File Output Command" in the Systemwalker Operation Manager Reference Guide for details).

[System Action]

Continues job execution.

[System Administrator Response]

When checking job execution history information, also check the log for the entry %1.

[Windows]MpMjes: WARNING: 1648: Failed to write to the job execution history information file because could not write to the named pipe. The entry that failed to be output is: %1

[Description]

The named pipe could not be written to during job execution history information output. Therefore, the entry %1 was not output.

[Parameter]

%1: Job execution history information that failed to be output. This information uses the format of the mjsview log file output command (refer to "Execution Results/Output Format" under "mjsview Log File Output Command" in the Systemwalker Operation Manager Reference Guide for details).

[System Action]

Continues job execution.

[System Administrator Response]

When checking job execution history information, also check the log for the entry %1.

[Windows]MpMjes: WARNING: 1649: Failed to open the job execution history information file. The entry that failed to be output is: %1

[Description]

The <log creation date>.log file could not be opened during job execution history information output. Therefore, the entry %1 was not output

[Parameter]

%1: Job execution history information that failed to be output. This information uses the format of the mjsview log file output command (refer to "Execution Results/Output Format" under "mjsview Log File Output Command" in the Systemwalker Operation Manager Reference Guide for details).

[System Action]

Continues job execution.

[System Administrator Response]

If there is no empty space in the file system, reserve some empty space.

When checking job execution history information, also check the log for the entry %1.

[Windows]MpMjes: ERROR: 1650: Failed to write to the job execution history information file. The entry that failed to be output is: %1

[Description]

The <log creation date>.log file could not be written to during job execution history information output. Therefore, the entry %1 was not output

[Parameter]

%1: Job execution history information that failed to be output. This information uses the format of the mjsview log file output command (refer to "Execution Results/Output Format" under "mjsview Log File Output Command" in the Systemwalker Operation Manager Reference Guide for details).

[System Action]

Continues job execution.

[System Administrator Response]

If there is no empty space in the file system, reserve some empty space.

When checking job execution history information, also check the log for the entry %1.

[Windows]MpMjes: WARNING: 1651: The format of the execution subsystem name definition file is invalid. Row No.=<row>

[Description]

The execution subsystem name definition file contains a row with an invalid format.

[Parameter]

row:Number of row in the execution subsystem name definition file containing the error.

[System Action]

Ignores the invalid row and continues the startup process for the Job Execution Control service.

[System Administrator Response]

Correct the invalid row and restart the Job Execution Control service.

[Windows]MpMjes: WARNING: 1652: The number of definitions in the execution subsystem name definition file exceeds 100.

[Description]

The number of execution subsystem name definitions in the execution subsystem name definition file exceeds 100.

[System Action]

Ignores definitions after the first 100 and continues the startup process for the Job Execution Control service.

[System Administrator Response]

Delete definitions after the first 100 from the execution subsystem name definition file.

[Windows]MpMjes: ERROR: 1653: An error occurred while reading the execution subsystem name definition file. Code=<code>

[Description]

An error occurred while the execution subsystem name definition file was being opened or loaded.

[Parameter]

code: Operating system error code

[System Action]

Stops the Job Execution Control service.

[System Administrator Response]

Eliminate the cause of the problem based on the error code generated by the operating system.

If the problem persists, use the Maintenance Information Collection Tool to collect information for Job Execution Control and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 1654: An error occurred when writing the execution subsystem name management file. Code=<code>

[Description]

An error occurred while the file that manages execution subsystem names was being opened or written to.

[Parameter]

code: Operating system error code

[System Action]

Stops the Job Execution Control service.

[System Administrator Response]

Check if the file system is depleted or an error has occurred. In such a case, eliminate the cause of the error from the file system in <Systemwalker Operation Manager installation directory>\mpwalker.jm\mpmjessv.

If the problem persists, use the Maintenance Information Collection Tool to collect information for Job Execution Control and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 2400: The license key was not registered or the trial time limit passed. Please register the license key if you continue to use this product.

[Description]

The license key is not registered, or the trial period has expired.

[System Action]

Outputs the message and cancels the processing.

[System Administrator Response]

A license is required. Refer to "Release Note" for information on corrective measures.

[Windows]MpMjes: INFO: 2401: This product operates as a trial period. The remainder trial period is XXXX days.

[Description]

This product is a trial version, and the remaining trial period is XXXX days.

[Parameter]

XXXX: Remaining trial period

[System Action]

Maintains the operation.

[System Administrator Response]

Purchase the product to continue using it after the trial period has expired.

[Windows]MpMjes: ERROR: 6030: Could not get spool directory path from registry in initialization process.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Installation of Job Execution Control server might have failed.

[System Administrator Response]

Reinstall Systemwalker Operation Manager.

[Windows]MpMjes: ERROR: 6031: Could not get queue path from registry in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Installation of Job Execution Control server might have failed.

[System Administrator Response]

Reinstall Systemwalker Operation Manager.

[Windows]MpMjes: ERROR: 6032: Could not get initialization file path from registry in initialization process. Error code=code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Parameter]

code: Error code

[Cause]

Installation of Job Execution Control server might have failed.

[System Administrator Response]

Reinstall Systemwalker Operation Manager.

[Windows]MpMjes: ERROR: 6033: Cannot open initialization file. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

  1. The initialization file may not exist.

  2. Other applications may be referencing the initialization file.

  3. Installation of Job Execution Control server might have failed.

[System Administrator Response]

  1. Open the Define Operation Information window and save the definition. Then start the Systemwalker MpMjesN service or operation. See "Defining the System Operating Information" in the Systemwalker Operation Manager Installation Guide for how to open the window.

  2. Exit all applications that refer to the initialization file, then start the Systemwalker MpMjesN service or operation. See "Initialization File (Job Execution Control)" in the Systemwalker Operation Manager Installation Guide for the initialization file.

  3. Reinstall Systemwalker Operation Manager.

[Windows]MpMjes: ERROR: 6034: Characters which cannot be used in initialization file are present.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[System Administrator Response]

Delete all invalid characters, then start the Systemwalker MpMjesN service or operation. For the invalid characters, see "initialization file (Job Execution Control)" in the Systemwalker Operation Manager Installation Guide.

[Windows]MpMjes: ERROR: 6035: Initialization file EOF detected while reading continuation rows of initialization parameters.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

There is an error in describing continuation lines.

[System Administrator Response]

Describe the continuation lines correctly, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6036: Length of 1 row of initialization parameter is exceeding. Row number=<row>

[Description]

More than 7168 bytes are described on a single line in the initialization file of the Job Execution Control server. The relevant row might have been treated as a continuation row since there are unnecessary commas at the end of the row.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

[System Administrator Response]

Modify the initialization file, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6037: Error in initialization parameter syntax.  Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Syntax error in parameter.

[System Administrator Response]

Correct parameter syntax, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6038: Parameter that cannot be specified in initialization file is mentioned. Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

  1. A parameter not included in the specification is specified.

  2. Parameter is not described correctly.

[System Administrator Response]

  1. Correct invalid parameter, then start the Systemwalker MpMjesN service or operation.

  2. Correct the wrong description in the parameter, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6039: Incorrect specified value of operand in initialization parameter. Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Invalid numeric or character string is specified in operand.

[System Administrator Response]

Specify a valid numeric or character string in operand, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6040: Error in definition sequence of initialization parameter. Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Other parameters might have been defined before the system parameter.

[System Administrator Response]

Redefine parameters concerned after the system parameter, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6041: Queue specified in dfltqueue operand of system parameter is not defined in queue parameter. Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The queue specified in the dfltqueue operand of the system parameter is not defined in the queue parameter.

[System Administrator Response]

Specify the queue (defined in the queue parameter) in the dfltqueue operand of the system parameter, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6042: dfltprty operand is not defined in either queue parameter or system parameter. Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system parameter or queue parameter in which the dfltprty operand is defined is not specified.

[System Administrator Response]

Describe the system parameter or queue parameter in which the dfltprty operand is defined, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6043: Initialization parameters after definition are described. Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Same parameter may be defined more than once.

[System Administrator Response]

Delete the unnecessary line on which the same parameter is redundantly described, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6044: Queue definition exceeded limit value. Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The number of queue control statement definitions exceeded the limit.

[System Administrator Response]

Delete unnecessary queue control statements, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6045: Incorrect start mode for starting job execution control.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6046: Failure in reading system information file in initialization process.  Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6047: Error in opening system information file in initialization process.  Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Other applications may be referring to the initialization file.

[System Administrator Response]

Exit all applications that refer to the initialization file, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6048: Error in writing to system information file in initialization process.  Error code=code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Parameter]

code: Error code

[Cause]

Other applications may be referring to the initialization file.

[System Administrator Response]

Exit all applications that refer to the initialization file, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6049: Error in creating queue directory in initialization process.  Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

A queue or spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6050: Error in opening queue information file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Other applications may be referring to the initialization file.

[System Administrator Response]

Exit all applications that refer to the initialization file, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6051: Error in writing to queue information file in initialization process. Error code=code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Parameter]

code: Error code

[Cause]

Other applications may be referring to the initialization file.

[System Administrator Response]

Exit all applications that refer to the initialization file, then the start Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6052: Operand that cannot be specified in initialization parameter is described. Row number=<row>

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

  1. The initialization parameter is misspelled.

  2. A parameter not included in the specification is specified.

[System Administrator Response]

  1. Correct the misspelling in the initialization parameter, then start the Systemwalker MpMjesN service or operation.

  2. Delete any parameters not included in the specification, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6053: No valid parameter in initialization file.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system parameter or queue parameter is not specified in initialization parameter.

[System Administrator Response]

Specify the system parameter or queue parameter in the initialization parameter, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6054: Failure in deleting spool directory in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Other applications may be referring to a directory under the spool directory.

[System Administrator Response]

Exit all applications that refer to a directory under the spool directory, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6055: Failure in deleting spool file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Other applications may be referring to a directory under the spool directory.

[System Administrator Response]

Exit all applications that refer to a directory under the spool directory, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6056: Failure in creating spool directory in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

A queue or spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6057: Error in read open process of queue information file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

A queue or spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

After stopping the Systemwalker MpMjesN service and deleting the spool directory of the Job Execution Control server, start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6058: Error to read from queue information file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

A queue or spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6059: Error in updation of queue information file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Other applications may be referring to a directory under the spool directory.

[System Administrator Response]

Exit all applications that refer to a directory under the spool directory, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6060: Error in read open process of job information file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6061: Error in reading from job information file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6062: Error in write opening of job information file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Other applications may be referring to a directory under the spool directory.

[System Administrator Response]

Exit all applications that refer to a directory under the spool directory, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6063: Error in writing to job information file in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates the subsystem number (when multiple subsystems are operated).

[Cause]

Other applications may be referring to a directory the under spool directory.

[System Administrator Response]

Exit all applications that refer to a directory under the spool directory, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6064: Error in queue search process in initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6065: Error in job initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6067: Error in reading from system information file in initialization process.  Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The memory required to operate the Job Execution Control server may be insufficient.

[System Administrator Response]

Exit all unnecessary applications, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6068: Failure in allocating heap for ACE in security process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The memory required to operate of the Job Execution Control server may be insufficient.

[System Administrator Response]

Exit all unnecessary applications, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6069: Failure in allocating heap for DOMAIN in security process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The memory required to operate of Job Execution Control server may be insufficient.

[System Administrator Response]

Exit all unnecessary applications, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6070: Failure in allocating heap for SNU in security process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The memory required to operate the Job Execution Control server may be insufficient.

[System Administrator Response]

Exit all unnecessary applications, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6071: Failure in getting xxx account information in initialization security process. Error code=code

[Parameter]

xxx: Account name

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The account information may be corrupted.

[System Administrator Response]

Check that the account information can be used, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6072: Abnormality regarding SID of xxx account in initialization security process. Error code=code

[Parameter]

xxx: Account name

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The account information may be corrupted.

[System Administrator Response]

Check whether the account information can be used, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6073: Failure in allocating heap for Account in security process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The memory required to operate the Job Execution Control server may be insufficient.

[System Administrator Response]

Exit all unnecessary applications, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6074: Failure in allocating heap for Object in security process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The memory required to operate the Job Execution Control server may be insufficient.

[System Administrator Response]

Exit all unnecessary applications, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6075: Failure in initializing heap for Object in security process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The memory required to operate the Job Execution Control server may be insufficient.

[System Administrator Response]

Exit all unnecessary applications, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6076: Failure in allocating heap for ACL in security process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The memory required to operate the Job Execution Control server may be insufficient.

[System Administrator Response]

Exit all unnecessary applications, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6077: Failure in initializing heap for ACL in security process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The program on the Job Execution Control server may be abnormal.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 6078: Error in setting ACE in initialization security process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The program on the Job Execution Control server may be abnormal.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 6079: ACL abnormality initialization security process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The program on the Job Execution Control server may be abnormal.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 6080: Failure in setting security information to object in initialization security process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The program on the Job Execution Control server may be abnormal.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[Windows]MpMjes: ERROR: 6081: System information file is absent during spool conversion process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Installation of Job Execution Control server might have failed.

[System Administrator Response]

Reinstall the Systemwalker Operation Manager server function.

[Windows]MpMjes: ERROR: 6082: System information file with incorrect file attribute during spool conversion process in initialization process.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6083: Failure in opening system information file during spool conversion process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6084: Failure in getting correct size of system information file during spool conversion process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6085: Failure in reading system information file in spool conversion process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6086: Incorrect read size of system information file in spool conversion process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6087: Failure in positioning write start position of system information file in spool conversion process of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6088: Incorrect position for writing system information file in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6089: Failure in writing new system information file in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The system information file on the Job Execution Control server may be corrupted

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6090: System information file that cannot be handled by current V/L job execution control in spool conversion of initialization process. Error code=code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool cannot be used on the installed V/L of Job Execution Control server.

[System Administrator Response]

Reinstall V/L of the Job Execution Control server that was using the spool, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6091: Structure file with incorrect file attribute found in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6092: Failure in opening structure file in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6093: Failure in getting size of structure file in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6094: Failure in reading structure file in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6095: Incorrect read size of structure file in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6096: Failure in opening new structure file in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6097: Failure in writing new structure file in spool conversion of initialization process. Error code=code

[Parameter]

code: Error code

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6098: Structure file that cannot be handled with current V/L job execution control was found in spool conversion of initialization process.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The structure file in the spool cannot be used on the installed V/L of Job Execution Control server.

[System Administrator Response]

Reinstall V/L of the Job Execution Control server that was using the spool, then start the Systemwalker MpMjesN service or operation.

[Windows]MpMjes: ERROR: 6099: Incorrect structure file found in spool conversion of initialization process.

[System Action]

Aborts the Systemwalker MpMjesN service or operation.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

The spool on the Job Execution Control server may be corrupted.

[System Administrator Response]

Stop the Systemwalker MpMjesN service, delete the spool directory of the Job Execution Control server, then start the Systemwalker MpMjesN service or operation. The default value of the spool directory is as follows:

mpwalker.jm\mpmjessv\mjespool located in the installation directory

[Windows]MpMjes: ERROR: 6102: The number of host group definitions crossed over the limit value.

[Description]

The number of defined host groups exceeded 64.

[System Action]

Aborts the Systemwalker MpMjesN service.

N: Indicates subsystem number (at multiple subsystems operation).

[System Administrator Response]

Correct the initialization file, then start the Systemwalker MpMjesN service.

[Windows]MpMjes: ERROR: 6106: Could not found the directory specified by the path operand of the log parameter.Row number=<row>

[Description]

The directory specified at the path operand in the log parameter in the initialization file could not be found.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Numeric values or strings that are invalid for operand are specified.

[System Administrator Response]

Use values or strings that are valid for operand, then start the Systemwalker MpMjes service or operation.

[Windows]MpMjes: ERROR: 6107: Could not found the directory specified by the path operand of the record parameter.Row number=<row> number=<row>

[Description]

The directory specified at path operand in record parameter in the initialization file could not be found.

The directory specified at the path operand in the log parameter in the initialization file could not be found.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Aborts the Systemwalker MpMjesN service.

N: Indicates subsystem number (at multiple subsystems operation).

[Cause]

Numeric values or strings that are invalid for operand are specified.

[System Administrator Response]

Use values or strings that are valid for operand, then start the Systemwalker MpMjes service or operation.

[Windows]MpMjes: ERROR: 6108: Could not found the host group specified by the host operand of the queue parameter. Row number=<row>

[Description]

The host group described in the host operand of the queue parameter may not be defined.

[System Action]

Aborts the Systemwalker MpMjesN service.

N: Indicates a subsystem number. (At operation of multiple subsystems)

[System Administrator Response]

Correct the initialization file, then start the Systemwalker MpMjesN service.

[Windows]MpMjes: WARNING: 6109: The host group has more than one host with the same name. The hosts specified redundantly have been ignored.

[Description]

The host group has more than one host with the same name. The first host can be recognized and none of the following hosts can be recognized.

[System Action]

Recognizes only the first specified host and starts the Systemwalker MpMjesN service.

N: Subsystem number (for multiple subsystems operation)

[System Administrator Response]

Review the settings to avoid specifying more than one host with the same name in the host group.

[Windows]MpMjes: WARNING: 6110: XXXX Systemwalker MpMjes failed to set policy information.

[Description]

Setting of the distributed policy information (Operating Information, Trust host information, Job owner information, Node name definition file, or execution subsystem definition file) failed.

[Parameter]

XXXX : Policy information file in copy destination

[System Action]

The Job Execution Control service startup process continues, and the Job Execution Control service starts without the policy information that failed to be set.

[System Administrator Response]

Check the policy information that failed to be set. To reset the policy information, restart the Job Execution Control service.

[Windows]MpMjes: ERROR: 6111: Failed to allocate memory during initialization.

[Description]

Memory allocation failed during initialization processing.

[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.

[Windows]MpMjes: WARNING: 9006:  It doesn't end even if job name (jobname) lapses by end plan time (time) minutes.(Project Name=projectname,Job Net=jobnetname)

[Description]

Time lapse for the job has exceeded the predefined estimated processing time.

[Parameter]

jobname : Job name

time : Predefined estimated processing time

projectname : Project name

jobnetname : Jobnet name

[System Action]

Continues job execution.

[System Administrator Response]

If the parent process of the job has terminated but the job has not terminated, there may still be child processes running under the job. Terminate the job forcibly, if necessary.

[Windows]MpMjes: ERROR: 9007: The job jobname was not canceled by Execution Server hostname.

[Description]

The job was not canceled by the execution server.

[Parameter]

jobname: Job name

hostname: Execution server name

[User Response]

Check the status of the applicable job by executing the qjstat command on the execution server, and then cancel the job by executing the qdel command. Note the following points when checking the job on the execution server.

  • If running multi-subsystem operation, be careful to use the correct subsystem number.

  • If multiple jobs with the same name exist, be careful to stop the correct job.

  • At the end of the job name, "_" is appended.

[System Administrator Response]

Port jmnet communication from the submitting server to the execution server has been interrupted or temporarily unavailable, preventing normal communication. Take the required actions to fix the communication issue.

[UNIX]MpMjes:ERROR: 10003: Could not found path to spool directory for initialization. Row number=<row>

[Description]

An error occurred while reading the host group information file at initialization.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Administrator Response]

Correct the initialization file and start Job Execution Control daemon.

[UNIX]MpMjes: ERROR: 10007: Cannot open initialization file.<code>

[Description]

The initialization file of the Job Execution Control server cannot be opened due to either of the following reasons:

  1. The initialization file of the Job Execution Control server does not exist.

  2. Installation of the Job Execution Control server failed.

  3. There was an error in the procedure used to migrate the operation information directory for Job Execution Control to the shared disk when the cluster system was set up.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

For 1): Open the Define Operation Information window and save the definition. Then start Job Execution Control daemon. See "Defining the System Operating Information" in the Systemwalker Operation Manager Installation Guide for how to open the window.

Initialization file name:/etc/mjes/initfile

For 2): Reinstall Systemwalker Operation Manager.

For 3): Migrate the operation information directory for Job Execution Control to the shared disk correctly. Refer to "Moving Resources to the Shared Disk" in the Cluster Setup Guide for details on the migration procedure.

[UNIX]MpMjes: ERROR: 10009: EOF of initialization file detected while reading continuation <row> of initialization parameter.

[Description]

EOF was detected while reading the file in which the initialization file of the Job Execution Control server was defined as there was an error in describing the continuation row of the initialization file of the Job Execution Control server.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after modifying the continuation row correctly.

[UNIX]MpMjes: ERROR: 10010: Length of a row of initialization parameter too long. Row number=<row>

[Description]

More than 7168 bytes are described on a single line in the initialization file of the Job Execution Control server. The relevant row might have been treated as a continuation row since there are unnecessary commas at the end of the row.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after modifying the initialization file.

[UNIX]MpMjes: ERROR: 10011: Fault in initialization parameter method. Row number=<row>

[Description]

There is an error in the syntax of the initialization file of the Job Execution Control server.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after describing the parameter syntax correctly.

[UNIX]MpMjes: ERROR: 10012: Initialization file contains parameters which cannot be specified. Row number=<row>

[Description]

A parameter that cannot be specified in the initialization file of the Job Execution Control server is described.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after modifying the parameter correctly.

[UNIX]MpMjes: ERROR: 10013: Incorrect value specified for initialization parameter operand. Row number=<row>

[Description]

The value specified in the operand of the initialization file parameter of the Job Execution Control server is incorrect. Character strings or numeric values that cannot be specified in the operand are specified.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after describing the character strings or numeric values that can be specified in the operand.

[UNIX]MpMjes: ERROR: 10014: Fault in definition order of initialization parameter. Row number=<row>

[Description]

There is an error in the parameter definition sequence of the initialization file of the Job Execution Control server. Other parameters have been defined before defining the system parameter.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after correcting the definition order to define the system parameter first and then others.

[UNIX]MpMjes: ERROR: 10015: The queue specified in the dfltqueue operand of system parameter, is not defined by queue parameter. Row number=<row>

[Description]

The queue specified in the dfltqueue operand of the system parameter is not defined in the queue parameter.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after specifying one of the queues defined in the queue parameter in the dfltqueue operand of the system parameter.

[UNIX]MpMjes: ERROR: 10016: dfltprty operand not defined either in system parameter or queue parameter. Row number=<row>

[Description]

The dfltprty operand is defined neither in the system parameter nor in the queue parameter.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after defining the dfltprty operand either in the system parameter or in the queue parameter.

[UNIX]MpMjes: ERROR: 10017: Specifies the initialization parameter already defined. Row number=<row>

[Description]

The parameter of the initialization file of the Job Execution Control server is specified more than once.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the unnecessary parameter from the row in which the relevant parameter is described.

[UNIX]MpMjes: ERROR: 10018: The number of definitions of queue exceeded the limit.

[Description]

The number of queue definitions exceeded the limit (64).

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the unnecessary queue parameter from the description.

[UNIX]MpMjes: ERROR: 10020: Failure reading system information file during initialization.<code>

[Description]

Failure in reading the system information file during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10021: Error in write open of system information file during initialization.<code>

[Description]

An error occurred in the write open process to the system information file during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10022: Error in writing to system information file while initializing.<code>

[Description]

An error occurred in writing to the system information file during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10023: Error creating queue directory during initialization.<code>

[Description]

An error occurred in creating the queue directory during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10024: Error in write open process of queue information file during initialization.<code>

[Description]

Error in the write open process of the system information file during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10025: Error writing in the queue information file during initialization.<code>

[Description]

An error occurred in writing the queue information file during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10026: Initialization file has operand which cannot be specified. Row number=<row>

[Description]

An operand that cannot be specified in the initialization file of the job execution server is described.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after modifying the operand in the initialization file correctly.

[UNIX]MpMjes: ERROR: 10027: Initialization file does not have valid parameters.

[Description]

There is no valid parameter in the definition contents of the initialization file of the Job Execution Control server.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after describing a queue parameter and a system parameter in the initialization file of the Job Execution Control server.

[UNIX]MpMjes: ERROR: 10028: Failure deleting spool directory during initialization.<code>

[Description]

Failure in deleting the spool directory during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10029: Failure deleting files in the spool directory during initialization.<code>

[Description]

Failure in deleting the files in the spool directory during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10030: Failure creating spool directory during initialization.<code>

[Description]

Failure in creating spool directory during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10032: Error in read open process of queue information file during  initialization.<code>

[Description]

An error occurred in the read open process of the queue information file during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10033: Error reading from queue information file during initialization.<code>

[Description]

An error occurred in reading from the queue information file during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10034: Error updating queue information file during initialization.<code>

[Description]

An error occurred in updating the queue information file during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10040: Error finding the queue during initialization.<code>

[Description]

An error occurred in searching the queue during initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10041: Error occurred in job initialization.<code>

[Description]

An error occurred in job initialization.

[Parameter]

code: Error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after deleting the spool directory of the Job Execution Control server. The default value of the spool directory is as follows:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10056: Could not found the directory specified by the path operand of the log parameter. Row number=<row>

[Description]

The directory specified in the path operand in the log parameter in the initialization file could not be found.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after creating the directory specified in the path operand.

[UNIX]MpMjes: ERROR: 10058: Could not found the directory specified by the path operand of the record parameter. Row number=<row>

[Description]

The directory specified in the path operand in the record parameter in the initialization file could not be found.

[Parameter]

row: Row number of the parameter with error

However, if parameter and operand straddle multiple lines, this parameter indicates one of the multiple line numbers instead of the line number on which the error actually occurred.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after creating the directory specified in the path operand.

[UNIX]MpMjes: ERROR: 10059: The number of host group definitions crossed over the limit value.

[Description]

The number of defined host groups exceeded 64.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after correcting the initialization file.

[UNIX]MpMjes: ERROR: 10060: Could not found the host group specified by the host operand of the queue parameter.

[Description]

The host group described in the host operand of the queue parameter may not be defined.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon after correcting the initialization file.

[UNIX]MpMjes: ERROR: 10061: mjsdaemon : Invalid option flag specified.

[Description]

An invalid option was specified.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Correct the option and start Job Execution Control daemon.

[UNIX]MpMjes: ERROR: 10062: mjsdaemon : Invalid sub-system number specified.

[Description]

An invalid sub-system number was specified.

[System Action]

Aborts processing.

[System Administration Response]

Specify the correct sub-system number and start Job Execution Control.

[UNIX]MpMjes: ERROR: 10063: mjsdaemon : The environment of the sub-system number does not exist.

[Description]

The environment of the sub-system number does not exist.

[System Action]

Aborts processing.

[System Administrator Response]

Specify a sub-system number that actually exists.

When Job Execution Control is started with the status transition procedure in a cluster environment, confirm that the shared disk assigned for the subsystem is set to be mounted correctly in case of a failover.

[UNIX]MpMjes: ERROR: 10064: mjsdaemon: Insufficient privilege.

[Description]

The user have no privileges to start Job Execution Control daemon.

[System Action]

Aborts the startup processing.

[User Response]

Request the system administrator to start Job Execution Control daemon.

[System Administrator Response]

Start Job Execution Control daemon.

[UNIX]MpMjes: ERROR: 10065: mjsdaemon : Unable to chdir() to spoolname.

[Description]

Job Execution Control daemon failed to move spoolname to another directory.

[Parameter]

spoolname: Spool name

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Check that the spool directory exists. The initial value of the spool directory is shown below:

/var/spool/mjes/mjespool

[UNIX]MpMjes: ERROR: 10066: mjsdaemon was not started. because swadmin group does not exist.

[Description]

Job Execution Control could not be started because no swadmin group exists in the system.

[System Action]

Aborts processing.

[System Administrator Response]

Register the swadmin group in the system and start Job Execution Control.

[UNIX]MpMjes: ERROR: 10067: mjsdaemon : Already starting.

[Description]

Job Execution Control daemon is already being started.

[System Action]

Aborts the newly demanded process.

[Cause]

This may have occurred for the following reasons:

  1. The startup command for Job Execution Control has been called during the startup processing of Job Execution Control.

  2. The run level has been changed during the startup processing of Job Execution Control.

[UNIX]MpMjes: ERROR: 10068: Failed to initialize the jclinfo directory.

[Description]

Failed to create the jcl information directory.

[System Action]

Stops Job Execution Control daemon.

[Cause]

The cause can be attributed to any of the following, regarding the /var/spool/mjes directory or the /var/spool/mjes/mjesN: directory (N: subsystem number for multiple subsystems operation):

  • There is not enough space on the disk

[System Administrator Response]

Remove the error cause and start Job Execution Control.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10069: mjsdaemon could not started. because to allocate job control table failed.

[Description]

Failed to start Job Execution Control daemon because enough space for job control table could not be reserved.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

There is not enough memory to start Job Execution Control daemon. Close unnecessary applications or add more memory, and then restart Job Execution Control daemon.

[UNIX]MpMjes: ERROR: 10070: mjsini process fork failed. jobnet= <jobnet> jobname = <jobname> jobno= <jobno>

[Description]

Failed to create an initiator process.

[Parameter]

jobnet: Job net name

jobname: Job name

jobno: Job number

[System Action]

Does not execute job.

[System Administrator Response]

There is not enough memory to start mjsini. Close unnecessary applications or add more memory.

[UNIX]MpMjes: WARNING: 10071: The job execution history/status information program failed to start.

[Description]

Failed to start the history information collection daemon.

[System Action]

Disables the logging function and continues the process.

[Cause]

The cause can be attributed to the following:

  1. There are not enough system resources.

[System Administrator Response]

Remove the error cause and start Job Execution Control.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: WARNING: 10072: Unable to open to the job execution status information file.

[Description]

Failed to open the job operation result information file.

[System Action]

Continues the startup process of Job Execution Control daemon. Suspends writing to the file.

[Cause]

The cause can be attributed to the following:

  • There is not enough space on the file system

  • No destination directory to save the job operation result information file exists

[System Administrator Response]

  • For space problem, reserve enough space by deleting unnecessary files and so on.

  • For destination directory problem, create the directory you specified in Saved Directory of Save operation results data in the Logging sheet of the Define Operating Information window.

In other cases, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10073: The system error occurred during the processing of the job execution history/status information program.

[Description]

An error occurred on the history information collection daemon.

[System Action]

Disables the logging function and continues the process.

[Cause]

The cause can be attributed to the following:

  1. There are not enough system resources.

[System Administrator Response]

Remove the error cause and start Job Execution Control.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10074: Error in writing to the job execution status information file.

[Description]

Failed to write to the job operation results information file.

[System Action]

Continues the startup process of Job Execution Control daemon. Suspends writing to the file.

[Cause]

The cause can be attributed to the following:

  1. There is not enough space on the file system

[System Administrator Response]

Reserve enough space by deleting unnecessary files and so on. In other cases, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: WARNING: 10075: Unable to make the directory for sub-system of history/status information file.

[Description]

Failed to create the execution history log directory or operation results log directory for subsystems.

[System Action]

Disables the logging function and continues the process.

[System Administrator Response]

The cause can be attributed the following:

  • The user attempted to create the directory in a path that actually does not exist

  • A file with the same name already exists, and so on

Examine the file system on which the log directory exists and resolve the cause of the error. Then restart Systemwalker. If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10076: Error in sending job message to Job Scheduler (jscmid:jscmid, mtype:mtype, mtext:mtext).

[Description]

Failed to notify job status to Jobscheduler.

[Parameter]

jscmid: Message number

mtype: Message type

mtext: Message text

[System Action]

Continues job execution.

[Cause]

The cause can be attributed to the following:

  1. There are not enough messages that are used as system resources

[System Administrator Response]

In this case, extend the message queue by referring to "Extending the Message Queue" in the Systemwalker Operation Manager Installation Guide. In other cases, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10077: jobinfo read error. delete path(path)

[Description]

Failed to read jobinfo (job information file).

[Parameter]

path: File path that could not be read

[System Action]

Aborts job execution.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10078: jobinfo read error. delete jobdir=jobdir

[Description]

Failed to read jobinfo (job information file).

[Parameter]

jobdir: Directory that could not be read

[System Action]

Aborts job execution.

[User Response]

Restart the canceled job as required.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool if the issue occurs frequently, and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10079: PreInitJob() : jcl struct convert error. delete jobdir=jobdir. code=code.

[Description]

Failed to convert the JCL structure.

[Parameter]

jobdir: Directory that could not be deleted

code: Error code

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10080: PreInitJob() :Return value can not be set to jobinfo file. jobno=jobno,  queue=queue

[Description]

Failed to write data to jobinfo (job information file).

[Parameter]

jobno: Job number

queue: Queue name

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10081: jobinfo write error. jobno=jobno, queue=queue

[Description]

Failed to write data to jobinfo (job information file).

[Parameter]

jobno: Job number

queue: Queue name

[System Action]

Aborts job execution.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10082: jmnetsv : Security mode is set to OFF. Because swadmin group does not exist.

[Description]

Security mode is set to off during system operation since no swadmini group exists.

[System Action]

Sets security mode to off and continues the process.

[System Administrator Response]

Create a swadmin group for the group definition of the OS and restart Systemwalker Operation Manager.

[UNIX]MpMjes: ERROR: 10083: mjsnetsv : Failed in deciding Network Control Table size.

[Description]

mjsnetsv could not decide the size of the network control table.

[System Action]

Stops mjsnetsv.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10084: jmnetsv : Failed in allocating Network Control Table.

[Description]

Failed to allocate memory for the network control table.

[System Action]

Stops jmnetsv.

[System Administrator Response]

Memory is insufficient to activate jmnetsv. Terminate other unnecessary applications or add memory, then restart Systemwalker Operation Manager.

[UNIX]MpMjes: ERROR: 10085: mjsnetsv : Failed in allocating Network Control Table.

[Description]

Failed to allocate memory for the network control table.

[System Action]

Stops mjsnetsv.

[System Administrator Response]

Memory is insufficient for starting mjsnetsv. Terminate unnecessary applications or add memory, and then start Job Execution Control daemon again.

[UNIX]MpMjes: ERROR: 10086: mjsnetsv : nodemap process failed.

[Description]

An abnormality occurred while processing the node name definition file.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10087: mjsnetsv : CLUSTER HOST information file format is invalid.

[Description]

The format of the node name definition file is incorrect.

[Cause]

In the cluster system where node names are not inherited, if the schedule server went down or switched, the status of the job that requests an execution to the job execution server is not available.

There is the following possible cause.

  1. The description in the nodemap file is incorrect.

[System Administrator Response]

For 1): Correct the wrong description in the nodemap file, then restart the daemon of Job Execution Control. see the Systemwalker Operation Manager Installation Guide for information about the description format of the nodemap file.

[UNIX]MpMjes: ERROR: 10088: Failed in the end notification of job (jobno=<jobno>, org_host=<host>, org_jobno=<org_jobno>, org_sub_system=<subsys>)

[Description]

With the processing that notifies the job termination from the job execution server to the submission server, it failed to write to a file.

This prevents job termination from being notified.

[Parameter]

jobno: Job No. on execution server

host: Input server name

org_jobno: Job No. on input server

subsys: Input server subsystem No.

[System Action]

Terminates the job abnormally with '0x40000132' on the input server.

[System Administrator Response]

Check whether the file system runs out of space or experiences any problem. If this is the case, eliminate the problem of the file system. The file system to be checked is located in "/var/spool/mjes". For a symbolic link, check the actual file in the link destination.

[UNIX]MpMjes: ERROR: 10089: mjsrjob : job information file write error. error code = xxx. jobname = xxx, job number = xxx, job end code = xxx.

[Description]

In the network job submission process, the internal file of Job Execution Control could not be overwritten.

[Parameter]

error code : Error code in the system

jobname : Job name

job number : Job number

job end code : Job completion code

[User Response]

Contact your system administrator.

[System Administrator Response]

Remove the cause of the error by examining its error code.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10090: mjsrjob : job information file read error. error code = CCCC. jobname = XXXX, job number = YYYY, job end code = ZZZZ.

[Description]

In the network job submitting process, the internal file of Job Execution Control could not be fetched.

The following reasons are assumed:

  1. A job that starts Systemwalker Operation Manager was running. Its name was XXXX (ending with an underscore "_") and its number was YYYY. It could have been either a local job or a network job.

    Then a different network job was submitted and finished executing.

  2. A job (job A in a nested configuration where Job A submits job B) that executes the qsub command (including shell scripts that execute the qsub command) was running. Its name was XXXX (ending with an underscore "_") and its number was YYYY. It could have been either a local job or a network job. The -x and -rh options were both specified in the qsub command.

    Then execution of the network job (job B in a nested configuration that submits job B from job A) that was submitted by the qsub command ended.

[Parameter]

CCCC: Error code in the system

XXXX: Job name

YYYY: Job number

ZZZZ: Job completion code

[System Action]

If the cause is aa. or bb, execution of the network job on the execution server ends and output is sent to the standard output and standard error output. However, the end code fails to be set on the submitting server, and the job ends abnormally with the code "0x40000999". The actual end code of the job is ZZZZ.

[User Response]

Contact your system administrator.

[System Administrator Response]

Take one of the following corrective measures according to the cause of the error.

  1. Do not run a job that starts Systemwalker Operation Manager in Systemwalker Operation Manager.

  2. Do not specify both the -x and -rh options in the qsub command. Use the -env option instead of the -x option and set the required environment variables.

In cases other than the above, remove the cause of the error by examining CCCC.

If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: WARNING: 10091: The continuous execution modes of each server are not unified.

[Description]

The continuous execution modes on each server are not identical.

[System Administrator Response]

Unify the continuous execution modes of each server. See "jmmode continuous execution mode switching command" in the Systemwalker Operation Manager Reference Guide for how to switch continuous execution mode.

[UNIX]MpMjes: ERROR: 10092: F3CUB_LOG_PIPE open error occurred. error code=xxxx

[Description]

Failed to open an internal file of Job Execution Control.

[Parameter]

xxxx : OS error code

[System Action]

Aborts writing to the history logging file. This error does not affect job execution although job history is no longer recorded in the history logging file. Continues job execution.

[User Response]

Contact your system administrator.

[System Administrator Response]

Remove the cause of the error based on the OS error code, and restart the Job Execution Control daemon if necessary. If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10093: F3CUB_LOG_PIPE write error occurred. error code=xxxx

[Description]

An error occurred while writing to an internal file of Job Execution Control.

[Parameter]

xxxx : OS error code

[System Action]

Aborts writing to the history logging file. This error does not affect job execution although job history is no longer recorded in the history logging file. Continues job execution.

[User Response]

Contact your system administrator.

[System Administrator Response]

Remove the cause of the error based on the OS error code, and restart the Job Execution Control daemon if necessary. If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10094: Console process fork failed. error code=xxxx

[Description]

Failed to start the history logging daemon.

[Parameter]

xxxx : OS error code

[System Action]

Aborts startup of the history logging daemon. This error does not affect job execution although job history is no longer recorded in the history logging file. Continues job execution.

[User Response]

Contact your system administrator.

[System Administrator Response]

Remove the cause of the error based on the OS error code, and restart the Job Execution Control daemon if necessary. If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10095: Console process execute failed. error code=xxxx

[Description]

Failed to start the history logging daemon.

[Parameter]

xxxx : OS error code

[System Action]

Aborts starting the history logging daemon. This error does not affect job execution although job history is no longer recorded in the history logging file. Continues job execution.

[User Response]

Contact the system administrator.

[System Administrator Response]

Remove the cause of the error based on the OS error code, and restart the Job Execution Control daemon if necessary. If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10096: mjsini process execute failed. error code=xxxx

[Description]

Failed to start the job execution initiator.

[Parameter]

xxxx : OS error code

[System Action]

Aborts starting the job execution initiator.

[User Response]

Contact your system administrator.

[System Administrator Response]

Remove the cause of the error based on the OS error code, and restart the Job Execution Control daemon if necessary. If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10097: mjsisini process execute failed. error code=xxxx

[Description]

Failed to start the online initiator for Job Execution Control.

[Parameter]

xxxx : OS error code

[System Action]

Aborts startup of the online initiator for Job Execution Control.

[User Response]

Contact your system administrator.

[System Administrator Response]

Remove the cause of the error based on the OS error code, and restart the Job Execution Control daemon if necessary. If the problem persists, collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10098: job status is not notify.

[Description]

Failed to notify Jobscheduler of the job status due to insufficient system resource (message queue).

[User Response]

Contact the system administrator.

[System Administrator Response]

Expand message queue by referring to "Extending the Message Queue" in the Systemwalker Operation Manager Installation Guide.

[UNIX]MpMjes: ERROR: 10099: Error in reading the host group file during initialization.

[Description]

An error occurred when reading the host group information file during the initialization process.

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10100: Failure in starting mjsnetsv daemon.

[Description]

Failed to start the network job receiving daemon.

[System Action]

No network jobs can be accepted.

[System Administrator Response]

There is not enough memory to start mjsnetsv. Close unnecessary applications or add more memory, and then restart Job Execution Control daemon.

[UNIX]MpMjes: INFO : 10101: The Systemwalker MpMjes has been stopped.

[Description]

Job Execution Control stopped normally.

[UNIX]MpMjes: INFO : 10102: The Systemwalker MpMjes has been started. startmode=x, lang=y, jmmode=z.

[Description]

Job Execution Control started.

[Parameter]

startmode : Status of daemon at startup

  • 0 : Recovery mode

  • 1 : Initialization mode

  • 2 : Continuous mode

lang : Character code at startup

  • 1 : English

  • 3 : EUC

  • 4: UTF-8

jmmode : Enable/disable continuous execution mode at startup

  • 0 : Disable

  • 1 : Enable

[UNIX]MpMjes: ERROR: 10110: mjsnetsv : Failed in the bind of port number <number>.

[Description]

mjsnetsv failed to bind port <number>.

[Parameter]

number: Port number

[System Action]

Stops mjsnetsv.

[System Administrator Response]

Port <number> is possibly used by another application. Change the port number for the relevant application, or change the port number for mjsnet, and then restart Job Execution Control daemon.

[UNIX]MpMjes: ERROR: 10111: jmnetsv : Failed in the bind of port number <number>.

[Description]

jmnetsv failed to bind port <number>.

[Parameter]

number: Port number

[System Action]

Stops jmnetsv.

[System Administrator Response]

Port <number> is possibly used by another application. Change the port number for the relevant application, or change the port number for jmnet, then restart Systemwalker Operation Manager.

[UNIX]MpMjes: ERROR: 10112: Failure in starting session manager daemon.

[Description]

Failed to start the session management daemon.

[Parameter]

Interrupts start processing of the session management daemon among the daemons that are started by the Systemwalker MpJmSrv service.

[System Administrator Response]

Collect Job Execution Control information with the Maintenance Information Collection Tool and contact a Fujitsu technical support.

[UNIX]MpMjes: WARNING: 10113: mjsnetsv : TCP port number does not exist.

[Description]

TCP port number for network job monitoring does not exist.

[System Administrator Response]

Add TCP port number for network job monitoring corresponding to each sub-system.

However, if the message is output in an environment where no network job is submitted, you can ignore the message since it does not affect system operation. (This message is output at startup of Job Execution Control or daemons as a warning message when submitting a network job from a server with multiple subsystems operation to a server with the same configuration.)

[UNIX]MpMjes: WARNING: 10114: It doesn't end even if job name (jobname) lapses by end plan time (time) seconds. (Project Name=projectname, Job Net=jobnetname)

[Description]

Time lapse for the job has exceeded the predefined estimated processing time.

[Parameter]

jobname : Job name

time : Predefined estimated processing time

projectname : Project name

jobnetname : Jobnet name

[System Action]

Continues job execution.

[System Administrator Response]

If the parent process of the job has terminated but the job has not terminated, there may still be child processes running under the job. Terminate the job forcibly, if necessary.

[UNIX]MpMjes: ERROR: 10115: job process fork failed. jobnet= jobnet jobname= jobname jobno= jobno

[Description]

Failed to create a job process.

[Parameter]

jobnet : Job net name

jobname: Job name

jobno :Job number

[System Action]

Aborts startup of the job

[Cause]

The cause can be attributed to the following:

  • The maximum number of processes that can be created on the system has been exceeded.

[System Administrator Response]

Review the concurrency value of job execution.

[UNIX]MpMjes: WARNING: 10120: Execution server <hostname> was excluded from host group <hostgroup>.

[Description]

With distributed execution jobs, the job requested to the execution server cannot be processed. As the result, the execution server has been excluded from the distribution target.

[Parameter]

hostname: Name of the execution server that was excluded from the distribution target because it failed to process the requested job.

hostgroup: Name of the host group that the excluded execution server belonged to.

[System Action]

The relevant execution server is excluded from the distribution target.

[System Administrator Response]

Eliminate the cause after checking the execution server status that failed to process the requested job. This may have occurred for the following reasons:

  • The power to the execution server is not turned on.

  • The job execution service is not running.

  • The network is disconnected.

[UNIX]MpMjes: WARNING: 10123: Abnormalities were detected to mjes.job.exit file.

[Description]

Failed to check the demand job termination exit file.

[Cause]

This may have occurred for the following reasons:

  • Execution rights may not be included in permissions to the demand job termination exit file.

  • The demand job termination exit file is corrupted.

  • Cannot access to the demand job termination exit file due to file system error.

[System Action]

Continues daemon startup process, but the demand job termination exit is operated in invalid status.

[System Administrator Response]

Check whether the demand job termination exit file is correct, then eliminate the cause.

Restart the daemon after eliminating the cause.

Contact a Fujitsu technical support if the same message is output even after the daemon is restarted.

[UNIX]MpMjes: ERROR: 10124: mjes.job.exit was not able to be called. code = xxxx

[Description]

Failed to call the demand job termination exit.

[Cause]

This may have occurred for the following reasons:

  • The demand job termination exit file does not exist.

  • The job termination exit file is not executable.

  • Failed to generate the process due to low memory.

[Parameter]

xxxx: System error code that is notified from the operating system.

[System Action]

Aborts the calling process of the demand job termination exit.

[System Administrator Response]

Eliminate the cause according to error codes of the operating system, then restart the Job Execution Control daemon if necessary.

If this problem is not resolved, collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: WARNING: 10127: The host group has more than one host with the same name. The hosts specified redundantly have been ignored.

[Description]

The host group has more than one host with the same name. The first host can be recognized and none of the following hosts can be recognized.

[System Action]

Recognizes only the first specified host and starts Job Execution Control daemon.

[System Administrator Response]

Review the settings to avoid specifying more than one host with the same name in the host group.

[UNIX]MpMjes: ERROR: 10128: Failed to create the exclusive processing control file for distributed execution. error code=xxxx

[Description]

Failed to create the exclusive control file for distributed job execution.

[Parameter]

xxxx: OS error code

[System Action]

Stops Job Execution Control daemon.

[System Administrator Response]

Remove the cause of the error based on the OS error code indicated, and then restart Job Execution Control daemon. If the error still remains unsolved with the OS error code, contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10129: mjsdaemon has stopped, because the system error occurred.

[Description]

A system error occurred in the processing of a Job Execution Control daemon.

[System Action]

Stops Job Execution Control daemon.

[User Response]

If this error recurs, contact your system administrator.

[System Administrator Response]

Collect the information about Job Execution Control by using the Maintenance Information Collection Tool, and contact your Fujitsu engineer.

[UNIX]MpMjes: WARNING: 10132: XXXX The daemon failed to set policy information.

[Description]

Setting of the distributed policy information (Operating Information, Trust host information, Job owner information or Node name definition file, or execution subsystem definition file) failed.

[Parameter]

XXXX: Policy information file in copy destination

[System Action]

The Job Execution Control service startup process continues, and the Job Execution Control service starts without the policy information that failed to be set.

[System Administrator Response]

Check the policy information that failed to be set. To reset the policy information, restart the Job Execution Control service.

[UNIX]MpMjes: WARNING: 10133: Internal configuration file is invalid. XXXX

[Description]

The format of the specified file is invalid.

[Parameter]

XXXX: Invalid section name, key name

May not be output.

[System Action]

Continues the process using the default values.

[System Administrator Response]

Review the content of the definition file (mjconf.ini).

[UNIX]MpMjes: WARNING: 10135: The line %1 of the user control list for job execution is too long.

[Description]

Line number %1 of the user control list for job execution was ignored because it contained more than the maximum allowable number of bytes (1,024).

[Parameter]

%1: The number of the line in the user control list for job execution

[System Action]

Continues the startup process of the Job Execution Control daemon.

[User Response]

Change the relevant line of the user control list for job execution so that it contains no more than 1,024 bytes.

[UNIX]MpMjes: WARNING: 10136: The user control list for job execution contains more than 256 users.

[Description]

The user control list for job execution contained more than 256 lines, so lines 257 and later were ignored.

[System Action]

Continues the startup process of the Job Execution Control daemon.

[User Response]

Delete all lines of the user control list for job execution beyond line 257.

[UNIX]MpMjes: ERROR: 10137: Failed to open the user control list for job execution. error code=xxxx

[Description]

The user control list for job execution could not be opened.

[Parameter]

xxxx: Operating system error code

[System Action]

Stops the Job Execution Control daemon.

[System Administrator Response]

Eliminate the cause of the problem based on the error code generated by the operating system.

If the problem persists, use the Maintenance Information Collection Tool to collect information for Job Execution Control and contact a Fujitsu SE.

[UNIX]MpMjes: WARNING: 10138: Failed to load the audit log library.

[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.

[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

[UNIX]MpMjes: WARNING: 10139: Failed to read the audit log file.

[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.

[UNIX]MpMjes: ERROR: 10140: Failed to allocate memory.

[Description]

Memory allocation failed during initialization processing.

[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.

[UNIX]MpMjes: ERROR: 10141: failed in allocate of the memory.

[Description]

Failed to allocate memory while retrieving a state of network job.

[System Action]

Aborts the process.

[User Response]

Wait a short time and try again.

[System Administrator Response]

Increase the physical memory or tune swap settings.

[UNIX]MpMjes: ERROR: 10142: Process Information File open error occurred. Failed in the injection of the job.

[Description]

The network job submission process failed to open the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10143: Process Information File read error occurred. Failed in the injection of the job.

[Description]

The network job submission process failed to read the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10144: Process Information File write error occurred. Failed in the injection of the job.

[Description]

The network job submission process failed to write to the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10145: Process Information File close error occurred. Failed in the injection of the job.

[Description]

The network job submission process failed to close the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10146: Process Information File open error occurred. Job is carrying it out.

[Description]

The network job termination process failed to open the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10147: Process Information File read error occurred. Job is carrying it out.

[Description]

The network job termination process failed to read the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10148: Process Information File write error occurred. Job is carrying it out.

[Description]

The network job termination process failed to write to the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10149: Process Information File close error occurred. Job is carrying it out.

[Description]

The network job termination process failed to close the process status management file that is used to manage the network job status on the execution server.

[System Action]

Aborts the process.

[Corrective Measures]

The process status management file may not exist or it may be corrupted.

Collect information for "Job Execution Control" by using the Maintenance Information Collection Tool, and then contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10150: The license key was not registered or the trial time limit passed. Please register the license key if you continue to use this product.

[Description]

The license key is not registered, or the trial period has expired.

[System Action]

Outputs the message and cancels the processing.

[System Administrator Response]

A license is required. Refer to "Relese Note" for information on corrective measures.

[UNIX]MpMjes: INFO: 10151: This product operates as a trial period. The remainder trial period is XXXX days.

[Description]

This product is a trial version, and the remaining trial period is XXXX.

[Parameter]

XXXX: Remaining trial period

[System Action]

Maintains the operation.

[System Administrator Response]

Purchase the product to continue using it after the trial period has expired.

[UNIX]MpMjes: WARNING: 10154: The format of the execution subsystem name definition file is invalid. Row No.=<row>

[Description]

The execution subsystem name definition file contains a row with an invalid format.

[Parameter]

row: Row number that encountered an error in the execution subsystem name definition file.

[System Action]

Ignores the invalid row and continues the startup process for the Job Execution Control daemon.

[System Administrator Response]

Correct the invalid row and restart the Job Execution Control daemon.

[UNIX]MpMjes: WARNING: 10155: The number of definitions in the execution subsystem name definition file exceeds 100.

[Description]

The number of execution subsystem name definitions in the execution subsystem name definition file exceeds 100.

[System Action]

Ignores definitions after the first 100 and continues the startup process for the Job Execution Control daemon.

[System Administrator Response]

Delete definitions after the first 100 from the execution subsystem name definition file.

[UNIX]MpMjes: ERROR: 10156: An error occurred while reading the execution subsystem name definition file. Code=<code>

[Description]

An error occurred while the execution subsystem name definition file was being opened or loaded.

[Parameter]

code: Operating system error code

[System Action]

Stops the Job Execution Control daemon.

[System Administrator Response]

Eliminate the cause of the problem based on the error code generated by the operating system.

If the problem persists, use the Maintenance Information Collection Tool to collect information for Job Execution Control and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10157: An error occurred when writing the execution subsystem name management file. Code=<code>

[Description]

An error occurred while the file that manages execution subsystem names was being opened or written to.

[Parameter]

code: Operating system error code

[System Action]

Stops the Job Execution Control daemon.

[System Administrator Response]

Check if the file system is depleted or an error has occurred. In such a case, eliminate the cause of the error from the file system. The file system to be checked is located in /var/spool/mjes. For a symbolic link, check the actual file in the link destination.

If the problem persists, use the Maintenance Information Collection Tool to collect information for Job Execution Control and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10158: Failed to initialize the working directory.

[Description]

Failed to create the working directory.

[System Action]

Stops the Job Execution Control daemon.

[Cause]

The cause regarding the /var/opt/FJSVMJS/ directory can be attributed to the following:

  • There is not enough space on the disk

[System Administrator Response]

Remove the error cause and start Job Execution Control.

If the problem persists, use the Maintenance Information Collection Tool to collect information for Job Execution Control and contact a Fujitsu technical support.

[UNIX]MpMjes: ERROR: 10159: The job <jobname> was not canceled by Execution Server <hostname>.

[Description]

The job was not canceled by the execution server.

[Parameter]

jobname: Job name

hostname: Execution server name

[User Response]

Check the status of the applicable job by executing the qjstat command on the execution server, and then cancel the job by executing the qdel command. Note the following points when checking the job on the execution server.

  • If running multi-subsystem operation, be careful to use the correct subsystem number.

  • If multiple jobs with the same name exist, be careful to stop the correct job.

  • At the end of the job name, "_" is appended.

[System Administrator Response]

Port jmnet communication from the submitting server to the execution server has been interrupted or temporarily unavailable, preventing normal communication. Take the required actions to fix the communication issue.