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.
Fail to get conf directory path. jp1BsCnfGetStringValue fail.
The conf directory path could not be obtained from the common definition.
- S:
- Terminates processing.
- O:
- Determine whether the conf directory path of JP1/Base is defined in the common definition.
Fail to get log directory path. jp1BsCnfGetStringValue fail.
The log directory could not be obtained from the common definition.
- S:
- Terminates processing.
- O:
- Determine whether the log directory path of JP1/Base is defined in the common definition.
HNTRLib Initialize fail. bslog NULL.
An attempt to initialize message output failed.
- S:
- Does not output the message.
- O:
- Make sure that JP1/Base setup was completed normally.
HNTRLib Initialize fail.
An attempt to initialize message output failed.
- S:
- Does not output the message.
- O:
- Make sure that JP1/Base setup was completed normally.
Fail to open message file.
An attempt to open the message file failed.
- S:
- Does not output the message.
- O:
- In UNIX, determine whether the catalog file exists in the /opt/jp1base/lib/nls directory.
Fail to load resource.
An attempt to read the message file failed.
- S:
- Does not output the message.
- O:
- Make sure that JP1/Base setup was completed normally.
Fail to load catalog file.
An attempt to read the message file failed.
- S:
- Does not output the message.
- O:
- In UNIX, make sure that the message file (jbsrt.cat) exists in the /opt/jp1base/lib/nls directory and that the access permission is appropriate.
vsprintf error.
An error occurred during internal processing of message output.
- S:
- Does not output the message.
- O:
- Make sure that sufficient system resources are allocated.
Cannot move to the log directory.
Could not move data to the log output directory.
- S:
- Does not move data to the log directory.
Failed to initialize JP1/IM communication infrastructure. Error Type = JBS_EJP1HOSTS
An attempt to initialize the communication infrastructure failed. Read processing failed because the jp1hosts data is invalid.
- S:
- Terminates processing.
- O:
- Carefully review the value of jp1hosts in the common definition.
Failed to initialize JP1/IM communication infrastructure. jp1BsCommInit Error Code = error-code. Terminating
An attempt to initialize the communication infrastructure failed.
- S:
- Aborts processing.
- O:
- Make sure that JP1/Base setup was completed normally.
Failed to acquire the port number. The default port number is used.
The port number could not be acquired.
- S:
- Uses the default port to start.
- O:
- Determine whether the port number for Configuration Management exists in the services file.
Failed to initialize JP1/IM communication infrastructure. Terminating.
An attempt to initialize communication failed. It is possible that the port is already in use.
- S:
- Terminates processing.
- O:
- Determine whether the port for Configuration Management is already in use.
- If IP bind is specified as the communication method, determine whether an invalid IP address is specified for a local IP host address.
Failed to create a thread communication to the process management. Terminating.
An attempt to create a thread for communicating with process management failed.
- S:
- Terminates Configuration Management.
- O:
- Make sure that there is sufficient memory, and then retry the operation.
jbsspm_getfd function failed. Terminating
An attempt to acquire a file descriptor for communication failed.
- S:
- Terminates the operation.
- O:
- Close other programs, and then retry the operation.
jbsroute is running.
Configuration Management started.
- S:
- Configuration Management enters operating status.
Reload request was received.
A reload request was received from process management.
- S:
- Starts reload processing.
jbsroute terminate.
Configuration Management ended.
- S:
- Terminates Configuration Management.
Cannot get JP1_BIND_ADDR. jp1BsCnfGetStringValue = function-return-value
The JP1_BIND_ADDR value of the common definition could not be acquired.
- S:
- Binds using ANY.
- O:
- Determine whether JP1_BIND_ADDR exists in the common definition.
There is no definition of conf directory path for JP1/IM - Console.
The conf directory definition of JP1/IM - Manager could not be acquired.
- S:
- Starts as JP1/Base.
- O:
- If only JP1/Base is installed on the machine ignore this message.
There is not JP1/IM - Console product Information.
The product type (JP1/IM - Manager) of JP1/IM cannot be acquired.
This message is always output when only JP1/Base is installed on a machine.
- S:
- Starts as JP1/Base.
- O:
- If only JP1/Base is installed on the machine, ignore this message.
JP1/IM - Central Console
JP1/IM - Manager has been installed.
- S:
- Configuration Management operates as JP1/IM - Manager.
JP1/IM - Satellite Console
JP1/IM - Satellite Console has been installed.
- S:
- Configuration Management operates as JP1/IM - Satellite Console.
JP1/Base
JP1/Base has been installed.
- S:
- Configuration Management operates as JP1/Base.
Failed to create communication data. jbsroute_make_rtdata Error Code = error-code. error-code-explanation
An attempt to create communication data failed.
- S:
- Continues processing.
- O:
- Make sure that there is sufficient memory.
Failed to send communication data. jbsroute_send_rtdata Error Code = error-code. error-code-explanation
An attempt to send communication data failed.
- S:
- Continues processing.
- O:
- Determine whether there is a lower-level host in the configuration definition that is unable to communicate.
Received configuration distribution request from JP1/Base
A definition distribution request was received from JP1/Base. Definitions cannot be distributed from a machine on which only JP1/Base is installed.
- S:
- Stops definition distribution.
- O:
- Carefully review the configuration definition file to determine whether a lower-level host is defined on a machine on which only JP1/Base is installed.
JP1/IM - Central Console received configuration distribution request from JP1/IM - Satellite Console.
JP1/IM - Manager is defined at a lower level than JP1/IM - Satellite Console in the configuration definition.
- S:
- Does not distribute the definition to the host.
- O:
- Correct the configuration definition file so that JP1/IM - Manager is not defined at a lower level than JP1/IM - Satellite Console.
JP1/Base defines lower-level hosts.
Lower-level hosts are defined in JP1/Base in the configuration definition.
- S:
- Does not distribute the definition to the lower-level hosts.
- O:
- Check the following items:
- Correct the configuration definition file so that hosts are not defined under JP1/Base.
- If this message is output on a logical host, make sure that logical host setup has been completed. If not, execute the following setup programs to set up the logical host.
Windows: jp1cohasetup.exe
UNIX: jp1cc_setup_cluster
Failed to get lower-level host in the definition file. jbsroute_get_under_host Error Code = error-code. error-code-explanation
An attempt to acquire lower-level hosts in the definition file failed. This error occurs primarily when there is a memory shortage.
- S:
- Cannot perform definition distribution and other operations at the lower-level hosts.
- O:
- Determine whether a memory shortage occurred.
Wrong attempt to distribute the configuration definition to the highest-level host from other host.
A separately defined definition file was sent from another host to a host that was defined as the highest-level host.
- S:
- Cannot perform definition distribution and other operations at the highest-level host.
- O:
- Another host cannot distribute configuration definition to a host defined as the highest-level host. Delete the configuration information at the highest-level host, and then re-execute the definition distribution command.
Failed to get upper-level host. jbsroute_get_parent_host Error Code = error-code. error-code-explanation
The highest-level host could not be acquired.
- S:
- Cannot perform definition distribution and other operations.
- O:
- Determine whether a memory shortage occurred.
Failed to get lower-level host. jbsroute_get_child_host Error Code = error-code. error-code-explanation
A lower-level host could not be acquired.
- S:
- Cannot perform definition distribution and other operations.
- O:
- Determine whether a memory shortage occurred.
Failed to write data to configuration information file. jbsroute_write_rtdata Error Code = error-code. error-code-explanation
An attempt to write to the configuration definition file failed.
- S:
- Cannot perform definition distribution and other operations.
- O:
- Make sure that there is write permission for the conf/route/ directory.
Failed to send communication data. jbsroute_send_rtdata_hosts Error Code = error-code. error-code-explanation
An attempt to send communication data failed.
- S:
- Cannot perform definition distribution and other operations at the transmission destination host.
- O:
- Make sure that JP1/Base is running on the transmission destination host. Also make sure that the host is able to communicate.
Failed to get lower-level host information. jbsrt_getunderhost Error Code = error-code. error-code-explanation
A lower-level host could not be acquired.
- S:
- Terminates the Configuration Management command.
- O:
- Make sure that sufficient memory is allocated.
Failed to delete configuration information file. jbsroute_del_rtdata Error Code = error-code. error-code-explanation
The configuration definition file could not be deleted.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Make sure that there is write permission for the conf/route/ directory.
Failed to communication initialization. jbsroute_send_rtdata_init Error Code = error-code. error-code-explanation
An attempt to initialize communication failed.
- S:
- Terminates the jbsrt_distrib or jbsrt_sync command.
- O:
- Determine whether it is possible to communicate with the communication destination host.
Failed to receive communication data. jbsroute_recv_rtdata Error Code = error-code. error-code-explanation
An attempt to receive communication data failed.
- S:
- Terminates the jbsrt_distrib or jbsrt_sync command.
- O:
- Determine whether an error occurred at the transmission destination host.
Failed to open the definition file.
An attempt to open the definition file failed.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Determine whether the configuration definition file is in the conf/route/ directory.
- Also make sure that there is read permission for the configuration definition file.
Memory allocation failed.
Memory could not be allocated.
- S:
- Configuration control continues processing. Terminates the command abnormally.
- O:
- Make sure that sufficient memory is allocated.
A line with more than two entries exists.
The same host name is defined multiple times in the definition file.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Determine whether the same host is defined multiple times in the configuration definition file.
No entries in a line.
The definition file does not contain any host name line.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Check the configuration definition file.
Length of host name exceeds 256 characters. host-name
The length of the host name in the definition file is 256 characters or more.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Carefully revise the configuration file so that the host name is no longer than 255 characters.
Definition of management host is invalid. management-host-name
The definition of the management host in the definition file is invalid.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Make sure that the displayed management host name is correctly enclosed by [ and ].
The host is specified more than once. host-name
The same host is defined multiple times in the definition file.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Carefully revise the configuration definition file so that the same host is not defined multiple times.
Managed host does not exist. host-name
A management host is defined without the managed host.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Carefully review the configuration definition file, and define the managed host for the management host.
The host is in a loop status. host-name
The definition file contains a looped definition.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Carefully review the configuration definition file, and correct the looped system configuration.
The highest-level host is different. host-name host-name
Two or more highest-level hosts are defined in the definition file.
- S:
- Terminates the jbsrt_distrib command.
- O:
- Carefully review the configuration definition file, and make sure that only one host is defined as the highest-level host.
Cannot get conf path from common definition.
The conf path could not be acquired from the common definition.
- S:
- Terminates Configuration Management or the command.
- O:
- Determine whether the conf directory of JP1/Base is defined in the common definition.
HNTRLib could not be initialized.
An attempt to initialize message output failed.
- S:
- Does not output the message.
- O:
- Make sure that JP1/Base setup was completed normally.
HNTRLib could not be initialized.
An attempt to initialize message output failed.
- S:
- Does not output the message.
- O:
- Make sure that JP1/Base setup was completed normally.
No execution authorization.
The user that attempted to execute the command does not have Administrator permissions.
- S:
- Cannot execute processing.
- O:
- Execute the command as a user with Administrator permissions.
Failed to acquire the port number. The default port number is used.
The port number could not be acquired.
- S:
- Uses the default port to start.
- O:
- Determine whether the port number of Configuration Management exists in the services file.
Failed to load definition file.
An attempt to read the definition file failed.
- S:
- Does not execute the jbsrt_distrib command.
- O:
- Make sure that the configuration definition file is placed in the correct location.
Cannot get the current host name from the definition file.
The local host is not defined in the definition file.
- S:
- Does not execute the jbsrt_distrib command.
- O:
- Define the local host in the configuration definition file.
Failed to get the lower-level host name in the definition file.
An error occurred while acquiring a lower-level host from the definition file.
- S:
- Does not execute the Configuration Management command.
- O:
- Make sure that sufficient memory is allocated.
JP1/Base defines lower-level hosts.
Lower-level hosts are defined in JP1/Base.
- S:
- Does not distribute configuration definitions to the lower-level hosts.
- O:
- Check the following items:
- Correct the configuration definition file so that hosts are not defined under JP1/Base.
- If this message is output in a logical host, make sure that logical host setup has been completed. If not, execute the following setup programs to set up the logical host.
Windows: jp1cohasetup.exe
UNIX: jp1cc_setup_cluster
Failed to get the definition data.
An I/O error occurred while reading the configuration definition file.
- S:
- Does not execute the Configuration Management command.
- O:
- Make sure that there is write permission for the conf/route/ directory.
Failed to create communication data.
An attempt to create communication data failed. This error occurs primarily when there is a memory shortage.
- S:
- Does not execute the Configuration Management command.
- O:
- Make sure that sufficient memory is allocated.
Failed to connect to the server.
An attempt to connect to the server failed.
- S:
- Does not execute the Configuration Management command.
- O:
- Make sure that JP1/Base is running.
Failed to send the data. Error Code = error-code. error-code-explanation
An attempt to send data to the Configuration Management server failed.
- S:
- Terminates the jbsrt_distrib or jbsrt_sync command.
- O:
- Determine whether Configuration Management is running and whether a memory shortage occurred.
Failed to receive the data.
An attempt to receive data from the Configuration Management server failed.
- S:
- Places the jbsrt_distrib or jbsrt_sync command in error status.
- O:
- Check the following items:
- After JP1/IM was installed, was JP1/Base restarted?
- Has a memory shortage occurred?
- Is there write or read permission for the conf/route/ directory?
Cannot delete configurations for the host and its lower-level hosts. Try again after deleting each definition separately.host-name
Configuration information could not be deleted from certain hosts.
- O:
- Execute the jbsrt_del command to delete configuration information individually from the displayed host and its lower-level hosts.
The server is processing.
An attempt was made to distribute definitions during processing of the Configuration Management server.
- S:
- Places the jbsrt_distrib or jbsrt_sync command in error status.
- O:
- Wait awhile, and then retry the operation.
Deleted the current configuration definition
The jbsrt_distrib command was used to delete configuration information.
- S:
- Continues processing.
Cannot set configuration in the host. host-name
Configuration information could not be set in certain hosts during configuration definition confirmation.
- S:
- Places the jbsrt_distrib command in error status.
- O:
- On the host that has the error, check the following items:
- Is JP1/Base running?
- Is the same port number being used as the one specified for the Configuration Management instance of the host where the definitions are distributed?
- Are lower-level hosts defined in JP1/Base?
- Is JP1/IM - Satellite Console the higher-level host of JP1/IM - Manager?
- Are at least 6 hosts defined immediately underneath JP1/IM - Central Console 5 Node?
- Are at least 11 hosts defined immediately underneath JP1/IM - Central Console 10 Node?
- Is it possible to resolve the host name of the host that has the error from a host at a higher-level than the host that has the error?
- Was the host that has the error previously defined as the highest-level host? If the configuration definition information for the highest-level host remains, execute the jbsrt_distrib command to delete the configuration information.
- After JP1/IM was installed, was JP1/Base restarted?
- Has a memory shortage occurred?
- Are there write and read permissions for the conf/route/ directory?
- If the problem is other than the above, check the following items in the host that has the error:
- Execute the jbsrt_get command.
- Determine whether any of the following occurred:
Was a KAVB3162-E message output?
Did the jbsrt_get command end abnormally?
Is the local host name displayed as a higher-level host or a lower-level host?
Is a host name other than the local host name displayed as the local host?
Is the host name misspelled?
- If any of the above occurred, use the following method to recover from the error:
- Execute the jbsrt_del command to delete the configuration definition information.
- On the manager host, execute the jbsrt_distrib command to redistribute the configuration definition information.
Failed in definition distribution. Cannot set configuration information in the host. host-name
Configuration information could not be distributed to certain hosts during configuration distribution.
- O:
- Re-execute the jbsrt_distrib command, distributing the definition without deleting the configuration information. If you can confirm that the definition was distributed to hosts and lower-level hosts for which errors occurred previously, it means that the configuration definition was distributed to the entire system.
Succeed the jbsrt_distrib command
The definition distribution command ended normally.
- S:
- Ends the jbsrt_distrib command normally.
Definition data is not found.
The configuration information has not been defined.
- S:
- Does not execute the jbsrt_sync command.
- O:
- Execute the jbsrt_distrib command, and then execute the jbsrt_sync command.
- After the jbsrt_sync command is executed, make sure that the conf/route/ 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.
Failed to execute the jbsrt_sync command. An error occurred in the host. host-name
An error occurred during execution of the jbsrt_sync command.
- S:
- Displays the host that has the error.
- O:
- Make sure that JP1/Base is running on the host that has the error. If it is running, check the following items:
- Execute the jbsrt_get command.
- Determine whether any of the following occurred:
Was a KAVB3162-E message output?
Did the jbsrt_get command end abnormally?
Is the local host name displayed as a higher-level host or a lower-level host?
Is a host name other than the local host name displayed as the local host?
Is the host name misspelled?
- If any of the above occurred, use the following method to recover from the error:
- Execute the jbsrt_del command to delete the configuration definition information.
- On the manager host, execute the jbsrt_distrib command to redistribute the configuration definition information.
Succeed the jbsrt_sync command
The synchronization command ended normally.
- S:
- Ends the jbsrt_sync command normally.
Definition does not exist.
The configuration information has not been defined.
- S:
- Terminates the jbsrt_get and jbsrt_del commands.
- O:
- Execute the jbsrt_distrib command, and then retry the operation.
- After the jbsrt_distrib command is executed, make sure that the conf/route/ 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.
Cannot access definition.
An attempt to read the configuration information failed.
- S:
- Terminates the jbsrt_get and jbsrt_del commands.
- O:
- Make sure that there is write permission for the conf/route/ directory.
Deleted the definition data.
The jbsrt_del command ended normally.
- S:
- Ends the jbsrt_del command.
Get the logical host name from the environment variable of JP1_HOSTNAME
The logical host name was obtained from the JP1_HOSTNAME environment variable.
- S:
- Starts as a logical host of the name obtained from the JP1_HOSTNAME environment variable.
- O:
- To start as a physical host, cancel the JP1_HOSTNAME environment variable setting.
jbsrt_distrib command is time out.
A time-out of the jbsrt_distrib command occurred.
- S:
- Places the jbsrt_distrib command in error status and terminates the command.
- O:
- Check the following items:
- Determine whether an error occurred in a lower-level host.
- If it is taking too long to distribute definitions, a time-out of the jbsrt_distrib command occurs. Carefully review the system configuration.
jbsrt_sync command is time out.
A time-out of the jbsrt_sync command occurred.
- S:
- Places the jbsrt_sync command in error status and terminates the command.
- O:
- Check the following items:
- Determine whether an error occurred in a lower-level host.
- If it is taking too long to perform synchronization processing, a time-out of the jbsrt_sync command occurs. Carefully review the system configuration.
Failed to initialize JP1/IM communication infrastructure. Error Type = JBS_EJP1HOSTS
An attempt to initialize the communication infrastructure failed. Read processing failed because the jp1hosts data is invalid.
- S:
- Terminates processing.
- O:
- Carefully review the value of the jp1hosts common definition.
Failed to initialize JP1/IM communication infrastructure. jp1BsCommInit Error Code = error-code
An attempt to initialize the communication infrastructure failed.
- S:
- Terminates the Configuration Management command.
- O:
- Make sure that JP1/Base setup was completed normally.
- Collect data, and then contact a system administrator.
Too many lower-level host. The maximum number is the-maximum-number-of-lower-level-hosts-directly-underneath
The number of hosts specified directly underneath as lower-level hosts in the configuration definition exceeds the maximum.
- S:
- Does not set the configuration information for the lower-level hosts.
- O:
- Make sure that no more than 5 hosts are defined immediately underneath JP1/IM - Central Console 5 Node and that no more than 10 hosts are defined immediately underneath JP1/IM - Central Console 10 Node.
Cannot get conf path from common definition with specified logical host name.
The conf path to the logical host name specified in the common definition could not be acquired.
- S:
- Terminates Configuration Management or the command.
- O:
- Make sure that the specified logical host name is correct, and that the conf directory of JP1/Base is defined in the common definition of the specified logical host name.
Failed to execute jevreload command.
The jevreload command could not be executed.
- S:
- Does not execute the jevreload command.
- O:
- Determine whether a memory shortage occurred.
Failed to get install path.
In Windows, the installation path of JP1/Base could not be acquired.
- S:
- Does not execute the jevreload command.
- O:
- Make sure that JP1/Base has been correctly installed and configured.
- If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
Failed to create jevreload process.
The jevreload command could not be executed.
- S:
- Does not execute the jevreload command.
- O:
- Determine whether a memory shortage occurred.
An attempt to use the jp1gethostname function has failed.
An attempt to perform initialization processing for communication failed.
- S:
- Suspends processing.
- O:
- For a physical host, make sure that the local host name setting is correct. For a logical host, make sure that the logical host name setting is correct.
An attempt to use the jp1gethostbyname(hostname:host-name) function has failed.
An attempt to resolve an IP address from the host name failed.
- S:
- Suspends processing.
- O:
- Determine whether it is possible to ping the host name. If you are using DNS, determine whether there is trouble on the network.
An attempt to create a socket has failed.
A communication socket could not be generated.
- S:
- Suspends processing.
- O:
- Make sure that sufficient system resources are allocated.
An attempt to set socket options has failed.
An attempt to specify socket options failed.
- S:
- Suspends processing.
- O:
- Make sure that sufficient system resources are allocated.
An attempt to bind has failed (IP address: IP-address).
A failure occurred during initialization processing for communication.
- S:
- Continues processing.
- O:
- Make sure that the relevant IP address is correctly assigned to the network card.
An attempt to listen has failed (IP address: IP-address).
A failure occurred during initialization processing for communication.
- S:
- Continues processing until wait response processing has been tried for all IP addresses defined in the local host.
- O:
- Make sure that the relevant IP address is correctly assigned to the network card and that the communication environment is ready.
Bind and listen attempt has succeeded (IP address: IP-address).
Initialization of the communication environment was successful.
- S:
- Continues processing.
No appropriate bind and listen IP address was found.
A failure occurred during initialization processing for communication.
- S:
- Suspends processing.
- O:
- Prepare the communication environment, and then retry the operation.
An attempt to connect has failed (hostname: host-name, IP address: IP-address).
A failure occurred during initialization processing for communication.
- S:
- Continues processing until connection has been tried to all IP addresses defined by the host name.
- O:
- Make sure that communication is possible with the connected IP address.
An attempt to connect has succeeded (hostname: host-name, IP address: IP-address).
An attempt to establish a communication connection was successful.
- S:
- Continues processing.
No appropriate bind and connect IP address was found.(hostname: host-name)
A failure occurred during initialization processing for communication.
- S:
- Suspends processing.
- O:
- Prepare the communication environment, and then retry the operation.
Please set the logical host name to within 255 characters.
A string of 256 characters or more was specified for a logical host name.
- S:
- Suspends processing.
- O:
- Specify a logical host name that contains no more than 255 characters.
Part of TCP/IP wait response processing has failed, but jbsroute processing will continue.
An attempt to perform part of TCP/IP wait response processing failed.
- S:
- Continues processing.
- O:
- Part of the IP address may have been specified incorrectly. Configuration Management processing of JP1/Base continues in impaired status. However, in this status, part of communication processing is not performed correctly. Resolve the problem, and then restart JP1/Base.
An error occurred in system call.:maintenance-information
An error occurred in an OS system call.
- S:
- Suspends processing.
- O:
- Check the following items. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
- Make sure that sufficient system resources are allocated.
- Make sure that the OS is operating normally.
- Make sure that the communication environment is operating normally.
The configuration information file is invalid.
The configuration definition file cannot be read because it is invalid.
- S:
- Configuration Management continues processing. Terminates the jbsrt_distrib, jbsrt_sync, and jbsrt_get commands.
- O:
- Use the following procedure to recover from the error:
- To delete the configuration definition information, execute the jbsrt_del command on the host where the message is output.
- Execute the jbsrt_distrib command to redistribute configuration definition information from the highest-level host.
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.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.