Job Management Partner 1/Integrated Management - Manager Messages
- Note:
- Messages with message IDs such as internal error messages may be output in addition to the messages shown in the message list.
- Messages related to process management may be output from JP1/Base or JP1/AJS (if installed) on the same host. For more information about messages output by JP1/Base and JP1/AJS, see the manual Job Management Partner 1/Base User's Guide.
An attempt to open the message file has failed.
An attempt to open the message file failed.
- S:
- Terminates process management.
- O:
- In Windows:
- Use the data collection tool to collect data, and then contact a system administrator.
- In UNIX:
- The possible causes are as follows. Check the environment.
- There may be no read permission for files in the /opt/jp1base/lib/nls directory. Assign read permission.
- The maximum number of files that can be opened in the system may have been reached. Review the kernel parameter.
- There may be a temporary memory shortage. Retry the operation. Also stop unnecessary processes.
- A directory or file may have been deleted. Re-install JP1/IM - Manager.
- If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
An attempt to read the message file has failed.
An attempt to read the message file failed.
- S:
- Does not output the message.
- O:
- Make sure that JP1/Base setup was completed normally.
An attempt to read the message file has failed.
An attempt to read the message file failed.
- S:
- Does not output the message.
- O:
- Make sure that the message file (jbsspm.cat) exists in the /opt/jp1base/lib/nls directory and that the access permission is appropriate.
An error occurred in internal processing to output a message.
An error occurred during internal processing to output a message.
- S:
- Does not output the message.
- O:
- Make sure that sufficient system resources are allocated.
An attempt to start the process management has failed. (errno = request-code)
An attempt to start process management failed.
- S:
- Terminates process management.
- O:
- Make sure that the product is correctly installed.
component-name managed-process-name has timed out.
The request timed out. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
- O:
- For a reload request, increase the time-out value, and then retry the operation. For other requests, wait awhile, and then retry the request. If the same message is displayed after re-execution, use the data collection tool to collect data, and then contact a system administrator.
SIGKILL was sent to managed-process-name of component-name, but termination could not be detected.
SIGKILL was sent to the managed process, but termination could not be detected. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Terminates process management.
- O:
- Determine whether managed-process-name stopped. If managed-process-name did not stop, manually stop it.
A component-name reload request has finished.
A reload request was completed. component-name is JP1_CONS.
- S:
- Continues processing.
jxx_spmd: component-name will now start all inactive processes.
All inactive managed processes will be started. jxx is jco. component-name is JP1_CONS.
- S:
- Continues processing.
jxx_spmd_reload: A reload request will now be sent to all running processes of component-name.
A reload request will be sent to all running managed processes. jxx is jco. component-name is JP1_CONS.
- S:
- Continues processing.
jxx_spmd_stop: A stop request will now be sent to all processes of component-name
A stop request will be sent to all managed processes. jxx is jco. component-name is JP1_CONS.
- S:
- Continues processing.
component-name has ended.
Terminates process management. component-name is JP1_CONS.
- S:
- Terminates process management.
component-name has terminated.
Terminates process management. component-name is JP1_CONS.
- S:
- Terminates process management.
jxx_spmd_stop -kill: A forced stop (kill) will be performed on all processes of component-name.
A forced stop will be performed on all managed processes. jxx is jco. component-name is JP1_CONS.
- S:
- Continues processing.
main_loop: An invalid request was received for Service Control Manager. (event ID = request-type)
An invalid request was received.
- S:
- Continues processing.
- O:
- Use the data collection tool to collect data, and then contact a system administrator.
component-name received a startup report from managed-process-name.
A startup report was received. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
All processes of component-name are running.
All managed processes are running. component-name is JP1_CONS.
- S:
- Continues processing.
component-name startup has finished.
Service startup was completed. component-name is JP1_CONS.
- S:
- Continues processing.
component-name completed to send the start up request to the managed-process-name.
Restart of the managed process that ended abnormally was completed. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
component-name received a reload-completed notification from managed-process-name.
A reload-completed notification was received from a managed process. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
A component-name reload request has finished.
Reload processing for a managed process was completed. component-name is JP1_CONS.
- S:
- Continues processing.
component-name received an termination notification from managed-process-name.
Termination notification was received from a managed process. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
A stop request will now be sent to all processes of component-name.
A stop request will be sent to all managed processes. component-name is JP1_CONS.
- S:
- Continues processing.
A component-name timeout occurred in managed-process-name. Processing continues.
A startup time-out occurred in a managed process. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
- O:
- Wait awhile to see if startup of the managed process finishes and the service starts. If it does not, execute the jxx_spmd_stop -kill command to perform a forced stop, and then restart the process.
Process management will now stop because an invalid component-name status occurred.
Process management will stop due to an invalid status. component-name is JP1_CONS.
- S:
- Terminates process management.
- O:
- Use the data collection tool to collect data, and then contact a system administrator.
Restart of the component-name managed-process-name has finished.
Restart of the managed process that ended abnormally was completed. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
The user does not have permission to execute the command execution-command-name.
The user executing the command does not have Administrator permissions.
- S:
- Does not execute the command.
- O:
- Execute the command as a user with Administrator permissions.
A fork system call failed during initialization: component-name
An attempt to perform a fork system call to be executed in the background failed during startup of process management. component-name is JP1_CONS.
- S:
- Terminates process management.
- O:
- Make sure that sufficient system memory has been allocated. Also make sure that the OS is operating normally.
The setsid function failed. (error-explanation)
A setsid system call failed.
- S:
- Terminates process management.
- O:
- Make sure that sufficient system memory has been allocated. Also make sure that the OS is operating normally.
An attempt to create a process management table has failed.
An attempt to create a process management table failed.
- S:
- Terminates the process management command.
- O:
- Make sure that sufficient system memory is allocated, that the product is correctly installed, and that the settings in the extended startup process definition file (jp1co_service.conf) are specified correctly. Also determine whether any processes managed by process management remain after ending abnormally.
- Delete the extended startup process definition file, and then restart process management.
An internal error occurred. Execution Command names differ. execution-command-name
The execution command names do not match.
- S:
- Terminates process management.
- O:
- Check execution-command-name. The command no longer operates if execution-command-name is changed.
An attempt to create a lock file has failed. path-to-lock-file - error-explanation
An attempt to create a lock file failed.
- S:
- Terminates the process management command.
- O:
- Make sure that the conf directory exists and that there is read and write permission for it. If operating in a cluster environment, make sure that the defined conf directory exists and that there is read and write permission for it.
component-name is already running.
The service was started twice. component-name is JP1_CONS.
- S:
- Terminates the process management command.
build_proc_table : The return value NULL was returned to the getfield function. setting
Entries in the extended startup process definition file (jp1co_service.conf) are not specified correctly.
- S:
- Terminates process management.
- O:
- Make sure that the entries in the extended startup process definition file are specified correctly.
An internal error occurred. Component names differ. component-name
The component names do not match. component-name is JP1_CONS.
- S:
- Terminates process management.
- O:
- Use the data collection tool to collect data, and then contact a system administrator.
An attempt to open the environment definition file file-name has failed.
An attempt to open the environment definition file failed.
- S:
- Terminates process management.
- O:
- Make sure that the product is correctly installed.
An attempt to expand the environment variables has failed.
An attempt to read the environment variable from jxx_spmd_env.conf failed. jxx is jco.
- S:
- Terminates process management.
- O:
- Make sure that sufficient system memory is allocated.
The logical hostname for process management is logical-host-name.
Process management starts on a logical host.
- S:
- Continues processing.
The option-name option is specified.
Process management starts with an option.
- S:
- Continues processing.
The expiration of the time limit. product-name
The expiration date was reached.
- S:
- Suspends processing.
The environment variable of JP1_HOSTNAME is empty.
The setting of the JP1_HOSTNAME environment variable is incorrect.
- S:
- Terminates the process management command.
- O:
- Specify the correct logical host name for the JP1_HOSTNAME environment variable, or delete the JP1_HOSTNAME environment variable.
Startup processing for component-name has started.
Process management will start a managed process. component-name is JP1_CONS.
- S:
- Process management will start the managed process.
A timeout occurred during the wait for a response. (timeout period = time-out-seconds seconds)
A time-out occurred while waiting for a response.
- S:
- Terminates the process management command.
- O:
- Change the time-out value, and then retry the operation.
An attempt to send a request to the process management has failed.
An attempt by the process management command to communicate with process management failed.
- S:
- Terminates the process management command.
- O:
- Make sure that the /var/opt/jp1base/tmp directory exists.
An attempt to receive a response from the process management has failed.
An attempt by the process management command to receive data from process management failed.
- S:
- Terminates the process management command.
- O:
- Restart process management, and then retry the operation.
Invalid data was received from process management.
The process management command received invalid data from process management.
- S:
- Terminates the process management command.
- O:
- Invalid data may have been received temporarily. Restart process management, and then retry the operation.
The startup command terminated normally.
The process management startup command ended normally.
- S:
- Terminates the process management command.
The startup command terminated abnormally
The startup command ended abnormally.
- S:
- Terminates the process management command.
- O:
- Execute the jxx_spmd_status command to check the status, and then retry the operation. jxx is jco.
The startup command terminated abnormally due to an inconsistent state.
This message is output when the command is executed while process management is performing other processing.
- S:
- Terminates the process management command.
- O:
- Wait awhile, execute the jxx_spmd_status command to check the status, and then retry the operation. jxx is jco.
There were no processes that could run.
No processes can be run.
- S:
- Terminates the process management command.
Invalid data was received.
The process management command received invalid data from process management.
- S:
- Terminates the process management command.
- O:
- Invalid data may have been received temporarily. Restart process management, and then retry the operation.
An unexpected result code was received. (Return code: return-code)
The process management command received an inappropriate result code from process management.
- S:
- Terminates the process management command.
- O:
- Execute the jxx_spmd_status command to check the status, and then retry the operation. jxx is jco.
The process management is not running.
Process management stopped.
- S:
- Terminates the process management command.
Execute the command from the administrator console.
This command must be executed from the administrator console.
- S:
- Terminates command processing.
- O:
- Re-execute the command from the administrator console.
A forced termination (kill) of component-name has started.
Forced termination processing of process management will start. component-name is JP1_CONS.
- S:
- Terminates the process management command.
Termination processing of component-name has started.
Termination processing of process management will start. component-name is JP1_CONS.
- S:
- Terminates the process management command.
The stop command terminated normally.
The stop command of process management ended normally.
- S:
- Terminates the process management command.
The stop command terminated abnormally.
The stop command ended abnormally.
- S:
- Terminates the process management command.
- O:
- Wait awhile, execute the jxx_spmd_status command to check the status, and then retry the operation. jxx is jco.
The stop command terminated abnormally due to an inconsistent state.
The command was executed while process management was performing other processing.
- S:
- Terminates the process management command.
- O:
- Wait awhile, and then retry the operation.
There were no processes that could terminate.
No processes can be terminated.
- S:
- Terminates the process management command.
Reload processing for component-name has started.
Reload processing for a process being managed by process management will start. component-name is JP1_CONS.
- S:
- Terminates the process management command.
The reload command terminated normally.
The reload command of process management ended normally.
- S:
- Terminates the process management command.
The reload command terminated abnormally.
The reload command ended abnormally.
- S:
- Terminates the process management command.
- O:
- Determine whether any managed processes failed during reload processing.
The reload command terminated abnormally due to an inconsistent state.
The command was executed while process management was performing other processing.
- S:
- Terminates the process management command.
- O:
- Wait awhile, and then retry the operation.
There were no processes that could be reloaded.
No processes can be reloaded.
- S:
- Terminates the process management command.
- O:
- Determine whether managed processes are running.
A timeout occurred in process-name.
Reload processing of the process indicated by process-name timed out.
- S:
- Terminates the process management command.
- O:
- Determine whether any managed processes failed during reload processing.
Processing to report the status of component-name has started.
Processing to report process management status will start. component-name is JP1_CONS.
- S:
- Terminates the process management command.
All the processes have started.
All managed processes have started.
- S:
- Terminates the process management command.
Some of the processes have started.
Some managed processes have started.
- S:
- Terminates the process management command.
All of the processes have stopped.
All managed processes have stopped.
- S:
- Terminates the process management command.
Part of the process is now restarting.
Part of process management is restarting.
- S:
- Terminates the status notification command of process management.
managed-process-name is now starting. (process ID = process-ID)
The managed process is starting. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the managed process being started.
- S:
- Continues processing.
component-name detected the termination of managed-process-name. (process ID = process-ID)
Termination of the managed process was detected. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the managed process being started.
- S:
- Continues processing.
All processes of component-name have stopped.
All managed processes have stopped. component-name is JP1_CONS.
- S:
- Terminates process management.
The component-name managed-process-name terminated abnormally.
Abnormal termination of the managed process was detected. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
- O:
- Refer to the integrated trace log output by the managed process that stopped abnormally, and remove the cause of the problem. Execute the jxx_spmd_status command to check the status, and then restart process management. jxx is jco. If there is no message output by the managed process, use the data collection tool to collect data, and then contact a system administrator.
component-name has terminated.
Terminates process management. component-name is JP1_CONS.
- S:
- Terminates process management.
component-name startup has finished.
Startup of the service was completed. component-name is JP1_CONS.
- S:
- Continues processing.
The component-name startup request has finished.
The startup request was completed. component-name is JP1_CONS.
- S:
- Continues processing.
An attempt to start managed-process-name has finished. (return code = return-code, detail code = request-code)
An attempt to start the managed process failed. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
- O:
- Use the data collection tool to collect data, and then contact a system administrator.
The changes to file-name were not applied.
The changes to the settings in the extended startup process definition file (jp1co_service.conf) were not accepted.
- S:
- Continues processing.
- O:
- Revise the settings, and then retry the operation.
In the file file-name, the restart-or-not value is invalid. ( restart-or-not = setting)
The restart-or-not value specified in the extended startup process definition file (jp1co_service.conf) is invalid.
- S:
- Continues processing.
- O:
- Revise the setting, and then retry the operation.
Set 0 or 1 for the restart-or-not value.
Specify 0 or 1 for the restart-or-not value set in the extended startup process definition file (jp1co_service.conf).
- S:
- Continues processing.
- O:
- Specify 0 or 1 for the restart-or-not value.
In the file file-name, the number-of-restarts value is invalid. (restart num. = setting)
The number-of-restarts value specified in the extended startup process definition file (jp1co_service.conf) is invalid.
- S:
- Continues processing.
- O:
- Revise the setting, and then retry the operation.
Set 0 to 99 for the number-of-restarts value.
Specify a value between 0 and 99 for the number-of-restarts value set in the extended startup process definition file (jp1co_service.conf).
- S:
- Continues processing.
- O:
- Specify a value between 0 and 99 for the number-of-restarts value.
In the file file-name, the restart interval value is invalid. (restart interval = setting)
The restart interval value specified in the extended startup process definition file (jp1co_service.conf) is invalid.
- S:
- Continues processing.
- O:
- Revise the setting, and then retry the operation.
Set 0 to 3600 for the restart interval value.
Specify a value between 0 and 3,600 for the restart interval value set in the extended startup process definition file (jp1co_service.conf).
- S:
- Continues processing.
- O:
- Specify a value between 0 and 3,600 for the restart interval value.
In the file file-name, the restart-count reset time is invalid. (restart-count reset time = setting)
The restart-count reset time specified in the extended startup process definition file (jp1co_service.conf) is invalid.
- S:
- Continues processing.
- O:
- Revise the setting, and then retry the operation.
Set 3600 to 2147483647 for the restart-count reset time.
Specify a value between 3,600 and 2,147,483,647 for the restart-count reset time set in the extended startup process definition file (jp1co_service.conf).
- S:
- Continues processing.
- O:
- Specify a value between 3,600 and 2,147,483,647 for the restart-count reset time.
In file-name, check the entries: process-name|path|startup-option|restart-or-not|number-of-restarts|restart-interval|restart-count-reset-time|
Check the entries in the extended startup process definition file (jp1co_service.conf).
- S:
- Continues processing.
- O:
- Check the entries in the extended startup process definition file.
component-name: The stopped managed-process-name will be restarted. (restart count = restart-count)
The stopped managed-process-name will be restarted. component-name is JP1_CONS. The managed process name is the process name that constitutes each component managed by process management.
- S:
- Restarts the managed process.
component-name: A startup request was sent to the process managed-process-name.
A startup request was sent to the managed process. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
component-name: An attempt to send a startup request to the process managed-process-name failed.
An attempt to send a startup request to a managed process failed. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
To process child-process-ID-of-managed-process, the system sent the signal signal-name.
The signal is sent to the child process of the managed process. child-process-ID-of-managed-process is the process ID of the process generated by the running managed process.
- S:
- Continues processing.
component-name: The number of restarts of managed-process-name exceeded the specified restart count.
The number of restarts of the managed process exceeded the specified value. component-name is JP1_CONS. managed-process-name is the name of the process that constitutes each component managed by process management.
- S:
- Continues processing.
- O:
- Refer to the integrated trace log output by the managed process that stopped abnormally, and remove the cause of the problem. Execute the jxx_spmd_status command to check the status, and then restart process management. jxx is jco. If there is no message output by the managed process, use the data collection tool to collect data, and then contact a system administrator.
The process manager will not be monitored because an attempt to initialize the health check function failed.
Process management will not be monitored because initialization of the health check function failed.
- S:
- Continues processing.
- O:
- To use the health check function to monitor process management, restart process management.
A system error occurred during startup of product-name.
A system error occurred during startup of product-name.
- S:
- Suspends processing.
- O:
- Use the data collection tool to collect data, and then contact a system administrator.
The product information could not be acquired because there was not enough memory. (Detailed information: function-name, return-value)
Acquisition of product information failed due to insufficient resources.
- S:
- Suspends processing.
- O:
- Make sure that sufficient system resources are allocated.
- Resolve the resource insufficiency, and then retry the operation.
- If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
The product information could not be acquired because the environment is invalid. (Detailed information: function-name, return-value)
An attempt to acquire product information failed due to an invalid environment.
- S:
- Suspends processing.
- O:
- Determine whether a system error occurred.
- Uninstall the program, re-install it, and then retry the operation.
- If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
component-name completed the reload request.
Reload processing was completed. component-name is JP1_CONS.
- S:
- Continues processing.
The process managed-process-name will be terminated by SIGKILL. (process ID = process-ID)
SIGKILL was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the running managed process.
- S:
- Continues processing.
component-name: No processes could be started.
No managed processes could be started. component-name is JP1_CONS.
- S:
- Terminates process management.
- O:
- Make sure that sufficient system memory is allocated. Also make sure that the product is correctly installed.
component-name: No processes can be reloaded.
No managed processes were ready to be reloaded. component-name is JP1_CONS.
- S:
- Continues processing.
- O:
- Wait awhile, and then retry the operation.
The conf directory path cannot be obtained from the common definition.
The conf directory path could not be obtained from the common definition.
- S:
- Terminates the process management command.
- O:
- The common definition information has not been specified. Make sure that the settings are correct.
- If operating in a cluster environment
- Make sure that the logical host of the argument specified by the process management command is correct. Also make sure that the logical host specified by the JP1_HOSTNAME environment variable is correct.
- If not operating in a cluster environment
- Determine whether the JP1_HOSTNAME environment variable was specified and the process is running. If the JP1_HOSTNAME environment variable was not specified, perform the following operation to recover from the error.
- In Windows:
Perform overwrite installation.
- In UNIX:
Execute the jp1cc_setup or jp1cs_setup command.
The conf directory path cannot be obtained by using the specified logical hostname.
The conf directory path could not be obtained from the common definition using the specified logical host name.
- S:
- Terminates the process management command.
- O:
- Use of a cluster system is a precondition. Make sure that the specified logical host name is correct and that setup was completed normally.
The log directory path cannot be obtained from the common definition information.
The log directory path could not be obtained from the common definition.
- S:
- Terminates the process management command.
- O:
- If operating in a cluster environment, make sure that the logical host name setting is correct and that setup was completed normally. If not operating in a cluster environment, perform the following operation to recover from the error.
- In Windows:
- Perform corrective installation.
- In UNIX:
- Execute the setup command.
The log directory path cannot be obtained by using the specified logical hostname.
The log directory path could not be obtained from the common definition using the specified logical host name.
- S:
- Terminates the process management command.
- O:
- Use of a cluster system is a precondition. Make sure that the specified logical host name is correct and that setup was completed normally.
HNTRLib could not be initialized.
HNTRLib2 could not be initialized. A log is not output.
- S:
- Continues processing.
- O:
- If process management is running, stop process management, and then restart it.
HNTRLib could not be initialized.
HNTRLib2 could not be initialized. A log is not output.
- S:
- Continues processing.
- O:
- If process management is running, stop process management, and then restart it.
The work directory path cannot be acquired from the common definition information. (Return code: return-code)
The work directory path could not be acquired from the common definition.
- S:
- Terminates the process management command.
- O:
- If operating in a cluster environment, make sure that the logical host name setting is correct and that setup was completed normally. If not operating in a cluster environment, perform the following operation to recover from the error.
- In Windows:
- Perform corrective installation.
- In UNIX:
- Execute the setup command.
A stop request was sent to the process managed-process-name. (process ID = process-ID)
A stop request was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the running managed process.
- S:
- Continues processing.
A reload request was sent to the process managed-process-name. (process ID = process-ID)
A reload request was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. The process ID is process-ID of the running managed process.
- S:
- Continues processing.
SIGTERM will terminate the process managed-process-name. (process ID = process-ID)
SIGTERM was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. The process ID is process-ID of the running managed process.
- S:
- Continues processing.
The process management daemon is busy.
The command is being processed.
- S:
- Terminates the process management command.
- O:
- Wait awhile, and then retry the operation. If this message is output when the jxx_spmd, jxx_spmd_stop, or jxx_spmd_reload command was executed during startup, stop, or reload processing, wait until processing finishes, and then retry the operation. jxx is jco.
The process is running.
- S:
- Terminates the process management command.
The process is not running.
- S:
- Terminates the process management command.
An attempt to open the lock file under the conf directory has failed.
The lock file of the conf directory could not be opened.
- S:
- Terminates the process management command.
- O:
- Make sure that the conf directory exists and that there is write permission for it.
- If operating in a cluster environment, make sure that the defined conf directory exists and that there is write permission for it.
create_pre_process_entry: Memory allocation failed. (request-code)
An attempt to create a startup preprocessing management table failed. Startup preprocessing is not performed.
- S:
- Continues processing.
- O:
- Determine whether a memory shortage occurred.
Startup preprocessing is being performed.
Process management is performing startup preprocessing.
- S:
- Terminates the process management status notification command.
The request could not be accepted because startup preprocessing is being performed.
Process management could not accept a command request because process management is performing startup preprocessing.
- S:
- Terminates the process management command.
- O:
- Wait awhile, and then retry the operation.
jxx_spmd_stop -job: A request to stop job restrictions will be sent to all processes of component-name.
A request to stop job restrictions will be sent to all managed processes. jxx is jco. component-name is JP1_CONS.
- S:
- Continues processing.
A request to stop job restrictions has been sent to the process managed-process-name. (process ID = process-ID)
A request to stop job restrictions was sent to the managed process. managed-process-name is the name of the process that constitutes each component managed by process management. process-ID is the process ID of the running managed process.
- S:
- Continues processing.
Processing to stop component-name job restrictions has started.
Processing to stop job restrictions of process management will start. component-name is JP1_CONS.
- S:
- Terminates the process management command.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.