Job Management Partner 1/Integrated Management - Manager Messages

[Contents][Index][Back][Next]

2.2 Messages related to command execution (KAVB2001 to KAVB2999)

KAVB2002-I

Command issued to host-name host was not received within the specified time (Command : command-name).

The entered command was not accepted within the specified time.

S:
Continues executing the entered command.

O:
This message may be output if the official name of the host that outputs this message cannot be resolved in host-name host. For the name displayed in host-name, the host name in the level that is defined in the configuration definition is displayed.
Check the hosts file of host-name host, registration of DNS, and configuration definition information.

KAVB2003-E

Cannot connect to host-name host; so, the command-name command cannot be executed.

The command cannot be executed because a connection could not be established to the host to which the command is transferred.

S:
Does not execute the command.

O:
Determine whether JP1/Base is running on the host of host-name. If JP1/Base is running, check the network for problems.

KAVB2005-E

The command-name command was rejected because it could not be relayed to the local host.

The host of JP1/IM - Manager that issued a command execution request matches the IP address of the command forwarding destination host.

S:
Does not execute the command.

O:
Check the following items:
  • Is there a problem resolving the IP address of the command forwarding destination host defined in the configuration definition?
  • Are the host name and IP address of the host that output the message set correctly?

KAVB2012-I

Received the command-name command.

The command was accepted.

S:
Continues processing.

KAVB2013-I

Terminated the command-name command. pid=process-ID terminate code=termination-code

Execution of the command indicated by command-name was completed. In Windows, the entered command is executed as cmd.exe, and in UNIX, the entered command is executed as an argument of the shell of the user that executed the command. Therefore, the displayed values are output for the process ID and termination code.

KAVB2022-E

Reception of the command was rejected because it exceeds the maximum length of 1024 bytes.

The length of the command including the argument exceeds 1024 bytes.

S:
Does not execute the command.

O:
Carefully review the length of the command including the argument.

KAVB2023-E

Could not find the command-name command.

The corresponding command cannot be found.

S:
Does not execute the command.

O:
In Windows, determine whether cmd.exe exists, and in UNIX, determine whether the shell of the user that will execute the command exists.

KAVB2024-E

Command cannot be executed because the corresponding host(host-name) is not registered in hosts.

The address of the host indicated by host-name cannot be resolved.

S:
Does not execute the command.

O:
Take the necessary steps so that the address of host-name can be resolved.

KAVB2027-E

Cannot execute the command. Failed to simulate the user user-name environment.

The command could not be executed because user mapping failed.

S:
Does not execute the command.

O:
Check the following items:
  • Is the JP1 user that logged in to JP1/IM - View or the user that is defined in the action definition defined in the user mapping definition of the command execution host?
  • Is the OS user defined in the user mapping definition?
  • In Windows, was the password of the OS user that is defined in user mapping changed?
  • In Windows, is the Log on as a service or Allow log on locally permission assigned to the OS user that is defined in user mapping?
  • In UNIX, is the user ID of the OS user that is defined in user mapping valid?

KAVB2029-I

Executed the command-name command. pid=process-ID

The command was executed.

KAVB2031-E

Cannot execute the command. The host (host-name) is not managed by JP1/Console.

Command execution was attempted by a host that is not a management target.

Another possibility is that the host name of the target host cannot be resolved.

S:
Does not execute the command.

O:
  • Use the configuration definition to define the specified host as the target host.
    For the target host, specify a host at a lower level than the manager host that is logged in and defined in the system configuration definition.
  • Configure settings so that the host name of the target host and the host name defined in the configuration definition can be resolved.

KAVB2037-I

Terminated Command Control.

Command control was stopped.

KAVB2041-E

Could not find the Environment file (file-name).

The environment variable file specified in the Execute Command window or the action definition was not found.

O:
Make sure that the specified file is on the target host and that the path is correct.

KAVB2042-E

Jcocmd received an illegal request from process manager.

Command control received an unusable request from the process manager.

S:
Terminates the remote command.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
  • In UNIX, is sufficient disk space allocated under /var/opt/jp1base?
  • In UNIX, are permissions under /var/opt/jp1base appropriate?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2051-I

A timeout has occurred, since no reply has been obtained from the host [host-name]. Common configuration value RSPTIME_START = [internal-code]

There is no response from the host at the connection destination.

S:
Does not execute the command.

O:
Make sure that JP1/Base is running on the host at the connection destination.

KAVB2052-I

Since the connection with host [host-name] was released, command response processing was interrupted.

Command response processing was suspended because connection with the host was released. This message may be output if JP1/Base on the host-name host stops during command execution, or if command execution takes a long time.

S:
Suspends command response processing because connection with the host was released. If command execution takes a long time, temporarily releases the connection but executes the command normally.

O:
If the system is not executing a command that takes a long time to be executed, determine whether JP1/Base has stopped on host-name host. If JP1/Base is running, check the network for problems.

KAVB2053-E

Socket bind error. An attempt to bind the socket on host [host-name] to the port number [port-number] and address [IP-address] has failed. [internal-message]

An attempt to bind to the output IP address failed.

S:
Unable to start using the output IP address; or does not execute the command.

O:
Determine whether the output IP address is available.

KAVB2054-E

Socket listen error. An attempt to listen to the host [host-name] has failed. [internal-message].

An attempt to perform a listen system call failed.

S:
Unable to receive communications using the output IP address of the host.

O:
Determine whether a resource shortage occurred.

KAVB2055-E

Cannot execute the command, since the host name [host-name] cannot be resolved.

The IP address of the host name cannot be resolved.

S:
Does not execute the command.

O:
Take the necessary steps so that the address can be resolved.

KAVB2056-E

The request [ID] from host [host-name] was invalid, and has been rejected.

Invalid data was received.

S:
Does not execute the command.

O:
Determine whether there is an invalid packet flow in the communication environment.

KAVB2057-E

Cannot send the execution results of the command [command-name] from the host [host-name]. [internal-message].

An attempt to send the command execution results failed.

S:
Does not send the command execution results.

O:
Determine whether a resource shortage occurred in the command execution host.

KAVB2058-E

The command request has been rejected, since the command queueing limit has been exceeded.

A command execution request exceeded the command queuing limit.

S:
Does not execute the command.

O:
Use the jcocmddef command to increase the command queuing limit.
If the same message appears after the command queuing limit is increased, perform the following:
  • Reduce requests for commands that require a long execution time.
  • Reduce the number of requested commands.

KAVB2059-E

Due to an internal error, an attempt to execute the command [command-name] has failed. [internal-message].

An attempt to execute a system call failed during command execution at the command execution host.

S:
Does not execute the command.

O:
Determine whether a resource shortage occurred at the command execution host.

KAVB2060-E

An internal error occurred while the results were being received.

An error occurred during transfer of the command execution results between internal processes in the command execution host.

S:
Does not display the command execution results.

O:
Determine whether a resource shortage occurred in the command execution host.

KAVB2061-E

Due to an internal error, the command request [command-name] has been rejected.

An error occurred during transfer of a command request between internal processes in the command execution host.

S:
Does not execute the command.

O:
Determine whether a resource shortage occurred in the command execution host.

KAVB2062-E

The command [command-name] cannot be sent from host [host-name] to host [host-name].

An error occurred while sending the command execution request.

S:
Does not execute the command.

O:
Determine whether a resource shortage occurred in the destination host.

KAVB2063-I

Failed to acquire the port number of [service-name]. The default port number is used. [internal-message].

The port number could not be acquired.

S:
Uses the default port to start.

O:
Check the port number of the jp1imcmda or jp1imcmdc service name in the services file.

KAVB2064-E

Error in writing execution results to Command execution log.

An error occurred during an attempt to write to the command execution log file.

S:
Does not save the command execution results in the command execution log file.

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.
  • Are sufficient system resources allocated?
  • Is the OS operating normally?
  • Has a disk space shortage occurred at the command execution log file output destination?
  • Are permissions for the command execution log file output destination appropriate?
  • It is possible that the command execution log file has been corrupted. For details about how to check the command execution log file for damage and how to recover the command execution log file, see 9.5(4) Actions to take when a command execution log file is damaged in the manual Job Management Partner 1/Integrated Management - Manager Administration Guide.
    If the command execution log file is normal, execute the data collection tool of JP1/IM, and then contact a system administrator.

KAVB2065-W

Failed to load the Environment file (file-name).

An attempt to read the environment variable file failed.

S:
Executes the command but does not enable the environment variable file settings.

O:
Make sure that a folder name or directory name is not specified for the file name and that the access permissions are correct.

KAVB2066-I

A process under execution was deleted. command=[command-name], pid=[process-ID].

The command was deleted successfully.

KAVB2067-I

A process under queuing was deleted. command=command-name

A queued command was deleted.

KAVB2068-E

The [command-name] command could not be executed. (maintenance-information)

The command could not be executed because an error occurred.

S:
Does not execute the command.

O:
The maintenance information is in the form of termination-code:error-information. Based on this information, check the following items:
  • When termination-code is 10000, or termination-code is between 10011 and 10099:
    Determine whether a resource shortage occurred in the command execution host.
  • When a signal is output for error-information:
    In the command execution host, determine whether another process has issued the signal.
If the cause is other than the above or the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2069-E

command-name was rejected because forward transmission processing could not be performed. (host-name)

command-name being transmitted was rejected because commands being transmitted are accumulated in command execution control of host-name and transmitting additional commands could cause transmission processing problems.

S:
Does not execute the command.

O:
Determine whether a network problem occurred between host-name host and the execution host.

KAVB2070-W

Acquisition of the command execution results was interrupted because the specified maximum of xx lines was reached.

Acquisition of command execution results was aborted because the maximum number of lines was acquired.

S:
Executes command processing without acquiring execution results.

KAVB2071-W

In target-host-name, the number of queued commands requested from source-host-name has exceeded the threshold (xx).

In target-host-name, the number of queued automated action requests from source-host-name reached the threshold [xx entries]. It is possible that automated action from source-host-name is delayed.

S:
Continues processing.

O:
Check the following items:
  • Determine whether a significant number of automated actions have occurred on source-host-name. If so, consider suppressing automated actions, or increase the number of commands to be executed concurrently.
  • Determine whether there are remaining commands that have not been terminated on target-host-name. If so, use the jcocmdshow or jcocmddel command to terminate the commands.

KAVB2072-I

In target-host-name, the number of queued commands requested from source-host-name has become 0.

On target-host-name, the number of queued automated action requests from source-host-name is 0.

S:
Continues processing.

KAVB2100-I

[host-name:JP1-user-name] Command execution started.

Execution of the command started.

KAVB2101-I

[host-name:JP1-user-name] Command execution ended normally.

Execution of the command ended.

KAVB2102-E

[host-name:JP1-user-name] Command execution ended abnormally.

Execution of the command ended abnormally.

S:
Stops command execution.

O:
Refer to the error message displayed in the Execute Command window, and take the corrective action given for that message.

KAVB2103-E

An attempt to send a command execution operation event failed. (ret = [return-code])

An attempt to send a command execution operation event failed.

S:
Stops sending the event and continues processing.

O:
Make sure that Event Service is running.

KAVB2200-E

The [option] option is invalid.

The option specified by the command line is invalid.

S:
Suspends command processing.

O:
Correct the syntax, and then re-execute the command.

KAVB2201-E

The [option] option is defined more than once.

The specified option is duplicated.

S:
Suspends command processing.

O:
Eliminate the duplication of the option, and then re-execute the command.

KAVB2202-E

The value for the [option] option is not specified.

The value is not specified for the option.

S:
Suspends command processing.

O:
Correct the syntax, and then re-execute the command.

KAVB2203-E

Specify between 1 and number-of-bytes bytes for Connected Host | Logical Host | Source Host Name.

The range of values specified by the option is invalid.

S:
Suspends command processing.

O:
Check the length of the following host names based on the information given in the message:
  • Connected Host: Host name specified by the -s option
  • Logical Host: Host name specified by the -h option
  • Source Host Name: Host name specified by the -ph option

KAVB2204-E

The number of arguments is invalid.

The number of arguments is too large or too small.

S:
Suspends command processing.

O:
Correct the syntax, and then re-execute the command.

KAVB2205-E

jcocmdshow was interrupted.

Command execution was interrupted.

S:
Suspends command processing.

O:
The command was interrupted by a user instruction. If necessary, re-execute the command.

KAVB2206-E

Super user privilege is required to execute the command.

The user executing the command does not have Administrator permissions.

S:
Suspends command processing.

O:
Execute the command as a user with Administrator or root permissions.

KAVB2207-E

The specified logical host [host-name] does not exist.

The logical host value is invalid.

S:
Suspends command processing.

O:
Check the logical host name specified by -h.

KAVB2208-E

The specified connected host [host-name] is unknown.

The name of the connected host does not exist.

S:
Suspends command processing.

O:
Check the name of the connected host specified by -s.

KAVB2209-E

An error occurred during retrieval of host information for the specified logical host [host-name].

The logical host name is invalid or does not exist.

S:
Suspends command processing.

O:
There is a problem in the common definition information settings of the logical host. Check the logical host settings, and, if necessary, reconfigure the logical host.

KAVB2210-E

No response has been received from the connected host [host-name].

The specified connected host did not respond.

S:
Suspends command processing.

O:
  • Make sure that JP1/Base is running on the connected host.
  • Make sure that the specified host exists.
  • Make sure that network communication with the connected host is possible.

KAVB2211-I

No commands exist in the command execution control for the specified request.

The command specified in command execution control does not exist.

KAVB2212-E

Memory is insufficient at the jcocmdshow command executing host.

A memory allocation error occurred.

S:
Suspends command processing.

O:
Resolve the memory shortage, and then retry the operation.

KAVB2213-E

The maximum number of connections has been exceeded.

The number of connections exceeded the maximum number of available connections.

S:
Suspends command processing.

O:
The maximum number of available connections was exceeded at the connected host. Wait awhile, and then retry the operation.

KAVB2214-E

Processing at the connected host has been interrupted.

The adapter command on the connected host stopped due to an interruption.

S:
Suspends command processing.

O:
The command was interrupted at the connected host. Re-execute the command.

KAVB2215-E

Command execution control is not responding at the connected host.

The adapter command at the connected host did not respond.

S:
Suspends command processing.

O:
Make sure that JP1/Base is running on the connected host.

KAVB2216-E

An error during access to command execution control at the connected host.

The adapter command of the logical host is not operating normally.

S:
Suspends command processing.

O:
There is a problem with the logical host settings of the connected host. Reconfigure the logical host of the connected host.

KAVB2217-E

The connected host environment is invalid.

The adapter command on the connected host is not operating due to a lack of permission.

S:
Suspends command processing.

O:
Make sure that JP1/Base is running on the connected host in the administrator role.

KAVB2218-E

Invalid protocol data was received from command execution control.

The adapter command on the connected host received invalid data.

S:
Suspends command processing.

O:
Invalid data was included during communication. Retry the operation.

KAVB2221-E

The contents of the configuration definition are corrupted. "[key]\\JP1BASE" key does not exist.

The common definition key JP1BASE does not exist.

S:
Suspends command processing.

O:
The environment is invalid. Re-install JP1/Base.

KAVB2222-W

Log directory information from the configuration definition under logical host [host-name] could not be retrieved. Processing will continue without logging messages.

An attempt to acquire the log directory from the common definition information failed.

S:
Continues command processing without outputting the log.

KAVB2223-W

Log settings information from the configuration definition under logical host [host-name] could not be retrieved. Processing will continue without logging messages.

An attempt to acquire log output settings from the common definition information failed.

S:
Continues command processing without outputting the log.

KAVB2224-W

An attempt to initialize the HNTR library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 failed.

S:
Continues command processing without outputting the log.

KAVB2225-E

Invalid protocol data was received from command execution control.

Invalid data was received from command execution control.

S:
Suspends command processing.

O:
Invalid data was included during communication. Retry the operation.

KAVB2227-I

jcocmdshow started.

The jcocmdshow command started.

KAVB2228-I

jcocmdshow terminated. return code: [return-code].

The jcocmdshow command stopped.

KAVB2229-E

Invalid source host name

An invalid character is contained in the argument specified by the -ph option.

S:
Suspends command processing.

O:
Check the argument specified using the -ph option.

KAVB2230-E

The value for the -state option [argument] is invalid.

Characters other than r or q are used in the -state option.

S:
Suspends command processing.

O:
Check the argument specified using the -state option.

KAVB2231-E

The maximum number of connections at the connected host has been exceeded. Wait a while, and then retry.

The maximum number of allowable concurrent connections was exceeded.

O:
The maximum number of connections has been reached. Wait awhile, and then retry the operation.

KAVB2232-E

An error occurred during initialization of communication with the plug-in service at the jcocmdshow command executing host.

An attempt to initialize the plug-in service API failed.

S:
Suspends command processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
  • Is there a problem in the network with the host specified by the -s option?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2233-E

An error occurred in the plug-in service on the jcocmdshow command executing host.

An invalid parameter was passed to the plug-in API, or an unexpected error occurred.

S:
Suspends command processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
  • Is there a problem in the network with the host specified by the -s option?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2234-E

An error occurred while a request was being processed on the connected host.

The environment of the connected host is invalid.

S:
Suspends command processing.

O:
Reconfigure JP1/Base on the connected host.

KAVB2235-E

An error occurred while data was being received from command execution control.

The following error occurred in the plug-in API:

  • Data reception error

S:
Suspends command processing.

O:
Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2236-E

An error occurred during data transmission to command execution control.

The following error occurred in the plug-in API:

  • Data transmission error

S:
Suspends command processing.

O:
  • Make sure that JP1/Base is running on the connected host.
  • Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2237-E

The connected host version does not support this command.

The following error(s) occurred in the plug-in API:

  • Invalid version
  • Lack of required components

S:
Suspends command processing.

O:
Make sure that the version of JP1/Base on the connected host is 07-00 or later.

KAVB2238-E

The connection with the connected host terminated. Try again.

The following error occurred in the plug-in API:

  • Connection was ended.

S:
Suspends command processing.

O:
Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2239-E

A network connection with the connected host could not be established.

The following error(s) occurred in the plug-in API:

  • Connection error
  • The plug-in service is busy.

S:
Suspends command processing.

O:
Check the status of the network with the connected host, and make sure that the settings allow normal operation. If there are no network problems, wait awhile, and then retry the operation.

KAVB2240-E

The environment is invalid on the jcocmdshow command executing host.

The following error(s) occurred in the plug-in API:

  • Syntax error in settings file
  • Unable to find settings file
  • Unable to find command definition information of logical host

S:
Suspends command processing.

O:
The common definition information of the host that executed the jcocmdshow command or the settings in the plug-in service settings file were invalid. Re-install JP1/Base.

KAVB2241-E

Invalid protocol data was transmitted through the plug-in service.

The following error occurred in the plug-in API:

  • Invalid data was received.

S:
Suspends command processing.

O:
Invalid data was included during communication. Retry the operation.

KAVB2242-E

JP1/Base does not support this command.

The following error occurred in the plug-in API:

  • Unable to find the plug-in

S:
Suspends command processing.

O:
Make sure that the version of JP1/Base on the connected host is 07-00 or later. If the version is not the problem, it is possible that the environment is invalid. Re-install JP1/Base to recover from the error.

KAVB2243-E

A timeout occurred during communication with the plug-in service. Try after a while.

The following error(s) occurred in the plug-in API:

  • A time-out request occurred.
  • The plug-in service is busy.
  • Connection to the plug-in service failed.

S:
Suspends command processing.

O:
Wait awhile, and then retry the operation.

KAVB2244-E

The connection with connected host terminated.

The following error occurred in the plug-in API:

  • Connection with the plug-in service was ended.

S:
Suspends command processing.

O:
Make sure that JP1/Base is running on the connected host.

KAVB2245-E

A timeout occurred during communication with the plug-in service.

The following error occurred in the plug-in API:

  • A time-out request occurred.

S:
Suspends command processing.

O:
Wait awhile, and then retry the operation.

KAVB2246-E

Failed to open catalog file /opt/jp1base/lib/nls/C/jp1BsCmdShow.cat

An attempt to open the catalog file failed.

S:
Does not execute the jcocmdshow command.

O:
In UNIX, check the items below. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
  • Does the catalog file exist under the /opt/jp1base/lib/nls directory?
  • Is there read permission for the catalog and path to /opt/jp1base/lib/nls?

KAVB2247-W

Unable to get message from the catalog file

The message could not be acquired from the catalog file. It is possible that the catalog file is corrupted.

S:
Does not output the message.

O:
Change the LANG environment variable, and then re-execute the command. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2248-E

Memory allocation failed due to insufficient memory.

An attempt to allocate an area of memory failed due to a memory shortage.

S:
Suspends command processing.

O:
Resolve the memory shortage, and then retry the operation.

KAVB2249-E

catopen() API failed. Error number: error-code

An attempt to open the catalog file failed.

S:
Does not execute the jcocmdshow command.

O:
In UNIX, check the items below. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
  • Does the catalog file exist under the /opt/jp1base/lib/nls directory?
  • Is there read permission for the catalog and path to /opt/jp1base/lib/nls?

KAVB2250-W

An attempt to initialize an individual trace log has failed. Processing will continue without logging messages.

An attempt to initialize log output processing failed.

S:
Continues processing without outputting the log.

KAVB2251-W

An attempt to initialize an integrated trace log has failed. Processing will continue without logging messages.

An attempt to initialize log output processing failed.

S:
Continues processing without outputting the log.

KAVB2252-E

The specified host to be connected is not subject to configuration management.

A connection could not be established to the host because the host is not being managed.

S:
Suspends command processing.

O:
Check the name of the connected host specified by the -s option.

KAVB2253-E

A reply was not returned during communication processing at the host where the jcocmdshow command was executed.

An attempt to communicate with the connected host failed during communication processing.

S:
Suspends command processing.

O:
At the host where the command was executed, execute the jbs_spmd_status command to determine whether all services are running, and then retry the operation.

KAVB2276-E

The [option] option is invalid.

The option specified by the command line is invalid.

S:
Suspends command processing.

O:
Correct the syntax, and then re-execute the command.

KAVB2277-E

The [option] option is defined more than once.

The specified option is duplicated.

S:
Suspends command processing.

O:
Eliminate the duplication of the option, and then re-execute the command.

KAVB2278-E

The value for the [option] option is not specified.

A value is not specified for the option.

S:
Suspends command processing.

O:
Correct the syntax, and then re-execute the command.

KAVB2279-E

Specify between 1 and [number-of-bytes] bytes for Connected Host.

The value specified for the option is outside the valid range.

S:
Suspends command processing.

O:
Execute the command using a correct value.

KAVB2280-E

The number of arguments is invalid.

The number of arguments is too large or too small.

S:
Suspends command processing.

O:
Correct the syntax, and the re-execute the command.

KAVB2281-E

jcocmddel was interrupted.

An interruption occurred during command execution.

S:
Suspends command processing.

O:
The command was interrupted by a user instruction. If necessary, re-execute the command.

KAVB2282-E

Superuser privilege is required to execute the command.

The user executing the command does not have Administrator permissions.

S:
Suspends command processing.

O:
Execute the command as a user with Administrator or root permissions.

KAVB2283-E

The specified logical host host-name does not exist.

The logical host value is invalid.

S:
Suspends command processing.

O:
Check the logical host name specified by -h.

KAVB2284-E

The specified connected host [host-name] is unknown.

The name of the connected host does not exist.

S:
Suspends command processing.

O:
Check the name of the connected host specified by -s.

KAVB2285-E

The specified logical host [host-name] does not exist.

The logical host name is invalid or does not exist.

S:
Suspends command processing.

O:
There is an error in the common definition information settings of the logical host. Check the logical host settings, and, if necessary, reconfigure the logical host.

KAVB2286-E

No response has been received from the connected host [host-name].

The specified connected host did not respond.

S:
Suspends command processing.

O:
  • Make sure that JP1/Base is running on the connected host.
  • Make sure that the specified host exists.
  • Make sure that network communication can be established with the connected host.

KAVB2287-I

No command exists in command execution control.

The command specified in command execution control does not exist.

KAVB2288-E

Memory is insufficient on the jcomddel command executing host.

A memory allocation error occurred.

S:
Suspends command processing.

O:
Resolve the memory shortage, and then retry the operation.

KAVB2289-E

<CommandID(S)>/ALL option is required.

The command ID or ALL option is not specified.

S:
Suspends command processing.

O:
Specify either the command ID or ALL option (if you wish to delete all).

KAVB2290-E

Command ID(S) cannot be specified with the ALL option.

Both the command ID and ALL option are specified at the same time.

S:
Suspends command processing.

O:
Specify either the command ID or ALL option (if you wish to delete all) but not both.

KAVB2291-Q

Do you want to delete the specified command ID(S) [Y/y or N/n] ->

Confirms that it is OK to delete the command.

S:
Stops command processing and waits for a response.

O:
Enter Y or y to continue processing. Enter N or n to suspend processing.

KAVB2292-I

The user cancelled the deletion of command(S).

The jcocmddel command was suspended.

KAVB2293-I

The command(S) were deleted successfully from command execution control.

The specified command ID was deleted successfully.

KAVB2294-W

The command ID(S) [command-ID] do not exist in command execution control.

The specified command does not exist.

S:
Cannot find the specified command ID.

KAVB2295-E

Invalid command ID. Specify a command ID between 0 and 4294967295.

An invalid command ID is specified.

S:
Suspends command processing.

O:
Specify a command ID that is within the allowed range.

KAVB2296-E

The maximum number of connections on the connected host has been exceeded.

The number of connections exceeded the maximum number of connections available on the connected host.

S:
Suspends command processing.

O:
Wait awhile, and then retry the operation.

KAVB2297-E

Processing on the connected host was interrupted.

The adapter command stopped due to an interruption at the connected host.

S:
Suspends command processing.

O:
The command was interrupted at the connected host. Re-execute the command.

KAVB2298-E

Command execution control is not responding on the connected host.

The adapter command is not responding on the connected host.

S:
Suspends command processing.

O:
Make sure that JP1/Base is running on the connected host.

KAVB2299-E

An error occurred during access to command execution control on the connected host.

The adapter command on the logical host is not operating normally.

S:
Suspends command processing.

O:
There is an error in the logical host settings of the connected host. Reconfigure the logical host of the connected host.

KAVB2300-E

The connected host environment is invalid.

The adapter command on the connected host is not operating due to a lack of permission.

S:
Suspends command processing.

O:
Make sure that JP1/Base is running in the administrator role on the connected host.

KAVB2301-E

Invalid protocol data was received in command execution control.

The adapter command on the connected host received invalid data.

S:
Suspends command processing.

O:
Invalid data was included during communication. Retry the operation.

KAVB2304-E

The contents of the configuration definition are corrupted. The "[key]\\JP1BASE" key does not exist.

The common definition key JP1BASE does not exist.

S:
Suspends command processing.

O:
The environment is invalid. Re-install JP1/Base.

KAVB2305-W

Log directory information from the configuration definition under the logical host [host-name] could not be retrieved. Processing will continue without logging messages.

An attempt to acquire the log directory from the common definition information failed.

S:
Continues command processing without outputting the log.

KAVB2306-W

Log settings information from configuration definition under logical host [host-name] could not be retrieved. Processing will continue without logging messages.

An attempt to acquire the log output settings from the common definition information failed.

S:
Continues command processing without outputting the log.

KAVB2307-W

An attempt to initialize the hntr library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 failed.

S:
Continues command processing without outputting the log.

KAVB2308-E

Invalid protocol data was received from command execution control.

Invalid data was received from command execution control.

S:
Suspends command processing.

O:
Invalid data was included during communication. Retry the operation.

KAVB2310-I

jcocmddel started.

The jcocmddel command started.

KAVB2311-I

jcocmddel terminated. return code: [return-code].

The jcocmddel command stopped.

KAVB2312-W

ID(S) [command-ID] is (are) specified more than once. Processing will continue with unique ID(S).

The command ID is specified more than once.

KAVB2313-E

The maximum number of connections at the connected host has been exceeded. Try after a while.

The maximum number of connections allowed at one time was exceeded.

S:
Ends the connection and suspends processing.

O:
The maximum number of connections was reached. Wait awhile, and then retry the operation.

KAVB2314-E

An invalid command ID was specified.

An invalid command ID was specified.

S:
Suspends command processing.

O:
Specify a command ID value between 0 and 4,294,967,295.

KAVB2316-E

An error occurred during initialization of communication with the plug-in service on the jcocmddel command executing host.

An attempt to initialize the plug-in service API failed.

S:
Suspends command processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
  • Is there a problem in the network with the host specified by the -s option?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2317-E

An error occurred in the plug-in service on the jcocmddel command executing host.

An invalid parameter was passed to the plug-in API, or an unexpected error occurred.

S:
Suspends command processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
  • Is there a problem in the network with the host specified by the -s option?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2318-E

An error occurred during request processing on the connected host.

The environment of the connected host is invalid.

S:
Suspends command processing.

O:
Reconfigure JP1/Base on the connected host.

KAVB2319-E

An error occurred during data reception from command execution control.

The following error occurred in the plug-in API:

  • Data reception error

S:
Suspends command processing.

O:
Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2320-E

An error occurred during data transmission to command execution control.

The following error occurred in the plug-in API:

  • Data transmission error

S:
Suspends command processing.

O:
  • Make sure that JP1/Base is running on the connected host.
  • Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2321-E

The connected host version does not support this command.

The following error(s) occurred in the plug-in API:

  • Invalid version
  • Lack of required components

S:
Suspends command processing.

O:
Make sure that the version of JP1/Base on the connected host is 07-00 or later.

KAVB2322-E

Connection with the connected host terminated. Try again.

The following error occurred in the plug-in API:

  • Connection was ended.

S:
Suspends command processing.

O:
Check the status of the network with the connected host, and make sure that the settings allow normal operation.

KAVB2323-E

A network connection with the connected host could not be established.

The following error(s) occurred in the plug-in API:

  • Connection error
  • The plug-in service is busy.

S:
Suspends command processing.

O:
  • Check the status of the network with the connected host, and make sure that the settings allow normal operation.
  • If there are no network problems, wait awhile, and then retry the operation.

KAVB2324-E

The environment is invalid on the jcocmddel command executing host.

The following error(s) occurred in the plug-in API:

  • Syntax error in settings file
  • Unable to find settings file
  • Unable to find common definition information of logical host

S:
Suspends command processing.

O:
The common definition information of the host that executed the jcocmdshow command or the contents of the plug-in service settings file are invalid. Re-install JP1/Base.

KAVB2325-E

Invalid protocol data was transmitted through the plug-in service.

The following error occurred in the plug-in API:

  • Reception of invalid data

S:
Suspends command processing.

O:
Invalid data was included during communication. Retry the operation.

KAVB2326-E

JP1/Base does not support this command.

The following error occurred in the plug-in API:

  • Unable to find the plug-in

S:
Suspends command processing.

O:
Make sure that the version of JP1/Base on the connected host is 07-00 or later. If the version is not the problem, it is possible that the environment is invalid. Re-install JP1/Base to recover from the error.

KAVB2327-E

A timeout occurred during communication with the plug-in service. Try after a while.

The following error(s) occurred in the plug-in API:

  • Request time-out occurred.
  • Plug-in service is busy.
  • Connection to plug-in service failed.

S:
Suspends command processing.

O:
Wait awhile, and then retry the operation.

KAVB2328-E

The connection with the connected host terminated.

The following error occurred in the plug-in API:

  • Connection with plug-in service was ended.

S:
Suspends command processing.

O:
Make sure that JP1/Base is running on the connected host.

KAVB2329-E

A timeout occurred during communication with the plug-in service.

The following error occurred in the plug-in API:

  • Request time-out occurred.

S:
Suspends command processing.

O:
Wait awhile, and then retry the operation.

KAVB2330-E

Failed to open catalog file /opt/jp1base/lib/nls/C/jp1BsCmdDel.cat

An attempt to open the catalog file failed.

S:
Does not execute the jcocmddel command.

O:
In UNIX, determine whether the catalog file exists in the /opt/jp1base/lib/nls directory.

KAVB2331-W

A message could not be acquired from the catalog file.

The message could not be acquired from the catalog file. It is possible that the catalog file is corrupted.

S:
Does not output the message.

O:
Change the LANG environment variable, and then re-execute the command. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2332-E

Memory allocation failed due to insufficient memory.

An attempt to allocate an area of memory failed due to a memory shortage.

S:
Suspends command processing.

O:
Resolve the memory shortage, and then retry the operation.

KAVB2333-E

catopen() API failed. Error number: error-code

An attempt to open the catalog file failed.

S:
Does not execute the jcocmddel command.

O:
In UNIX, determine whether the catalog file exists in the /opt/jp1base/lib/nls directory.

KAVB2334-W

An attempt to initialize an individual trace log has failed. Processing will continue without logging messages.

An attempt to initialize log output processing failed.

S:
Continues processing without outputting the log.

KAVB2335-W

An attempt to initialize an integrated trace log has failed. Processing will continue without logging messages.

An attempt to initialize log output processing failed.

S:
Continues processing without outputting the log.

KAVB2336-E

The specified host to be connected is not subject to configuration management.

The host could not be connected because the host to be connected is not subject to configuration management.

S:
Suspends command processing.

O:
Check the name of the connected host specified by the -s option.

KAVB2337-E

A reply was not returned during communication processing at the host where the jcocmddel command was executed.

An attempt to communicate with the connected host failed during communication processing.

S:
Suspends command processing.

O:
On the host where the command was executed, execute the jbs_spmd_status command to determine whether all services are running, and then retry the operation.

KAVB2339-E

An attempt to delete the commands has failed. Try again.

An error occurred during command deletion processing.

S:
Suspends command processing.

O:
Wait awhile, and then retry the operation.

KAVB2356-E

The value for the logical logical-host-name is invalid.

The logical host value is invalid.

S:
Suspends command processing.

O:
Check the logical host name specified by the -h option.

KAVB2401-I

The logs of commands executed are not displayed for a setup which do not save them.

The command execution log is not saved because it is set up not to be saved.

S:
Continues command processing.

O:
To save the command execution log, execute the following command on the host where JP1/IM - Manager is running:
jcocmddef -actresult ON

KAVB2402-W

[host-name]The execution time of command execution exceeded the regulation value (numeric-value sec)

The execution time of the command being executed exceeds the regulation value.

S:
Continues command execution.

O:
Processing of command execution is taking a long time. Execute the jcocmdshow command to check the details of the command, and execute the jcocmddel command to delete the command being executed.

KAVB2500-E

An attempt to open a catalog file has failed. A default message is used.

An attempt to read the message resource failed.

S:
Suspends processing.

O:
Re-install JP1/Base.

KAVB2501-E

A value is invalid. (option = option-name value)

The displayed option and value are invalid.

S:
Suspends processing.

O:
Specify the correct option and value.

KAVB2502-E

A value is invalid. The option [-host: logical host name (host-name)] is too long.

The logical host name is too long.

S:
Suspends processing.

O:
Specify a logical host name using no more than 255 characters.

KAVB2503-E

The logical host host-name does not exist on this host.

The specified logical host does not exist.

S:
Suspends processing.

O:
Specify an existing logical host name.

KAVB2504-E

The host group file file-name cannot be opened.

The specified host group file cannot be found.

S:
Suspends processing.

O:
Make sure that the host group file exists.

KAVB2505-E

The host group name is not defined.

The host group name is not defined in the host group file.

S:
Suspends processing.

O:
Make sure that the host group name is specified correctly in the host group file.

KAVB2506-E

The format is invalid. (line: line-number)

The format of the host group file is invalid.

S:
Suspends processing.

O:
There is a syntax error in the host group file. Check the following items:
  • Are the characters { and } used correctly in the host group definition?
  • Is more than one host group name specified before the character { in the host group definition?
Correct the syntax error in the host group file, and then retry the operation.

KAVB2507-E

The group name group-name is too long.

The group name specified in the host group file is too long.

S:
Suspends processing.

O:
Specify a group name using no more than 32 characters.

KAVB2508-E

Access permission is lacking.

An access permission error occurred while accessing the common definition.

S:
Suspends processing.

O:
The environment is invalid. Re-install JP1/Base.

KAVB2509-E

The host name host-name is too long.

The host name is too long.

S:
Suspends processing.

O:
Specify a host name using no more than 255 characters.

KAVB2510-E

The value is invalid. The option [-group: group file name (file-name)] is too long.

The host group file name is too long.

S:
Suspends processing.

O:
The group file name can contain a maximum of 1,023 characters. Modify the file name, and then retry the operation.

KAVB2511-E

An error occurred at the API of the common definition. (Access permission was lacking.)

An error occurred while accessing the common definitions.

S:
Suspends processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2512-E

An error occurred at the API of the common definitions. (No entry was found.)

An error occurred while accessing the common definitions.

S:
Suspends processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.

KAVB2513-E

An error occurred at the API of the common definitions. (An invalid parameter was used.)

An error occurred while accessing the common definitions.

S:
Suspends processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2514-E

An error occurred at the API of the common definitions. (An internal error occurred.)

An error occurred while accessing the common definitions.

S:
Suspends processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2515-E

An error occurred at the API of the common definitions. (An initialization error occurred.)

An error occurred while accessing the common definitions.

S:
Suspends processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2516-E

An error occurred at the API of the common definitions. (A logic conflict occurred.)

An error occurred while accessing the common definitions.

S:
Suspends processing.

O:
Check the following items:
  • Are sufficient system resources and memory allocated?
  • Is the OS operating normally?
If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2517-E

Super user privilege is required to execute the command.

The user executing the command does not have sufficient permission.

S:
Suspends processing.

O:
Execute the command as a user with Administrator or root permissions.

KAVB2518-E

The specified directory path (directory-name) is too long.

The specified directory path is too long.

S:
Does not execute the command.

O:
Shorten the length of the path to the directory where the command execution log file is stored.

KAVB2519-E

The specified host name (host-name) is too long.

The specified host name is too long.

S:
Does not execute the command.

O:
Make sure that the specified logical host name is correct.

KAVB2520-E

The specified logical host (host-name) does not exist.

The specified logical host has not been set up.

S:
Does not execute the command.

O:
Make sure that the specified logical host name is correct.

KAVB2521-E

The specified directory (directory-name) does not exist.

The specified directory could not be found.

S:
Does not execute the command.

O:
Check the name of the directory where the command execution log file is stored.

KAVB2522-W

The command-execution log file for the executed command does not exist.

The log file of a command executed in the Execute Command window does not exist.

S:
Does not output the log of the command that was executed in the Execute Command window.

O:
Execute the command in the Execute Command window, and then retry the operation.

KAVB2523-E

The command-execution log file for the executed command cannot be opened.

The log file of a command executed in the Execute Command window could not be opened.

S:
Does not output the log of the command executed in the Execute Command window.

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 the permission for the storage destination of the command execution log file is appropriate.
  • It is possible that the command execution log file is corrupted. For details about how to check the log file for damage and how to recover the command execution log file, see 9.5(4) Actions to take when a command execution log file is damaged in the manual Job Management Partner 1/Integrated Management - Manager Administration Guide.
    If the command execution log file is normal, execute the JP1/IM data collection tool, and then contact a system administrator.

KAVB2524-W

The command-execution log file for the automatic action does not exist.

There is no log file of a command executed by automated action.

S:
Does not output the log of the command executed by automated action.

O:
Execute the automated action, and then retry the operation.

KAVB2525-E

The command-execution log file for the automatic action cannot be opened.

The log file of a command executed by automated action could not be opened.

S:
Does not output the log of the command executed by automated action.

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 the permission for the storage destination of the command execution log file is appropriate.
  • It is possible that the command execution log file is corrupted. For details about how to check the log file for damage and how to recover the command execution log file, see 9.5(4) Actions to take when a command execution log file is damaged in the manual Job Management Partner 1/Integrated Management - Manager Administration Guide.
    If the command execution log file is normal, execute the JP1/IM data collection tool, and then contact a system administrator.

KAVB2526-W

Reading of the command-execution log file was interrupted.

Read processing was suspended because an exclusive operation was performed on the command execution log file by another process.

S:
Suspends output of the command execution log.

O:
Determine whether the following processing was executed, and then re-execute the jcocmdlog command.
  • Execution of automated action
  • Execution of a command in the Execute Command window
  • Execution of another jcocmdlog command

KAVB2527-E

An attempt to read the command-execution log file has failed.

Processing stopped because an error occurred during reading of the command execution log file.

S:
Stops outputting the command execution log.

O:
It is possible that the command execution log file is corrupted. For details about how to check the log file for damage and how to recover the command execution log file, see 9.5(4) Actions to take when a command execution log file is damaged in the manual Job Management Partner 1/Integrated Management - Manager Administration Guide.
If the command execution log file is normal, execute the JP1/IM data collection tool, and then contact a system administrator.

KAVB2528-E

The date is invalid.(date)

There is an error in the specified date/time. Check the following items:

  • Date error: The specified date is not in the calendar.
  • Time error: The specified hour, minute, or second is inappropriate.
    (Hour: 00 to 23, Minute: 00 to 59; Second: 00 to 59)

S:
Does not execute the command.

O:
Specify appropriate values in the date and time format (YYYYMMDDhhmmss), and then retry the operation.

KAVB2529-E

The range specified for the date is invalid.

A date later than the end date is specified as the start date.

S:
Does not execute the command.

O:
Specify a start date that is earlier than the end date, and then retry the operation.

KAVB2530-I

The jcocmdconv command started.

Processing of the jcocmdconv command started.

S:
Executes the command.

KAVB2531-I

The jcocmdconv command terminated. (Return code: return-code)

The jcocmdconv command ended.

S:
Finishes command processing.

KAVB2532-I

The user cancelled the conversion of the command-execution log file.

Processing of the jcocmdconv command was stopped by the user.

S:
Suspends command processing.

KAVB2534-E

The specified option option-name is invalid.

The option specified by the command line is invalid.

S:
Suspends command processing.

O:
Specify the correct option, and then re-execute the command.

KAVB2535-E

The number of arguments is invalid.

The argument of the option is incorrect.

S:
Suspends command processing.

O:
Specify the correct option, and then re-execute the command.

KAVB2536-E

The option option-name is specified more than once.

An option that can only be specified once is specified multiple times.

S:
Suspends command processing.

O:
Specify the correct option, and then re-execute the command.

KAVB2537-E

The value for the option option-name is not specified.

The specified option value is invalid.

S:
Suspends command processing.

O:
Specify the correct option, and then re-execute the command.

KAVB2538-E

The directory does not exist. (directory-path = directory-name)

The specified source or target execution directory does not exist.

S:
Suspends command processing.

O:
Specify the correct directory path, and then re-execute the command.

KAVB2539-E

The specified directory is too long. (directory-path = directory-name)

The specified directory is too long.

S:
Suspends command processing.

O:
Specify the correct directory path, and then re-execute the command.

KAVB2540-E

The specified logical host does not exist. (logical-host-name = logical-host-name)

The logical host name is invalid or does not exist.

S:
Suspends command processing.

O:
There is an error in the common definition information settings of the logical host. Check the logical host settings, and, if necessary, reconfigure the logical host.

KAVB2541-E

The specified logical host name is too long. (logical-host-name = logical-host-name)

The specified logical host name is too long.

S:
Suspends command processing.

O:
Check the logical host name specified by the -h option.

KAVB2542-E

Superuser permissions are required to execute the command.

The user executing the command does not have Administrator permissions.

S:
Suspends command processing.

O:
Execute the command as a user with Administrator or root permissions.

KAVB2543-E

Command execution will now stop because memory is insufficient.

An error occurred during memory allocation.

S:
Suspends command processing.

O:
Stop other processes that are using memory, and then re-execute the command.

KAVB2544-E

Command execution will now stop because disk space is insufficient.

There is insufficient disk space at the executing directory path.

S:
Suspends command processing.

O:
Increase the available disk space, and re-execute the command.

KAVB2545-E

The user does not have access permission for the file file-name.

The command could not be executed because there is no access permission for the command execution log file.

S:
Suspends command processing.

O:
Make sure that there is access permission for the command execution log file.

KAVB2546-E

The jcocmdconv command was interrupted.

Command processing was suspended.

S:
Suspends command processing.

O:
Re-execute the command.

KAVB2547-E

Another jcocmdconv command is already running.

Processing of the jcocmdconv command stopped because another jcocmdconv command is being executed on the same logical host.

S:
Suspends command processing.

O:
Determine whether a jcocmdconv command is already being executed.

KAVB2548-I

The specified file file-name contains no data to be converted.

There is no valid record in the specified execution log file.

S:
Suspends command processing.

KAVB2549-E

The source file file-name could not be deleted.

The specified command execution log file in an older format could not be deleted after file conversion.

S:
Finishes command processing without deleting the execution file.

O:
Make sure that there is access permission for the command execution log file in the older format.

KAVB2550-E

A file with the name of the command-execution log file after conversion (file-name) already exists.

The command could not be executed because the post-conversion command execution log file cannot be found in the specified path.

S:
Suspends command processing.

O:
Delete the command execution log file in the specified path, or specify a different path, and then re-execute the command.

KAVB2551-W

The command-execution log file for the executed command does not exist.

Conversion is not performed because the log of the command in an older format executed in the Execute Command window does not exist.

S:
Does not convert the log file of the command executed in the Execute Command window.

KAVB2552-W

The command-execution log file for the automatic action does not exist.

Conversion is not performed because the command execution log file for automated action does not exist.

S:
Does not convert the command execution log file for automated action.

KAVB2553-Q

Do you want to convert the command-execution log file? [Y/y or N/n] ->

Confirms that it is OK to process the command execution log file.

S:
Stops command processing and waits for a response.

O:
To continue command processing, specify Y or y. To stop command processing, specify N or n.

KAVB2554-Q

Do you want to delete the old-format command-execution log file file-name? [Y/y or N/n] ->

Confirms that it is OK to delete the command execution log file.

S:
Stops command processing and waits for a response.

O:
Specify Y or y to delete the command execution log file in the older format and continue processing. Specify N or n to continue processing without deleting the command execution log file in the older format.

KAVB2555-W

An attempt to initialize the HNTR library has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 failed.

S:
Continues command execution without outputting the log.

KAVB2556-W

An attempt to initialize an individual trace log has failed. Processing will continue without logging messages.

An attempt to initialize an individual trace log failed.

S:
Continues command execution without outputting the log.

KAVB2557-W

An attempt to initialize integrated and individual trace logs has failed. Processing will continue without logging messages.

An attempt to initialize HNTRLib2 failed.

S:
Continues command execution without outputting the log.

KAVB2559-E

The contents of the common configuration definition are corrupted. The logical-host-name\\JP1BASE key does not exist.

The common definition key JP1BASE does not exist.

S:
Suspends command processing.

O:
The environment is invalid. Re-install JP1/Base.

KAVB2560-W

Log directory information could not be obtained from the common configuration definition of the logical host logical-host-name. Processing will continue without logging messages.

An attempt to obtain log directory information from the common definition information failed.

S:
Executes command processing without outputting the log.

KAVB2561-W

Log settings information could not be obtained from the common configuration definition of the logical host logical-host-name. Processing will continue without logging messages.

An attempt to obtain log settings information from the common definition information failed.

S:
Executes command processing without outputting the log.

KAVB2563-E

An attempt to get user input has failed.

An attempt to obtain user confirmation from standard output failed.

S:
Suspends command processing.

O:
Re-execute the command. If the problem cannot be resolved by re-executing the command, contact a system administrator.

KAVB2564-E

An attempt to initialize the common definition information has failed.

An attempt to initialize the common definition information failed.

S:
Suspends command processing.

O:
Make sure that the product is installed correctly. If the problem cannot be resolved, contact a system administrator.

KAVB2565-E

An error occurred during command processing.

One of the following errors occurred during processing:

  • Unable to read common definition information
  • Unable to open or read the executive file
  • Failed to create or delete the lck file used during processing

S:
Suspends command processing.

O:
Execute the Jischk command to determine whether the command execution log file is corrupted. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2566-E

Execute the command from the administrator console.

The command must be executed on the administrator console.

S:
Terminates command processing.

O:
Re-execute the command on the administrator console.

KAVB2600-I

New [process-name] Process with PID:[process-ID] is created.

The process name and process ID were created.

KAVB2605-E

The request to execute the command was rejected because the number of connected hosts to be managed has reached the maximum. (host = host-name)

The number of connections between managed hosts exceeded the maximum number that can be processed safely.

S:
Rejects the command execution request.

O:
Execute the jcocmdshow and jcocmddel commands to determine the number of commands currently being executed, and delete any unnecessary commands.

KAVB2606-E

The automatic-action request command-name was rejected because the maximum number of processing requests was exceeded. (host that made the execution request = host-name, process = process-name, pid = process-ID)

The number of commands being executed exceeded the maximum number that can be processed safely. The automated action request will not be processed until the number of commands being executed is reduced to less than the maximum set by the system.

S:
Ignores the automated action request.

O:
  • Execute the jcocmdshow and jcocmddel commands to determine the number of commands currently being executed, and delete any unnecessary commands.
  • Make sure that the network connection to the execution host is functioning.

KAVB2607-E

The command-execution request command-name was rejected because the maximum number of processing requests was exceeded. (host that made the execution request = host-name, process = process-name, pid = process-ID)

The number of commands being executed exceeded the maximum number that can be processed safely. The automated action request will not be processed until the number of commands being executed is reduced to less than the maximum set by the system.

S:
Ignores the command execution request.

O:
  • Execute the jcocmdshow and jcocmddel commands to determine the number of commands currently being executed, and delete any unnecessary commands.
  • Make sure that the network connection to the execution host is functioning.

KAVB2608-E

The process process-name with the pid process-ID terminated abnormally. (Return code: return-code)

The process stopped abnormally due to a system error.

S:
If the process name is any of the following, the system terminates the command execution control abnormally:
  • jcocmd
  • jcocmdexe
  • jcocmdcom
If the process name is the following, stops subsequent command processing of each client:
  • jcocmdapi

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.
  • Is JP1/Base installed correctly?
  • Is the OS operating normally?

KAVB2609-I

The process process-name with the pid process-ID has started.

process-name process started.

KAVB2610-I

The process process-name with the pid process-ID finished normally.

process-name process ended normally.

KAVB2611-E

An attempt to create the process process-name has failed.

An attempt to create the process failed.

S:
Could not start the process due to a system restriction or internal error.

O:
Make sure that sufficient system resources are allocated. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KAVB2613-E

An attempt to allocate memory has failed. (process = process-name, pid = process-ID)

An attempt to allocate memory failed.

S:
Continues processing.

O:
Stop other processes that are using memory, and then re-execute the command.

KAVB2614-E

An attempt to load the message file has failed.

An attempt to open the catalog file failed.

S:
Terminates command execution control.

O:
Make sure that the following files exist. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
  • In Windows: message DLL file (Jcocmdmsg.dll)
  • In UNIX: message catalog file (Jcocmdmsg.cat)

KAVB2615-E

An attempt to execute the command command-name failed due to a memory shortage. (error code = error-code)

An attempt to execute the command failed due to a memory shortage.

S:
Does not execute the command.

O:
Check the following item. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
  • Are sufficient memory and system resources allocated to execute the command?

KAVB2616-E

An attempt to execute the command command-name has failed. (pid = process-ID). (internal-message)

An attempt to execute the command failed for a reason other than a nonexistent command or a lack of resources.

S:
Does not execute the command.

O:
Check the following item. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
  • Is there appropriate permission to execute the command?

KAVB2618-E

An internal error occurred while processing the results.

An error occurred during processing of the command execution results. This error occurs on the host that requests command execution.

S:
Does not output the command execution result log to the ISAM database.

O:
Check the following item. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
  • Are sufficient resources allocated on the host that requests command execution?

KAVB2619-E

An attempt to initialize the log has failed. (Function name: function-name, error code = error-code)

An attempt to initialize log output failed while running the process due to one of the following reasons:

  • Unable to find the common definition parameter, or the parameter is incorrect.
  • A large number of processes are being executed concurrently.

S:
Continues command execution control processing without outputting the log.

O:
Check the following item. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
  • Reduce the number of commands that are being executed concurrently.

KAVB2620-E

An error occurred during startup of the process process-name. (internal-message)

An error occurred while starting the service due to one of the following reasons:

  • The length of the JP1_HOSTNAME environment variable is 256 characters or more.
  • Insufficient resources at the time of process startup.
  • An internal error occurred while starting the service.

S:
Terminates the service abnormally.

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.
  • Is the length of the environment variable 255 characters or fewer?
  • Are sufficient memory and system resources allocated to execute the command?

KAVB2621-E

An attempt to acquire the message from the message file has failed.

An attempt to acquire the message from the catalog file failed.

S:
Does not output the message.

O:
Make sure that the following files exist. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.
  • In Windows: message DLL file (Jcocmdmsg.dll)
  • In UNIX: message catalog file (Jcocmdmsg.cat)

KAVB2623-E

The command cannot be forwarded to the host host-name because the command length is numeric-value bytes or more. This length is not supported by the earlier JP1/Base version on the host. (process = process-name, pid = process-ID).

The version of JP1/Base installed on the execution host does not support the length of the specified command.

S:
Does not execute the command.

O:
Check the version of JP1/Base on the host specified as the execution host for the command. JP1/Base version 08-00 or later must be installed.

KAVB2627-E

The jcocmdconv command is accessing the command execution log file.

The jcocmdapi process was started during execution of the jcocmdconv command.

S:
Stops the jcocmdapi process.

O:
Determine whether the jcocmdconv command was executed. The jcocmdconv command must be executed while JP1/Base is in stop status.

KAVB2628-E

Reception of the command was rejected because it exceeds the maximum length of 4096 bytes.

A command request that exceeds 4,096 bytes was received.

S:
Does not execute the command.

O:
Check the length of the command specified in the Execute Command window or a command specified by automated action.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.