KNAN22846-E

A command ended abnormally.

S:

Stops the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

• An error occurred while writing to a CSV file.

• An error occurred while opening a CSV file.

• Operations cannot be performed on the file.

  Check the following items, and then retry the operation.

  • Is there sufficient memory?

  • Does the file exist?

  • Is the file access permission configured correctly?

  • Has the file been opened (locked) by another application?

• An attempt to read the common definition parameter has failed.

  The common definition information is not configured. Make sure that the configuration is correct.

  If operating in a cluster environment, and if the command is executed with the -h option, make sure that the logical host name is correct.

  Also make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

• An error occurred while opening a temporary CSV file.

  In Windows, make sure that the tmp directory exists.

  In UNIX, make sure that the tmp directory exists in /var/opt/jp1imm/, and that the user has read and write permissions for the tmp directory.

  If operating in a cluster environment, check the following items:

  • Does the defined log directory exist below the JP1IMM directory on the shared disk?

  • Is the common disk mounted?

  • Is there read and write permission?

  If the command is executed with the -h option, make sure that the command was issued by the primary host.

• An invalid node ID has been specified for a new node.

  The file specified for IMCS_ExportFile is invalid. Specify a file that was output by the jcsdbexport command.

• Creation of the jcfallogtrap process failed.

  If the OS of the manager host is Windows, check the IM host account specified in the system common settings. If the OS is UNIX, check the OS settings related to startup of processes.

• The specified command option is invalid.

  An incorrect startup option is specified. From IM Configuration Management - View, check the following items for the startup option:

  • Is the maximum number of monitored log files exceeded?

  • Can the option and its value be specified with additional options?

• The specified command option is invalid.

• The JP1/Base command arguments are invalid.

  An incorrect startup option is specified. From IM Configuration Management - View, check the following items for the startup option:

  • Can the option and its value be specified with additional options?

• JP1/Base command execution error

  Check the JP1/Base environment.

  Check whether the JP1/Base LogTrap service or daemon has stopped or restarted. If the JP1/Base LogTrap service or daemon has stopped, start it and then start or restart all the remote monitoring profiles. If the JP1/Base LogTrap service or daemon has restarted, stop all the remote monitoring profiles, and then start or restart them.

• An internal error occurred.

• Communication with the remote monitoring process failed.

• The format of the management file is invalid.

  Use the data collection tool to collect data, and then contact a system administrator.

If the problem cannot be resolved using the above methods, use the data collection tool to collect data, and then contact a system administrator.