9.3.4 Messages related to process management (KAVB3501 to KAVB3999)
- Notes:
-
-
In addition to the messages listed here, other messages with message IDs (such as internal error messages) might also be displayed.
-
Messages related to process management might also be output by other programs, such as JP1/Base and JP1/IM - Manager (if installed). For details about messages output by programs other than JP1/IM - EG for NNMi, see the appropriate documentation for the specific products.
-
-
KAVB3501-E
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 the system administrator.
- In UNIX:
-
Possible causes are listed below. Check the environment.
-
The user might not have read permissions for the files under /opt/jp1eg4nnmi/lib/nls. Grant read permissions.
-
The number of open files might have reached the maximum permitted in the system. Check and revise (if necessary) the kernel parameter.
-
A temporary memory shortage might have occurred. Re-execute the command. Also terminate any unneeded process.
-
The directory or file might have been deleted. Re-install it.
If the problem cannot be resolved, use the data collection tool to collect data and then contact the system administrator.
-
-
KAVB3502-E
An attempt to read the message file has failed.
An attempt to read the message file has failed.
- S:
-
Does not output messages.
- O:
-
Check if JP1/Base was set up successfully.
-
KAVB3503-E
An attempt to read the message file has failed.
An attempt to read the message file has failed.
- S:
-
Does not output messages.
- O:
-
Check if there is a message file (jegnspm.cat) under the /opt/jp1eg4nnmi/lib/nls directory and whether the reference permissions are appropriate.
-
KAVB3504-E
An error occurred in internal processing to output a message.
An error occurred during internal processing for message output.
- S:
-
Does not output messages.
- O:
-
Check for a shortage of system resources.
-
KAVB3516-E
An attempt to start the process management has failed. (errno = request-code)
An attempt to start process management failed.
- S:
-
Terminates process management.
- O:
-
Check if the product has been installed correctly.
-
KAVB3552-E
component-name name-of-managed-process has timed out.
The request resulted in a timeout. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
- O:
-
In the case of the reload request, check integrated trace logs to see if there are any log entries for errors in definition files. If you find an error, correct the error in the relevant definition file and then execute the jegn_spmd_reload command.
If no error on definition files is found, increase the timeout value and then re-execute the command.
Otherwise, wait a while and then re-execute the request.
If the same event occurs after re-execution, collect the required data using the data collection tool and contact the system administrator.
-
KAVB3553-E
SIGKILL was sent to name-of-managed-process of component-name, but termination could not be detected.
After sending SIGKILL, the system was unable to determine whether termination occurred. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Terminates process management.
- O:
-
Make sure that the indicated process is not running. If this process is running, terminate it manually.
-
KAVB3554-I
A component-name reload request has finished.
A reload request has been completed. component-name is JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3564-I
jegn_spmd: component-name will now start all inactive processes.
All managed processes that are currently inactive will be started. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3574-I
jegn_spmd_reload: A reload request will now be sent to all running processes of component-name.
The system will send a reload request to all managed processes that are active. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3577-I
jegn_spmd_stop: A stop request will now be sent to all processes of component-name.
The system will send a stop request to all managed processes. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3578-I
component-name has ended.
Process management is being terminated. component-name indicates JP1_EGN.
- S:
-
Terminates process management.
-
KAVB3586-I
component-name has terminated.
Process management has terminated. component-name indicates JP1_EGN.
- S:
-
Terminates process management.
-
KAVB3597-I
jegn_spmd_stop -kill: A forced stop (kill) will be performed on all processes of component-name.
All managed processes are being terminated forcibly. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3599-E
main_loop: An invalid request was received for Service Control Manager. (event ID = request-type)
An invalid request was received.
- S:
-
Resumes processing.
- O:
-
Use the data collection tool to collect data and then contact the system administrator.
-
KAVB3602-I
component-name received a startup report from name-of-managed-process.
A startup completion notification has been received. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
-
KAVB3603-I
All processes of component-name are running.
All managed processes have started. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3604-I
component-name startup has finished.
Service startup processing has been completed. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3605-I
component-name completed to send the start up request to the name-of-managed-process.
Startup processing for the indicated managed process, which terminated abnormally, has been completed. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
-
KAVB3608-I
component-name received a reload-completed notification from name-of-managed-process.
A reload completion notification was received from the indicated managed process. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
-
KAVB3609-I
A component-name reload request has finished.
Reload processing has been completed for all managed processes. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3610-I
component-name received an termination notification from name-of-managed-process.
A termination notification was received from the indicated managed process. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
-
KAVB3612-I
A stop request will now be sent to all processes of component-name.
A termination request is being sent to all managed processes. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3613-W
A component-name timeout occurred in name-of-managed-process. Processing continues.
Startup processing for the indicated managed process resulted in a timeout. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
- O:
-
Wait a while. If the service does not start because startup processing for the managed process still isn't completed, use the jegn_spmd_stop -kill command to restart the service.
-
KAVB3614-E
Process management will now stop because an invalid component-name status occurred.
Process management is being terminated because of an invalid status. component-name indicates JP1_EGN.
- S:
-
Terminates command processing.
- O:
-
Use the data collection tool to collect data and then contact the system administrator.
-
KAVB3616-I
Restart of the component-name name-of-managed-process has finished.
Restart has been completed for the indicated managed process, which had terminated abnormally. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
-
KAVB3620-E
The user does not have permission to execute the command execution-command-name.
The user who attempted to execute the command does not have Administrator permissions.
- S:
-
Does not execute the command.
- O:
-
Have a user with Administrator permissions execute the command.
-
KAVB3621-E
A fork system call failed during initialization: component-name
A fork system call for background execution failed during process management startup processing. component-name indicates JP1_EGN.
- S:
-
Terminates command processing.
- O:
-
Make sure that there is sufficient system memory. Also check that the OS is running normally.
-
KAVB3623-E
The setsid function failed. (description-of-error)
A setsid system call failed.
- S:
-
Terminates command processing.
- O:
-
Make sure that there is sufficient system memory. Also check that the OS is running normally.
-
KAVB3624-E
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 there is sufficient system memory and check that the product has been installed correctly. Make sure that the settings are correct in the extended startup process definition file (jegn_service_0700.conf). Also make sure that processes managed by process management have terminated normally.
Delete the extended startup process definition file and then start process management.
-
KAVB3625-E
An internal error occurred. Execution Command names differ. execution-command-name
The execution command names do not match.
- S:
-
Terminates command processing.
- O:
-
Check the command name indicated as execution-command-name. If you have changed the command name (execution-command-name), the command will no longer function.
-
KAVB3626-E
An attempt to create a lock file has failed. lock-file-path-description-of-error
An attempt to create a lock file has failed.
- S:
-
Terminates the process management command.
- O:
-
Check that the conf directory exists and that you have read and write permissions. In the case of operation in a cluster system, make sure that the defined conf directory exists and that the read and write permissions have been granted.
-
KAVB3627-I
component-name is already running.
An attempt was made to start the same service more than once concurrently. component-name indicates JP1_EGN.
- S:
-
Terminates the process management command.
-
KAVB3631-E
build_proc_table : The return value NULL was returned to the getfield function. setting
The extended startup process definition file (jeng_service_0700.conf) contains an invalid entry.
- S:
-
Terminates command processing.
- O:
-
Make sure that the entries in the extended startup process definition file are correct.
-
KAVB3642-E
An internal error occurred. Component names differ. component-name
The component names do not match. component-name indicates JP1_EGN.
- S:
-
Terminates command processing.
- O:
-
Use the data collection tool to collect data and then contact the system administrator.
-
KAVB3643-E
An attempt to open the environment definition file file-name has failed.
An attempt to open the environment definition file failed.
- S:
-
Terminates command processing.
- O:
-
Check that the product has been installed correctly.
-
KAVB3644-E
An attempt to expand the environment variables has failed.
An attempt to load environment variables from jegn_spmd_env.conf failed.
- S:
-
Terminates command processing.
- O:
-
Make sure that the system has sufficient memory.
-
KAVB3645-I
The logical hostname for process management is logical-host-name.
Process management is starting on the logical host.
- S:
-
Resumes processing.
-
KAVB3646-I
The option-name option is specified.
Process management is starting with an option in effect.
- S:
-
Resumes processing.
-
KAVB3647-E
The expiration of the time limit. JP1/IM-EG for NNMi
The evaluation version has expired.
- S:
-
Cancels processing.
-
KAVB3649-E
The environment variable of JP1_HOSTNAME is empty.
Specification of the JP1_HOSTNAME environment variable is invalid.
- S:
-
Terminates the process management command.
- O:
-
Either specify the correct logical host name in the JP1_HOSTNAME environment variable or delete the JP1_HOSTNAME environment variable.
-
KAVB3651-I
Startup processing for component-name has started.
Process management is starting a managed process. component-name indicates JP1_EGN.
- S:
-
Process management starts the managed process.
-
KAVB3652-E
A timeout occurred during the wait for a response. (timeout period = timeout-value seconds)
A timeout occurred while the system was waiting for a response.
- S:
-
Terminates the process management command.
- O:
-
Change the timeout value and then re-execute the command.
-
KAVB3653-E
An attempt to send a request to the process management has failed.
Communication with process management from a process management command has failed.
- S:
-
Terminates the process management command.
- O:
-
Make sure that the /var/opt/jp1eg4nnmi/tmp directory exits.
-
KAVB3654-E
An attempt to receive a response from the process management has failed.
Data reception processing from process management to a process management command has failed.
- S:
-
Terminates the process management command.
- O:
-
Restart process management and then re-execute the command.
-
KAVB3655-E
Invalid data was received from the process management.
A process management command received invalid data from process management.
- S:
-
Terminates the process management command.
- O:
-
Invalid data might have been received temporarily. Restart process management and then re-execute the command.
-
KAVB3656-I
The startup command terminated normally.
The process management startup command terminated normally.
- S:
-
Terminates the process management command.
-
KAVB3657-E
The startup command terminated abnormally
The startup command terminated abnormally.
- S:
-
Terminates the process management command.
- O:
-
Use the jegn_spmd_status command to check the status and then re-execute the command.
-
KAVB3658-E
The startup command terminated abnormally due to an inconsistent state.
A command is executed while process management was performing other processing.
- S:
-
Terminates the process management command.
- O:
-
Wait a while, use the jegn_spmd_status command to check the status, and then re-execute the command.
-
KAVB3659-I
There were no processes that could run.
There is no process that can be started.
- S:
-
Terminates the process management command.
-
KAVB3660-E
Invalid data was received.
The process management command received invalid data from process management.
- S:
-
Terminates the process management command.
- O:
-
Invalid data might have been received temporarily. Restart process management and then re-execute the command.
-
KAVB3661-E
An unexpected result code was received. (return code = return-code)
The process management command received an invalid result code from process management.
- S:
-
Terminates the process management command.
- O:
-
Use the jegn_spmd_status command to check the status, and then re-execute the command.
-
KAVB3662-I
The process management is not running.
Process management is not running.
- S:
-
Terminates the process management command.
- O:
-
-
When the jegn_start command was executed
Either setup has not been executed or a definition might be invalid in the NNMi incident forwarding filter definition file.
Check the integrated trace log, take appropriate action according to the displayed messages, and then re-execute the command.
-
-
KAVB3663-E
Execute the command from the administrator console.
This command must be executed at the administrator console.
- S:
-
Terminates command processing.
- O:
-
Re-execute the command at the administrator console.
-
KAVB3672-I
A forced termination (kill) of component-name has started.
Forced termination of process management has begun. component-name indicates JP1_EGN.
- S:
-
Terminates the process management command.
-
KAVB3674-I
Termination processing of component-name has started.
Termination processing of process management has begun. component-name indicates JP1_EGN.
- S:
-
Terminates the process management command.
-
KAVB3675-I
The stop command terminated normally.
The process management termination command terminated normally.
- S:
-
Terminates the process management command.
-
KAVB3676-E
The stop command terminated abnormally.
The process management termination command terminated abnormally.
- S:
-
Terminates the process management command.
- O:
-
Wait a while, use the jegn_spmd_status command to check the status, and then re-execute the command.
-
KAVB3677-E
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 a while and then re-execute the command.
-
KAVB3678-I
There were no processes that could terminate.
There is no process that can be terminated.
- S:
-
Terminates the process management command.
-
KAVB3680-I
Reload processing for component-name has started.
Reload processing of processes managed by process management has started. component-name indicates JP1_EGN.
- S:
-
Terminates the process management command.
-
KAVB3681-I
The reload command terminated normally.
Process management's reload command terminated normally.
- S:
-
Terminates the process management command.
-
KAVB3682-E
The reload command terminated abnormally.
Process management's reload command terminated abnormally.
- S:
-
Terminates the process management command.
- O:
-
Check if any of the managed processes has resulted in a reloading error.
-
KAVB3683-E
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 a while and then re-execute the command.
-
KAVB3684-E
There were no processes that could be reloaded.
There is no process that can be reloaded.
- S:
-
Terminates the process management command.
- O:
-
Make sure that a managed process is running.
-
KAVB3685-E
A timeout occurred in process-name.
Reload processing for the indicated process resulted in a timeout.
- S:
-
Terminates the process management command.
- O:
-
Check if any of the managed processes has resulted in a reloading error.
-
KAVB3690-I
Processing to report the status of component-name has started.
Process management's status report processing has started. component-name indicates JP1_EGN.
- S:
-
Terminates the process management command.
-
KAVB3691-I
All the processes have started.
All managed processes are running.
- S:
-
Terminates the process management command.
-
KAVB3692-I
Some of the processes have started.
Some managed processes are running.
- S:
-
Terminates the process management command.
-
KAVB3693-I
All of the processes have stopped.
All managed processes are stopped.
- S:
-
Terminates the process management command.
-
KAVB3694-I
Part of the process is now restarting.
Part of process management is running.
- S:
-
Terminates process management's status notification command.
-
KAVB3705-I
name-of-managed-process is now starting. (process ID = process-ID)
The indicated managed process is being started. name-of-managed-process indicates the name of a process that constitutes a component managed by process management. process-ID indicates the process ID of the active managed process.
- S:
-
Resumes processing.
-
KAVB3732-I
component-name detected the termination of name-of-managed-process. (process ID = process-ID)
Termination of the indicated managed process was detected. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management. process-ID indicates the process ID of the active managed process.
- S:
-
Resumes processing.
-
KAVB3736-I
All processes of component-name have stopped.
All managed processes have terminated. component-name indicates JP1_EGN.
- S:
-
Terminates command processing.
-
KAVB3737-E
The component-name name-of-managed-process terminated abnormally
Abnormal termination of the indicated managed process was detected. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
- O:
-
Check the integrated trace log output by the managed process that terminated abnormally and eliminate the cause of the error. Use the jegn_spmd_status command to check the status, and then restart. If no message has been output by the managed process, use the data collection tool to collect data and then contact the system administrator.
-
KAVB3743-I
component-name has terminated.
Process management has terminated. component-name indicates JP1_EGN.
- S:
-
Terminates command processing.
-
KAVB3744-I
component-name startup has finished.
Service startup processing has been completed. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3745-I
The component-name startup request has finished.
The startup request has been processed to completion. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3752-E
An attempt to start name-of-managed-process has finished. (return code = return-code, detail code = request-code)
Startup processing for the indicated managed process has failed. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
- O:
-
Use the data collection tool to collect data and then contact the system administrator.
-
KAVB3760-I
The changes to file-name were not applied.
The changes to the settings in the extended startup process definition file (jegn_service_0700.conf) were not applied.
- S:
-
Resumes processing.
- O:
-
Change the settings and then re-execute the command.
-
KAVB3761-E
In the file file-name, the restart-or-not value is invalid. ( restart-or-not = setting)
The setting in the extended startup process definition file (jegn_service_0700.conf) for whether restart is to be permitted is not valid.
- S:
-
Resumes processing.
- O:
-
Change the setting and then re-execute the command.
-
KAVB3762-I
Set 0 or 1 for the restart-or-not value.
You must specify either 0 or 1 in the extended startup process definition file (jegn_service_0700.conf) as the setting for whether restart is to be permitted.
- S:
-
Resumes processing.
- O:
-
Specify either 0 or 1 for the restart setting.
-
KAVB3763-E
In the file file-name, the number-of-restarts value is invalid. (restart num. = setting)
The specification in the extended startup process definition file (jegn_service_0700.conf) for the restart count is not valid.
- S:
-
Resumes processing.
- O:
-
Change the setting and then re-execute the command.
-
KAVB3764-I
Set 0 to 99 for the number-of-restarts value.
You must specify a value in the range from 0 to 99 in the extended startup process definition file (jegn_service_0700.conf) as the setting for the restart count.
- S:
-
Resumes processing.
- O:
-
Specify a value in the range from 0 to 99 for the restart count.
-
KAVB3765-E
In the file file-name, the restart interval value is invalid. (restart interval = setting)
The specification in the extended startup process definition file (jegn_service_0700.conf) for the retry interval is not valid.
- S:
-
Resumes processing.
- O:
-
Change the setting and then re-execute the command.
-
KAVB3766-I
Set 0 to 3600 for the restart interval value.
You must specify a value in the range from 0 to 3,600 in the extended startup process definition file (jegn_service_0700.conf) as the setting for the retry interval.
- S:
-
Resumes processing.
- O:
-
Specify a value in the range from 0 to 3,600 for the retry interval.
-
KAVB3767-E
In the file file-name, the restart-count reset time is invalid. (restart-count reset time = setting)
The specification in the extended startup process definition file (jegn_service_0700.conf) for the restart-count reset time is not valid.
- S:
-
Resumes processing.
- O:
-
Change the setting and then re-execute the command.
-
KAVB3768-I
Set 3600 to 2147483647 for the restart-count reset time.
You must specify a value in the range from 3,600 to 2,147,483,647 in the extended startup process definition file (jegn_service_0700.conf) as the setting for the restart-count reset time.
- S:
-
Resumes processing.
- O:
-
Specify a value in the range from 3,600 to 2,147,483,647 for the restart-count reset time.
-
KAVB3769-I
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 indicated entries in the extended startup process definition file (jegn_service_0700.conf).
- S:
-
Resumes processing.
- O:
-
Check the entries in the extended startup process definition file.
-
KAVB3777-I
component-name: The stopped name-of-managed-process will be restarted. (restart count = restart-count)
The indicated managed process, which was terminated, is being restarted. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Restarts the indicated managed process.
-
KAVB3778-I
component-name: A startup request was sent to the process name-of-managed-process.
A start request was sent to the indicated managed process. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
-
KAVB3779-I
component-name: An attempt to send a startup request to the process name-of-managed-process failed.
An attempt to send a startup request to the indicated managed process has failed. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
-
KAVB3786-E
To process child-process-ID-of-managed-process, the system sent the signal signal-name
The indicated signal was sent to the indicated child process of a managed process. child-process-ID-of-managed-process indicates the process ID of a process generated by the active managed process.
- S:
-
Resumes processing.
-
KAVB3788-E
component-name: The number of restarts of name-of-managed-process exceeded the specified restart count.
The number of restart attempts for the indicated managed process has exceeded the specified maximum. component-name indicates JP1_EGN. name-of-managed-process indicates the name of a process that constitutes a component managed by process management.
- S:
-
Resumes processing.
- O:
-
Check the integrated trace log output by the managed process that terminated abnormally and eliminate the cause of the error. Use the jegn_spmd_status command to check the status, and then restart. If no message has been output by the managed process, use the data collection tool to collect data and then contact the system administrator.
-
KAVB3802-W
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:
-
Resumes processing.
- O:
-
To use the health check function to monitor process management, restart process management.
-
KAVB3840-E
The product information could not be acquired because there was not enough memory. (Detailed information : function-name, return-value)
An attempt to acquire product information failed because of insufficient resources.
- S:
-
Cancels processing.
- O:
-
Check for a shortage of system resources. After the resource shortage is resolved, re-execute the command. If the error cannot be resolved, use the data collection tool to collect data and then contact the system administrator.
-
KAVB3841-E
The product information could not be acquired because the environment is invalid. (Detail information : function-name, return-value)
An attempt to acquire product information failed because of an invalid environment.
- S:
-
Cancels processing.
- O:
-
Check for a system failure. Uninstall the product, reinstall it, and then re-execute the command.
-
KAVB3846-I
component-name completed the reload request.
Reload processing has been completed. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3855-I
The process name-of-managed-process will be terminated by SIGKILL. (process ID = process-ID)
SIGKILL has been sent to the indicated managed process. name-of-managed-process indicates the name of a process that constitutes a component managed by process management. process-ID indicates the process ID of the active managed process.
- S:
-
Resumes processing.
-
KAVB3862-E
component-name: No processes could be started.
The system was unable to start any of the managed processes. component-name indicates JP1_EGN.
- S:
-
Terminates command processing.
- O:
-
Make sure that there is sufficient system memory and check if the product has been installed correctly.
-
KAVB3863-E
component-name: No processes can be reloaded.
None of the managed processes was ready to be reloaded. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
- O:
-
Wait a while and then re-execute the command.
-
KAVB3870-E
The conf directory path cannot be obtained from the common definition.
An attempt to acquire the conf directory path from the common definition failed.
- S:
-
Terminates the process management command.
- O:
-
- When operating in a cluster system:
-
Make sure that the correct logical host name is specified in the argument of the process management command. Also make sure that the correct logical host name is set in the JP1_HOSTNAME environment variable.
- When not operating in a cluster system:
-
Make sure that the JP1_HOSTNAME environment variable is not used during startup. If the JP1_HOSTNAME environment variable is not set, perform a repair installation.
-
KAVB3871-E
The conf directory path cannot be obtained by using the specified logical hostname.
The attempt to acquire the conf directory path from the common definition using the specified logical host name has failed.
- S:
-
Terminates the process management command.
- O:
-
This operation assumes you are operating in a cluster system. Make sure that the specified logical host name is correct or that setup has been completed successfully.
-
KAVB3872-E
The log directory path cannot be obtained from the common definition information.
An attempt to acquire the log directory path from a common definition has failed.
- S:
-
Terminates the process management command.
- O:
-
If you are operating in a cluster system, make sure that the specified logical host name is correct or that setup has been completed successfully. If you are not operating in a cluster system, perform a repair installation.
-
KAVB3873-E
The log directory path cannot be obtained by using the specified logical hostname.
An attempt to acquire the log directory path from a common definition using the specified logical host name has failed.
- S:
-
Terminates the process management command.
- O:
-
This operation assumes you are operating in a cluster system. Make sure that the specified logical host name is correct or that setup has been completed successfully.
-
KAVB3874-E
HNTRLib could not be initialized.
Initialization of HNTRLib2 has failed. No log information will be output.
- S:
-
Resumes processing.
- O:
-
If process management was running, terminate it and then restart it.
-
KAVB3875-E
HNTRLib could not be initialized.
An attempt to initialize HNTRLib2 has failed. No log information will be output.
- S:
-
Resumes processing.
- O:
-
If process management was running, terminate it and then restart it.
-
KAVB3899-E
The work directory path cannot be acquired from the common definition information. (return code = return-code)
An attempt to acquire the work directory path from a common definition has failed.
- S:
-
Terminates the process management command.
- O:
-
If you are operating in a cluster system, make sure that the specified logical host name is correct or that setup has been completed successfully. If you are not operating in a cluster system, perform a repair installation.
-
KAVB3905-I
A stop request was sent to the process name-of-managed-process. (process ID = process-ID)
A termination request has been issued to the indicated managed process. name-of-managed-process indicates the name of a process that constitutes a component managed by process management. process-ID indicates the process ID of the active managed process.
- S:
-
Resumes processing.
-
KAVB3908-I
A reload request was sent to the process name-of-managed-process. (process ID = process-ID)
A reload request has been issued to the indicated managed process. name-of-managed-process indicates the name of a process that constitutes a component managed by process management. process-ID indicates the process ID of the active managed process.
- S:
-
Resumes processing.
-
KAVB3910-I
SIGTERM will terminate the process name-of-managed-process. (process ID = process-ID)
SIGTERM has been sent to the indicated managed process. name-of-managed-process indicates the name of a process that constitutes a component managed by process management. process-ID indicates the process ID of the active managed process.
- S:
-
Resumes processing.
-
KAVB3911-E
The process management daemon is busy.
Some other command processing is underway.
- S:
-
Terminates the process management command.
- O:
-
Wait a while and then re-execute the command. If this message was displayed when the jegn_spmd_reload command was executed during startup, termination, or reload processing, wait until the other processing is completed, and then re-execute the command.
-
KAVB3912-I
The process is running.
- S:
-
Terminates the process management command.
-
KAVB3913-I
The process is not running.
- S:
-
Terminates the process management command.
-
KAVB3914-E
An attempt to open the lock file under the conf directory has failed.
An attempt to open the lock file in the conf directory has failed.
- S:
-
Terminates the process management command.
- O:
-
Check that there is a conf directory and that you have write permissions.
If you are operating in a cluster system, check that the defined conf directory exists and that you have write permissions.
-
KAVB3935-E
create_pre_process_entry: Memory allocation failed. (request-code)
Creation of a startup preprocessing management table has failed. Startup preprocessing is not being performed.
- S:
-
Resumes processing.
- O:
-
Check if a memory shortage occurred.
-
KAVB3960-I
Startup preprocessing is being performed.
Process management is engaged in startup preprocessing.
- S:
-
Terminates process management's status notification command.
-
KAVB3961-E
The request could not be accepted because startup preprocessing is being performed.
Process management was unable to accept a command request because it was engaged in startup preprocessing.
- S:
-
Terminates the process management command.
- O:
-
Wait a while and then re-execute the command.
-
KAVB3981-I
jegn_spmd_stop -job: A request to stop job restrictions will be sent to all processes of component-name.
A job restriction stop request is being sent to all managed processes. component-name indicates JP1_EGN.
- S:
-
Resumes processing.
-
KAVB3984-I
A request to stop job restrictions has been sent to the process name-of-managed-process. (process ID = process-ID)
A job restriction stop request has been sent to the indicated managed process. name-of-managed-process indicates the name of a process that constitutes a component managed by process management. process-ID indicates the process ID of the active managed process.
- S:
-
Resumes processing.
-
KAVB3986-I
Processing to stop component-name job restrictions has started.
Process management's job restriction stop processing has started. component-name indicates JP1_EGN.
- S:
-
Terminates the process management command.