Job Management Partner 1/Integrated Management - Manager Administration Guide

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

9.5 Corrective actions

This section explains how to correct the problems that can generally be anticipated.

Table 9-19 Problems that can generally be anticipated

No. Problem description
1 You cannot log on from JP1/IM - View.
2 The definition menu is not displayed in the Event Console window.
3 You cannot execute a command.
4 The command execution log file is damaged.
5 Unknown is displayed as the automated action execution status.
6 An automated action is delayed.
7 The monitored object database is damaged.
8 The monitored object database cannot be unlocked.
9 KAVB5150-W is displayed in the detailed information (message) for the action result.
10 Either the JP1/IM - Central Scope version or the JP1/IM - View version is old.
11 Many JP1 events occurred for which correlation events were generated.
12 Correlation events cannot be displayed in JP1/IM - View.
13 The JP1/IM - View window cannot be displayed after you have logged on to JP1/IM - View.
14 Command execution or a batch file executed in an automated action does not terminate normally (Windows only).
15 Processing of JP1 events received by JP1/IM - Manager (JP1/IM - Central Scope) is delayed.
16 No JP1 event is displayed in the Event Console window.
17 Status cannot be changed.
18 An event search cannot be performed.
19 Memo entries cannot be set up.
20 The IM database cannot be terminated.
21 You cannot connect to the IM database.
22 JP1/IM - Manager cannot be uninstalled.
23 An error message indicating an invalid port number is issued when the IM database is set up.
24 IM database setup fails.
25 The setup information file is output as invalid during IM database setup.
26 The IM database cannot be started. Or, database-related commands cannot be executed.
27 IM Configuration Management failed to collect host information.
28 IM Configuration Management failed to apply the system hierarchy.
29 IM Configuration Management failed to collect the operation definition file for the log file trap.
30 JP1/IM - View cannot display any of the log file traps that are active.
31 The content of the profile settings file does not match the content of the valid configuration information.
32 Menu items such as Register Host and Edit IM Configuration are disabled in IM Configuration Management - View.
Organization of this section
(1) Actions to take when you cannot log on from JP1/IM - View
(2) Actions to take when the definition menu is not displayed in the Event Console window
(3) Actions to take when you cannot execute a command
(4) Actions to take when a command execution log file is damaged
(5) Actions to take when Unknown is displayed as the automated action execution status
(6) Actions to take when an automated action is delayed
(7) Actions to take when the monitored object database is damaged
(8) Actions to take when the monitored object database cannot be unlocked
(9) Actions to take when KAVB5150-W is displayed in the detailed information (message) for the action result
(10) Actions to take when an earlier version of JP1/IM - Central Scope or JP1/IM - View is being used
(11) Actions to take when many JP1 events occurred for which correlation events were generated
(12) Actions to take when correlation events cannot be displayed in JP1/IM - View
(13) Actions to take when the JP1/IM - View window cannot be displayed after you log on to JP1/IM - View
(14) Actions to take when command execution or a batch file executed in an automated action does not terminate normally (Windows only)
(15) Actions to take when processing of JP1 events received by JP1/IM - Manager (JP1/IM - Central Scope) is delayed
(16) Actions to take when no JP1 event is displayed in the Event Console window
(17) Actions to take when a status cannot be changed
(18) Actions to take when an event search cannot be performed
(19) Actions to take when memo entries cannot be set up
(20) Actions to take when the IM database cannot be terminated
(21) Actions to take when you cannot connect to the IM database
(22) Actions to take when JP1/IM - Manager cannot be uninstalled
(23) Actions to take when an error message indicating an invalid port number is issued after the IM database has been set up
(24) Actions to take when IM database setup fails
(25) Actions to take when the setup information file is output as invalid during IM database setup
(26) Actions to take when the IM database cannot be started or database-related commands cannot be executed
(27) Actions to take when IM Configuration Management fails to collect host information
(28) Actions to take when IM Configuration Management fails to apply the system hierarchy
(29) Actions to take when IM Configuration Management fails to collect the operation definition file for the log file trap
(30) Actions to take when JP1/IM - View cannot display any of the log file traps that are active
(31) Actions to take when the content of the profile settings file does not match the content of the valid configuration information
(32) Actions to take when menu items such as Register Host and Edit IM Configuration are disabled in IM Configuration Management - View

(1) Actions to take when you cannot log on from JP1/IM - View

The actions to take differ depending on the message that is output.

The message KAVB1200-E: Communication error occurred in establishing the connection. is output.

Cause
The following are possible causes:
  • JP1/IM - Manager has not been started.
  • The host name at the connection destination is invalid.

Corrective actions
Take the corrective action that matches the cause.
  • Start JP1/IM - Manager.
  • Make sure that the host name at the connection destination is correct.

The message KAVB0104-E: Failed to authenticate the user. is output.

Cause
The user name or password for the connection destination is invalid.

Corrective action
Make sure that the user name or password for the connection destination is valid.

The message KAVB0109-E: Communication error occurred between the connecting host and the authentication server. is output.

Cause
The authentication server that is set at the connection-destination host has not been started.

Corrective action
Start the authentication server.

The message KNAN20100-E: Address resolution for the specified connection destination host name failed. is output.

Cause
The following are possible causes:
  • The target host name is invalid.
  • The target host has not been started.
  • An error occurred in communications with the target host.

Corrective action
Take the corrective action that matches the cause.
  • Make sure that the target host name is correct.
  • Make sure that the target host has been started.
  • Make sure that there are no communication problems with the target host.

The message KNAN20101-E: A connection to the specified connection destination host cannot be established. Confirm that the server has started up. is output.

Cause
The following are possible causes:
  • The target host name is invalid.
  • The target host has not been started.
  • An error occurred in communications with the target host.

Corrective action
Take the corrective action that matches the cause.
  • Make sure that the target host name is correct.
  • Make sure that the target host has been started.
  • Make sure that there are no communication problems with the connection-target host.

The message KNAN20102-E: A connection to the specified connection destination host cannot be established. is output.

Cause
User authentication failed. The user name or password is invalid.

Corrective action
Make sure the specified user name and password are correct, and then retry the operation.

The message KNAN20103-E: A communication error occurred while sending data. is output.

Cause
A communication error occurred between the connecting host and the authentication server.

Corrective action
Check the following, and then retry the operation:
  • Make sure that the target host name is correct.
  • Make sure that the target host has been started.
  • Make sure that there are no communication problems with the target host.

The message KNAN20104-E: A communication error occurred while receiving data. is output.

Cause
A communication error occurred during an attempt to connect to the host.

Corrective action
Check the following, and then retry the operation:
  • Make sure that the target host name is correct.
  • Make sure that the target host has been started.
  • Make sure that there are no communication problems with the target host.

(2) Actions to take when the definition menu is not displayed in the Event Console window

In the Options menu of the Event Console window, menu-related definitions are disabled.

Cause
The JP1 resource group settings are invalid.

Corrective action
Make sure that in the JP1 resource group settings, the group name JP1_Console is specified for the JP1 resource group of the logged-in JP1 user, and JP1_Console_Admin or JP1_Console_Operator is specified for the permission level.

(3) Actions to take when you cannot execute a command

In the Execute Command window, the message KAVB2027-E: Cannot execute the command. Failed to simulate the user user-name environment. is output.

Cause
The user mapping setting is invalid.

Corrective action
Check the user mapping setting. If it is not set, set it. This setting is required in Windows.
When the host specified for the mapping source server name is using DNS, a domain name must be included in the setting. If the host name is correct but the simulation still fails, check whether DNS is being used.

In the Execute Command window, the message KAVB2031-E: Cannot execute the command. The host (host-name) is not managed by JP1/Console. is output.

Cause
The definition of the configuration definition file is invalid. Or, the executing host name cannot be resolved.

Corrective action
  • Make sure the configuration information is defined in the configuration definition file.
  • Make a correction so that the executing host name can be resolved.
  • If this message is output in an environment in which both a physical host and a logical host are started under Windows, the network settings are insufficient. For details, see the section on building both a physical host environment and a logical host environment on the same host, in the notes related to cluster operation (Windows only) in the Job Management Partner 1/Base User's Guide.

The execution result from the DOS prompt differs from the execution result in the Execute Command window, or it differs from the execution result of an automated action.

Cause
The OS user environment used for execution is invalid.

Corrective action
Enable the -loaduserprofile option of the jcocmddef command. For details, see 7.4.4(3)(c) Environment for command execution in the Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide. See also the chapter that explains commands in the Job Management Partner 1/Base User's Guide.

(4) Actions to take when a command execution log file is damaged

If an operation to write data into a command execution log file is interrupted by, for example, a machine stoppage caused by a power failure, the command execution log file for automated actions or the command execution log file for command execution may be damaged.

In such cases, the following messages are issued:

If any of these messages is output, use the following procedure to check the status of the command execution log file.

  1. Use the procedure in (a) below to check the file that may have been damaged.
  2. If it is not damaged, take the correction action prescribed in each message.
  3. If it is damaged, restored it using the procedure described in (b).
  4. If the file cannot be restored using the procedure in (b), follow the procedure in (c) to delete the command execution log file.

(a) How to check the command execution log files

Checking the command execution log file for automated actions

Checking the command execution log file for command execution

If the Jischk command does not detect file invalidity, the command execution log file is not damaged. If the Jischk command detects file invalidity, follow the procedure described in (b) below to restore the command execution log file.

For details about the Jischk command, see the Job Management Partner 1/Base User's Guide.

(b) How to restore the command execution log files

Restoring the command execution log file for automated actions

Restoring the command execution log file for command execution

(c) How to delete the command execution log files

Deleting the command execution log file for automated actions

When you delete the command execution log file for automated actions, all history on past automated actions is lost. Therefore, if deletion will cause a problem, back up the files. For details, see 1.2.2 Database backup and recovery.

  1. Stop JP1/IM - Manager.

  2. Stop JP1/Base.

  3. Delete the command execution log file.
    Delete the files listed in the table below if you could not restore the command execution log file for automated actions. For details about the command execution log file, see the Job Management Partner 1/Base User's Guide.
    In Windows

    Table 9-20 Locations of files to be deleted (Windows)

    File name Location
    Command execution log file for automated actions
    • Base-path\log\COMMAND\ACTISAMLOGV8.DRF
    • Base-path\log\COMMAND\ACTISAMLOGV8.K01
    • Base-path\log\COMMAND\ACTISAMLOGV8.KDF

    • shared-folder\jp1base\log\COMMAND\ACTISAMLOGV8.DRF
    • shared-folder\jp1base\log\COMMAND\ACTISAMLOGV8.K01
    • shared-folder\jp1base\log\COMMAND\ACTISAMLOGV8.KDF
    Action information file Console-path\log\action\actinf.log
    shared-folder\jp1cons\log\action\actinf.log
    Action host name file Console-path\log\action\acttxt{1|2}.log
    shared-folder\jp1cons\log\action\acttxt{1|2}.log
    In UNIX

    Table 9-21 Locations of files to be deleted (UNIX)

    File name Location
    Command execution log file for automated action
    • /var/opt/jp1base/log/COMMAND/actisamlogv8.DAT
    • /var/opt/jp1base/log/COMMAND/actisamlogv8.K01
    • /var/opt/jp1base/log/COMMAND/actisamlogv8.DEF

    • shared-directory/jp1base/log/COMMAND/actisamlogv8.DAT
    • shared-directory/jp1base/log/COMMAND/actisamlogv8.K01
    • shared-directory/jp1base/log/COMMAND/actisamlogv8.DEF
    Action information file /var/opt/jp1cons/log/action/actinf.log
    shared-directory/jp1cons/log/action/actinf.log
    Action host name file /var/opt/jp1cons/log/action/acttxt{1|2}.log
    shared-directory/jp1cons/log/action/acttxt{1|2}.log

  4. Start JP1/Base.

  5. Start JP1/IM - Manager.

Deleting the command execution log file for command execution

When you delete the command execution log file for command execution, all history on past command execution is lost. Therefore, if deletion will cause a problem, back up the files. For details, see 1.2.2 Database backup and recovery.

  1. Stop JP1/IM - Manager.

  2. Stop JP1/Base.

  3. Delete the command execution log file.
    Delete the files listed in the table below if you could not restore the command execution log file for command execution. For details about the command execution log file, see the Job Management Partner 1/Base User's Guide.
    In Windows

    Table 9-22 Locations of files to be deleted (Windows)

    File name Location
    Command execution log file for command execution
    • Base-path\log\COMMAND\CMDISAMLOGV8.DRF
    • Base-path\log\COMMAND\CMDISAMLOGV8.K01
    • Base-path\log\COMMAND\CMDISAMLOGV8.KDF

    • shared-folder\jp1base\log\COMMAND\CMDISAMLOGV8.DRF
    • shared-folder\jp1base\log\COMMAND\CMDISAMLOGV8.K01
    • shared-folder\jp1base\log\COMMAND\CMDISAMLOGV8.KDF
    In UNIX

    Table 9-23 Locations of files to be deleted (UNIX)

    File name Location
    Command execution log file for command execution
    • /var/opt/jp1base/log/COMMAND/cmdisamlogv8.DAT
    • /var/opt/jp1base/log/COMMAND/cmdisamlogv8.K01
    • /var/opt/jp1base/log/COMMAND/cmdisamlogv8.DEF

    • shared-directory/jp1base/log/COMMAND/cmdisamlogv8.DAT
    • shared-directory/jp1base/log/COMMAND/cmdisamlogv8.K01
    • shared-directory/jp1base/log/COMMAND/cmdisamlogv8.DEF

  4. Start JP1/Base.

  5. Start JP1/IM - Manager.

(5) Actions to take when Unknown is displayed as the automated action execution status

There may be inconsistencies among the files in which automated action execution results are saved (action information file, action host name file, and command execution log file).

If so, you need to delete the files in which automated action execution results are saved. If you delete these files, you will no longer be able to view past automated action execution results. Therefore, if deletion will cause a problem, back up the files. For details, see 1.2.2 Database backup and recovery.

The deletion procedure follows.

  1. Stop JP1/IM - Manager and then stop JP1/Base.
    In the case of a cluster configuration, operate the cluster software to stop the logical hosts. After you have confirmed that they have stopped, mount a shared disk in the shared directory.

  2. Delete the action information file, action host name file, and command execution log file.
    The table below shows the locations of the files to delete.

    In Windows

    Table 9-24 Locations of files to delete (Windows)

    File name Location
    Action information file Console-path\log\action\actinf.log
    shared-folder\jp1cons\log\action\actinf.log
    Action host name file Console-path\log\action\acttxt{1|2}.log
    shared-folder\jp1cons\log\action\acttxt{1|2}.log
    Command execution log file All files under Base-path\log\COMMAND\
    All files under shared-folder\jp1base\log\COMMAND\

    In UNIX

    Table 9-25 Locations of files to delete (UNIX)

    File name Location
    Action information file /var/opt/jp1cons/log/action/actinf.log
    shared-directory/jp1cons/log/action/actinf.log
    Action host name file /var/opt/jp1cons/log/action/acttxt{1|2}.log
    shared-directory/jp1cons/log/action/acttxt{1|2}.log
    Command execution log file All files under /var/opt/jp1base/log/COMMAND/
    All files under shared-directory/jp1base/log/COMMAND/

  3. Start JP1/Base and then start JP1/IM - Manager.
    In the case of a cluster configuration, unmount the shared disk and then operate the cluster software to start the logical hosts.

(6) Actions to take when an automated action is delayed

When the automated action status remains Running.

First, use the jcocmdshow command# to check the command status. The action to take differs depending on the result. The possible cause for each obtained result and the action to take in each case are explained below.

There is a command whose command execution lapse time (ETIME) is too long.

Cause
A command is executing that does not terminate, or that is taking a long time.

Corrective action
Using the jcocmddel command,# delete the command that does not terminate. For details, see 7.1.3 Checking command execution status and deleting a command in this manual, and see 7.4.4(6) Commands for troubleshooting in the Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide.

The message KAVB2239-E: A network connection with the connected host could not be established. is displayed.

Cause
JP1/Base on the executing host stopped while the command was being executed.

Corrective action
Restart JP1/Base on the executing host.
As a means of monitoring JP1/Base, the JP1/Base health check function is available. For details, see 7.4.8 JP1/Base health check function in the Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide.

There are a large number of commands whose execution status (STATUS) is Q.

Cause
The number of automated actions to be executed is too large.

Corrective action
Check the automated actions being executed and reassess the following:
  • Were any unnecessary automated actions set?
  • Is it possible to narrow the JP1 events for which automated actions are to be set?
If there are no unnecessary automated actions, use the jcocmddef command# to increase the number of commands that can be executed simultaneously. For details, see 12.7.6 Command execution environment in the Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide.

#
For details about the jcocmdshow command, jcocmddel command, and jcocmddef command, see the chapter explaining commands in the Job Management Partner 1/Base User's Guide.

(7) Actions to take when the monitored object database is damaged

Messages such as KAVB7247-E: JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The record in the database is invalid). and KAVB7248-E: JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be operated). are output.

Cause
The following is the possible cause:
  • Logical conflict has occurred in the monitored object database of JP1/IM - Manager.

Corrective action
Take the following steps:
  1. Stop JP1/IM - Manager.
  2. Collect a backup of the Scope-path\database folder for problem investigation.
  3. Execute the jcsdbsetup -f command.
  4. Delete all files from the Scope-path\database\jcshosts folder.
  5. Execute the jcshostsimport -r jcshosts command.
  6. Start JP1/IM - Manager.

(8) Actions to take when the monitored object database cannot be unlocked

The monitored object database stays locked.

Cause
The following is the possible cause:
  • An attempt to acquire a lock on the monitored object database of JP1/IM - Manager failed.

Corrective action
Take the following steps:
  1. Execute the jco_spmd_status command to make sure the jcsmain process is not active.
  2. Execute the Jismlcktr command.
  3. Determine which process has locked the files under Scope-path\database.
  4. Execute the Jislckfree -p PID command on the process ID determined in Step 3.
The Jismlcktr and Jislckfree commands are provided by JP1/Base. For details, see the chapter that explains commands in the Job Management Partner 1/Base User's Guide.

(9) Actions to take when KAVB5150-W is displayed in the detailed information (message) for the action result

When the Action Log Details window is opened, the message KAVB5150-W: There is no applicable data in the Command Executed log file. is displayed in the message column.

Cause
The command execution log file (ISAM) may have wrapped. If it has wrapped, automated action execution results cannot be displayed.

Corrective action
If this phenomenon occurs frequently, consider increasing the upper limit for the record count in the command execution log file. Keep in mind, however, that increasing the record count will also use more disk space.
The procedure follows.
Changing the upper limit for the record count
When you increase the upper limit for the record count, you must delete the command execution log file to enable the new setting. When you delete the command execution log file, all history on past automated actions and command execution is lost. Therefore, if deletion will cause a problem, back up the files. For details, see 1.2.2 Database backup and recovery.
  1. Execute the jcocmddef command to change the record count in the command execution log file.
  2. Stop JP1/IM and JP1/Base.
    In the case of a cluster configuration, operate the cluster software to stop the logical hosts.
    After you have confirmed that they have stopped, mount a shared disk in the shared directory.
  3. Delete the command execution log files.
    This means all files under the command execution log folder. The default command execution log folder is described below.
In Windows

Table 9-26 Locations of command execution log files (Windows)

File name Location
Command execution log file All files under Base-path\log\COMMAND\
All files under shared-folder\jp1base\log\COMMAND\
In UNIX

Table 9-27 Locations of command execution log files (UNIX)

File name Location
Command execution log file All files under /var/opt/jp1base/log/COMMAND/
All files under shared-directory/jp1base/log/COMMAND/
For details about the command execution log file, see the Job Management Partner 1/Base User's Guide.
  1. Start JP1/Base and JP1/IM.
    In the case of a cluster configuration, unmount the shared disk and then operate the cluster software to start the logical hosts.
For details about the jcocmddef command, see the chapter that explains commands in the Job Management Partner 1/Base User's Guide.

(10) Actions to take when an earlier version of JP1/IM - Central Scope or JP1/IM - View is being used

The actions to take differ depending on the message that is output.

The message KAVB6060-E: The connection destination server did not respond. is displayed.

Cause
The version of JP1/IM - Manager or JP1/IM - Central Scope is earlier than the version of JP1/IM - View, or an earlier version of the monitored object database is being used.

Corrective action

When the version of JP1/IM - Manager or JP1/IM - Central Scope is earlier than the version of JP1/IM - View:
Use the following procedure to upgrade the JP1/IM - Manager or JP1/IM - Central Scope version.
  1. In the Monitoring Tree (Editing) window, choose File and then Save Tree, and save the edited monitoring tree in the csv file.
  2. Upgrade JP1/IM - Manager or JP1/IM - Central Scope to the same version as JP1/IM - View.
  3. In the Monitoring Tree (Editing) window, choose File and then Open Tree, and load the csv file that was saved.
  4. In the Monitoring Tree (Editing) window, choose File and then Update Server Tree to update the server tree.

When the version of JP1/IM - View is the same as the version of JP1/IM - Manager or JP1/IM - Central Scope, but an earlier version of the monitored object database is being used:
Follow the procedure below to upgrade the monitored object database version.
  1. In the Monitoring Tree (Editing) window, choose File and then Save Tree, and save the edited monitoring tree in the csv file.
  2. Upgrade the monitored object database version.
  3. In the Monitoring Tree (Editing) window, choose File and then Open Tree, and then load the csv file that was saved.
  4. In the Monitoring Tree (Editing) window, choose File and then Update Server Tree to update the server tree.
For details about upgrading the monitored object database version, see the following sections:
  • For a physical host
    Windows: 1.18.3(2) Executing the Central Scope upgrade command in the Job Management Partner 1/Integrated Management - Manager Configuration Guide
    UNIX: 2.17.5(2) Executing the Central Scope upgrade command in the Job Management Partner 1/Integrated Management - Manager Configuration Guide
  • For a logical host
    Windows: 6.2.2(2) Setup during upgrading in the Job Management Partner 1/Integrated Management - Manager Configuration Guide
    UNIX: 6.3.2(2) Setup during upgrading in the Job Management Partner 1/Integrated Management - Manager Configuration Guide

When the version of JP1/IM - Manager or JP1/IM - Central Scope is later than the version of JP1/IM - View, and an earlier version of the monitored object database is being used:
Follow the procedure below to upgrade the JP1/IM - View version.
  1. In the Monitoring Tree (Editing) window, choose File and then Save Tree, and save the edited monitoring tree in the csv file.
  2. Uninstall JP1/IM - Manager or JP1/IM - Central Scope.
  3. Delete the JP1/IM - Manager or JP1/IM - Central Scope installation directory.
  4. Install the version of JP1/IM - Manager or JP1/IM - Central Scope that matches the version of JP1/IM - View.
  5. In the Monitoring Tree (Editing) window, choose File and then Open Tree, and load the csv file that was saved.
  6. In the Monitoring Tree (Editing) window, choose File and then Update Server Tree to update the server tree.
  7. Upgrade JP1/IM - Manager or JP1/IM - Central Scope to the later version.
  8. Upgrade JP1/IM - View to the same version as JP1/IM - Manager or JP1/IM - Central Scope.

The message KAVB6046-E: The user (user) does not have permission necessary for operations. is displayed.

Cause
The version of JP1/IM - View is earlier than the version of JP1/IM - Manager or JP1/IM - Central Scope, or the edited data in JP1/IM - View is from an earlier version.

Corrective action
Follow the procedure below to upgrade the version of JP1/IM - View.
  1. In the Monitoring Tree (Editing) window, choose File and then Save Tree, and save the edited monitoring tree in the csv file.
  2. Uninstall JP1/IM - Manager or JP1/IM - Central Scope.
  3. Delete the JP1/IM - Manager or JP1/IM - Central Scope installation directory.
  4. Install the JP1/IM - Manager or JP1/IM - Central Scope version that is the same version as JP1/IM - View.
  5. In the Monitoring Tree (Editing) window, choose File and then Open Tree, and load the csv file that was saved.
  6. In the Monitoring Tree (Editing) window, choose File and then Update Server Tree to update the server tree.
  7. Upgrade JP1/IM - Manager or JP1/IM - Central Scope to the later version.
  8. Upgrade JP1/IM - View to the same version as JP1/IM - Manager or JP1/IM - Central Scope.

(11) Actions to take when many JP1 events occurred for which correlation events were generated

If an operation such as system maintenance generates a large number of JP1 events for which correlation events are generated, the correlation event generation process may become overloaded.

The following two methods are available for avoiding this situation:

Stop JP1/IM - Manager only if the problem cannot be avoided even after the correlation event generation process has been paused.

Pausing the correlation event generation process
Pause the correlation event generation process, and resume it once the situation has improved.
The procedure follows.
  1. Execute the jcoegsstop command to pause correlation event generation processing.
    Executing the jcoegsstop command places Event Generation Service in standby status. This means that JP1 events generated during this period are not processed.
    Since the command stops only the processing without actually stopping the service, operations can continue without failover during cluster operation.
  2. To resume correlation event generation processing, execute the jcoegsstart command.

Stopping JP1/IM - Manager
When you stop JP1/IM - Manager, if the startup option is set to cold, there is no need to perform the procedure described below. Perform it only when the startup option is set to warm.
The procedure follows.
  1. Edit the correlation event generation system profile (egs_system.conf) and then change the startup option to cold.
  2. Restart JP1/IM - Manager.
  3. Edit the correlation event generation system profile (egs_system.conf) and then change the startup option back to warm.
  4. Execute the jco_spmd_reload command to enable the startup option setting.

(12) Actions to take when correlation events cannot be displayed in JP1/IM - View

The following are possible causes:

The action to take in response to each cause is described below.

Correlation event generation is not enabled.
Event Generation Service is an optional function and thus does not start by default. If Event Generation Service is not set to start, execute the jcoimdef command to set up the service to start. Event Generation Service will now start when JP1/IM - Manager is restarted.
To check whether the correlation event generation process is running, first restart JP1/IM - Manager and then execute the jcoegsstatus command to check whether Event Generation Service is in RUNNING status.

A correlation event generation definition has not been created.
Event Generation Service generates correlation events according to the correlation event generation definition. Since the correlation event generation definition is not created by default, correlation events are not generated.
After you have created the correlation event generation definition file, execute the jcoegschange command to apply the correlation event generation definition to Event Generation Service. You can use the jcoegsstatus command to check the correlation event generation definition that has been applied.

Correlation events are being filtered.
Check whether correlation events are not being filtered by an event acquisition filter, a user filter, a severe event filter, or a view filter.
Like normal JP1 events, correlation events are also filtered by an event acquisition filter, a user filter, a severe event filter, and a view filter. Furthermore, events for which no severity level has been defined are filtered by an event acquisition filter (in the default setting).

The applied correlation event generation definition is damaged.
If the message described below is output to the integrated trace log, the correlation event generation definition that was applied to Event Generation Service by the jcoegschange command may have been damaged.
  • KAJV2246-E An incorrect definition was detected because the correlation event generation definition storage file is corrupt. (line = line-number, incorrect contents = invalid-content)
If this message is output, execute the jcoegschange command and apply the correlation event generation definition again.

(13) Actions to take when the JP1/IM - View window cannot be displayed after you log on to JP1/IM - View

After you log on to JP1/IM - View, the JP1/IM - View window is not displayed. The task bar shows the JP1/IM - View task bar button.

Cause
When you perform the following operation, the JP1/IM - View window is not displayed after you log on to JP1/IM - View:
  • Terminating JP1/IM - View while a screen area was displayed in which JP1/IM - View was not shown because of the virtual window configuration.#

#
This configuration, by having more desktops than the display windows in the memory and by displaying each of the partitioned areas as a single virtual desktop, allows the user to use multiple desktops by switching among the windows.
This configuration is also called a virtual desktop.

Corrective action
Take one of the following corrective actions:

Corrective action 1
  1. Press the Alt + Tab keys and select JP1/IM - View.
  2. From the task bar, choose Cascade Windows to display all windows in a cascade.
  3. Change the display positions and sizes of the JP1/IM - View and other windows.

Corrective action 2
  1. Press the Alt + Tab keys and select JP1/IM - View.
  2. From the task bar, choose Tile Windows Horizontally to display all windows as horizontal tiles.
  3. Change the display positions and sizes of the JP1/IM - View and other windows.

Corrective action 3
  1. Press the Alt + Tab keys and select JP1/IM - View.
  2. From the task bar, choose Tile Windows Vertically and display all windows as vertical tiles.
  3. Change the display positions and sizes of the JP1/IM - View and other windows.

Corrective action 4
  1. Press the Alt + Tab keys and select JP1/IM - View.
  2. From the Context menu of JP1/IM - View, choose Move and then use the cursor key to adjust the position.
  3. Once you have decoded the position of the displayed window or its frame, press the Enter key.

Corrective action 5
  1. Press the Alt + Tab keys and select JP1/IM - View.
  2. From the Context menu of JP1/IM - View, choose Maximize, and with the window maximized, log out from JP1/IM - View.
  3. After you log on to JP1/IM - View again, change the window's display position and size.

(14) Actions to take when command execution or a batch file executed in an automated action does not terminate normally (Windows only)

Cause
If all of the following conditions are present, batch file processing is interrupted and cannot be normally executed.
  • The OS of the host specified as the command execution destination is Windows 2000.
  • A batch file uses the FOR /F command.
  • After the execution of the FOR /F command, the result is output to standard error.

Corrective action
Take one of the following corrective actions:
  • Do not use the FOR /F command.
  • Do not output the result to standard error after execution of the FOR /F command.

(15) Actions to take when processing of JP1 events received by JP1/IM - Manager (JP1/IM - Central Scope) is delayed

Cause
Name resolution of the character string (host name or IP address) specified as an attribute value of the individual condition in the status-change condition settings may have failed.

Corrective action
The host name that could not be resolved is output to the following logs:

In Windows
Scope-path\log\jcsmain_trace{1|2|3}.log#

In UNIX
/var/opt/jp1scope/log/jcsmain_trace{1|2|3}.log#

#
Do not specify this log as the monitoring target of the JP1/Base log file trapping function.
If name resolution failed, one of the following messages is output in the aforementioned log file:
...fs_jcsHostsAccessPtr->getHostByName() is failed. (host = host-name-for-which-name-resolution-failed,jp1error = 2001)...
or
...fs_jcsHostsAccessPtr->getHostByAddr() is failed. (host = IP-address-for-which-name-resolution-failed,jp1error = 2001)...
Check one of these messages and specify Host name comparison as the individual condition. Then, use one of the methods described below to enable name resolution of the host name or IP address specified as the attribute value.
  • Register in the host information database the host name or IP address specified as the attribute value of the individual condition.
  • Register in jp1hosts of JP1/Base the host name or IP address specified as the attribute value of the individual condition.
  • Register in hosts or DNS the host name or IP address specified as the attribute value of the individual condition.

(16) Actions to take when no JP1 event is displayed in the Event Console window

Cause
Because no condition is specified in the exclusion conditions or valid common exclusion conditions for a filter, all JP1 events are excluded.

Corrective action
Reassess the exclusion conditions or valid common exclusion conditions for the following filters:
  • Event acquisition filter
  • User filter
  • Severe event filter
  • View filter

(17) Actions to take when a status cannot be changed

The following are possible causes:

The action to take in response to each cause is described below.

Connection cannot be established between the event console and Central Console. Or, connection cannot be established between the event console and the jcochstat command.
The event console on the manager may not have been started, the system (host or network) may be under a heavy workload, or the network settings may be invalid.
  • Corrective action
    Execute the jco_spmd_status command to check whether the event console on the manager has started, and then try to change the status again.
    Alternatively, use the ping command, for example, to check whether the logged-in host is running normally, and then try to change the status again.

The specified JP1 event was an event that cannot be changed.
  • Corrective action
    Reassess the serial number inside the event database and then try to change the status again.

Connection cannot be established between Event Console Service and Event Service.
  • Corrective action
    Check whether Event Service has started, and then try to change the status again.

Connection cannot be established between Event Console Service and Event Base Service.
Event Base Service may not have been started, or the system (host or network) may be under a heavy workload.
  • Corrective action
    Execute the jco_spmd_status command to check whether Event Base Service on the manager has started, and then try to change the status again.

Connection cannot be established between the Event Base Service and the IM database service.
The IM database service may not have been started, or the system (host or network) may be under a heavy workload.
  • Corrective action
    First start the IM database service, and then try to change the status again.

(18) Actions to take when an event search cannot be performed

The following are possible causes:

The action to take in response to each cause is described below.

Connection cannot be established between the event console and the viewer.
The event console on the manager may not have been started, the system (host or network) may be under a heavy workload, or the network settings may be invalid.
  • Corrective action
    Execute the jco_spmd_status command to check whether the event console on the manager has started, and then perform the event search again.
    Alternatively, use the ping command, for example, to check whether the logged-in host is running normally, and then perform the event search again.

Connection cannot be established between Event Base Service and Event Console Service.
Event Base Service may not have been started, or the system (host or network) may be under a heavy workload.
  • Corrective action
    Execute the jco_spmd_status command to check whether Event Base Service has started on the manager, and then perform the event search again.

Connection cannot be established between Event Base Service and the integrated monitoring database.
The integrated monitoring database may not have been started, or the system (host or network) may be under a heavy workload.
  • Corrective action
    First start the integrated monitoring database, and then perform the event search again.

Connection cannot be established between Event Console Service and Event Service.
The Event Service instance at the target host may not have been started, the system (host or network) may be under a heavy workload, or the network settings may be invalid.
  • Corrective action
    Execute the jevstat command to check whether the Event Service instance at the target host has started, and then perform the event search again. For details about the jevstat command, see the Job Management Partner 1/Base User's Guide.
    Alternatively, use the ping command to check whether the target host is running normally, and then perform the event search again.

A JP1 event search was performed using an unsupported condition.
A JP1 event search was performed using an unsupported condition (Is contained, Is not contained, Regular expression, or multiple statuses specified) for Event Service of JP1/Base Version 06-00 or earlier. Or, a JP1 event search was performed using an unsupported condition (Regular expression specified) for Event Service of JP1/Base Version 06-51 or earlier.
  • Corrective action
    Make sure that Is contained, Is not contained, Regular expression, or multiple statuses are not selected, and then perform the search again.

The regular expression specified for performing the event search was invalid.
  • Corrective action
    Make sure the displayed regular expression is valid, and then re-execute the search.

When an event search was executed with an exclusion condition specified, and the JP1/Base version of the target host was 08-00 or earlier.
  • Corrective action
    Check the version of JP1/Base on the host that is specified as the event search target, and if it is 08-00 or earlier, execute the search without using an exclusion condition.

(19) Actions to take when memo entries cannot be set up

The following are possible causes:

The action to take in response to each cause is described below.

Connection cannot be established between the event console and Central Console - View.
The event console on the manager may not have been started, the system (host or network) may be under a heavy workload, or the network settings may be invalid.
  • Corrective action
    Make sure that Event Console Service or the host is running normally, and then set up memory entries.
    Execute the jco_spmd_status command to check whether the event console on the manager has started, and then set up memory entries again.
    Alternatively, use the ping command, for example, to check whether the logged-in host is running normally, and then set up memory entries again.

Connection cannot be established between Event Console Service and Event Base Service.
Event Base Service may not have been started, or the system (host or network) may be under a heavy workload.
  • Corrective action
    Execute the jco_spmd_status command to check whether Event Base Service on the manager has started, and then set up memory entries again.

Connection cannot be established between Event Base Service and the integrated monitoring database.
The integrated monitoring database may not have been started, or the system (host or network) may be under a heavy workload.
  • Corrective action
    After starting the integrated monitoring database, set up memory entries again.

(20) Actions to take when the IM database cannot be terminated

Cause
There is a JP1/IM - Manager process that is currently connected.

Corrective action
Check whether JP1/IM - Manager is running. If it is, terminate it first and then terminate the IM database.

(21) Actions to take when you cannot connect to the IM database

The following are possible causes:

The action to take in response to each cause is described below.

The system is not set up to use the IM database.
  • Corrective action
    Execute the jcoimdef command without specifying any option, and check whether S_DB is set to ON. For details about the jcoimdef command, see jcoimdef (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

The IM database has not been started.
  • Corrective action
    Make sure that the IM database has been started.

The port number setting is invalid.
  • Corrective action
    Make sure that the specified port number is not the same as any of the following port numbers:
  • Port number specified during the setup of another logical host
  • Port number described in the services file
  • Port number that is used by a HiRDB instance bundled with another product
  • Temporary port number that is used by another product or by the OS, for example

When a logical host in a non-cluster system was set up, standby was specified for the -c option of the jcfdbsetup or jcodbsetup command.
  • Corrective action
    When setting up a logical host of a non-cluster system, specify online for the -c option of the jcfdbsetup or jcodbsetup command.

(22) Actions to take when JP1/IM - Manager cannot be uninstalled

The message KAVB9940-E: Unsetup has not been performed for the IM database service on the physical host. or KAVB9941-E: Unsetup has not been performed for the IM database service on the logical host. (Logical host name: logical-host-name) is output.

Cause
The IM database has not been unset up.

Corrective action
Make sure that the integrated monitoring database and the IM Configuration Management database have been unset up.

(23) Actions to take when an error message indicating an invalid port number is issued after the IM database has been set up

The message KNAN11044-E: The setup information file does not exist. is output.

Cause
The specified port number is the same as a port number being used elsewhere.

Corrective action
Make sure that the specified port number is not the same as any of the following port numbers:
  • Port number specified during the setup of another logical host
  • Port number described in the services file
  • Port number that is used by a HiRDB instance bundled with another product
  • Temporary port number that is used by another product or the OS, for example

(24) Actions to take when IM database setup fails

The message KNAN11084-E: Creation of a database file system area has failed. is output.

The following are possible causes:

The action to take in response to each cause is described below.

The file system in the path specified in IMDBDIR or SHAREDBDIR does not support large files.
  • Corrective action
    In the target OS, enable the large file setting.

The kernel parameters have not been set correctly.
  • Corrective action
    Make sure that the kernel parameters have been set correctly. For details about kernel parameters, see the JP1/IM - Manager release notes.

The host name specified in LOGICALHOSTNAME or ONLINEHOSTNAME is invalid.
  • Corrective action
    Check the following items:
  • Is the host name specified in LOGICALHOSTNAME or ONLINEHOSTNAME appropriate?
  • Is the host name specified in the -h option of database-related commands appropriate?
  • Is the host name specified in the hosts file described? Are there any duplicate host names?
  • Is the IP address corresponding to the specified host name appropriate? Are there any duplicate IP addresses?

(25) Actions to take when the setup information file is output as invalid during IM database setup

One of the following messages is output:

The following are possible causes:

The action to take in response to each cause is described below.

A required item or value is not specified.
  • Corrective action
    Check the setup information file and the cluster information file, and specify all required items.

The character string specified for the item name is invalid.
  • Corrective action
    Check the setup information file and the cluster information file, and specify all required items.

An invalid value is specified.
  • Corrective action
    Check the specified value and correct it if necessary.

An unnecessary space is inserted before or after the equal sign (=).
  • Corrective action
    Check whether there is a space before or after the equal sign (=) and delete it if present.

(26) Actions to take when the IM database cannot be started or database-related commands cannot be executed

When executing a database-related command, the message KNAN11037-E: The data storage directory of the IM database service cannot be accessed. or KNAN11143-E: Configuration of the IM database service is invalid. is output.

The following are possible causes:

The action to take in response to each cause is described below.

In UNIX, the IM database installation directory or data storage directory has been unmounted.
  • Corrective action
    Check whether you can access the directory. If you cannot, mount the directory.

The host name has been changed.
  • Corrective action
    Restore the host name to the previous name, and then change the host name by following the host name change procedure for the IM database.

The IM database is using a port number that is being used by another product.
  • Corrective action
    Make sure that the specified port number is not the same as any of the following port numbers:
    [Figure] Port number specified during the setup of another logical host
    [Figure] Port number described in the services file
    [Figure] Port number that is used by a HiRDB instance bundled with another product
    [Figure] Temporary port number that is used by another product or by the OS, for example

(27) Actions to take when IM Configuration Management fails to collect host information

The message KNAN22017-E: Collection of host information failed because a connection could not be established with the host "host-name". is output and host information collection fails.

Cause
The following are possible causes:
  • The target host name is different.
  • The target host name has not been resolved.
  • The target host has not been started.
  • JP1/Base of the target host has not been started.
  • An error occurred in communications with the target host.
  • The installation of JP1/Base on the target host is earlier than Version 7.

Corrective action
Take the corrective action that matches the cause.
  • Maker sure that the target host name is correct.
  • Maker sure that the target host has been started.
  • Maker sure that JP1/Base of the target host has been started.
  • Maker sure that there is no problem in communications with the target host.
  • Maker sure that the installation of JP1/Base on the target host is Version 7 or later.

(28) Actions to take when IM Configuration Management fails to apply the system hierarchy

Cause
The following are possible causes:
  • JP1/Base of the host onto which the system hierarchy is to be applied has not been started.
    To apply the system hierarchy, all hosts included in the system hierarchy must be active.
  • The host onto which the system hierarchy is to be applied is already included in another system hierarchy.
  • Name resolution cannot occur among the integrated manager, relay manager, and agent.

Corrective action
Take the corrective action that matches the cause.
  • Make sure that the JP1/Base of the host for which system hierarchy application failed is active, and then retry the operation.
  • Execute the jbsrt_get command on the host for which system hierarchy application failed, and then check whether the host is included in another system hierarchy. If the host is included in another system hierarchy, delete if from that system hierarchy, and then retry the operation.
  • Check whether host name resolution among various hosts was successful. If it was unsuccessful, change the settings so that name resolution can take place, and then retry the operation.

(29) Actions to take when IM Configuration Management fails to collect the operation definition file for the log file trap

Cause
The action definition file for a log file trap must be unique within the agent. Multiple log file traps may have been started using the same settings file, or multiple log file traps may have been started using action definition files that have the same name but are in different directories.

Corrective action
Follow the steps described below.
  1. On the agent, stop the log file trap.
  2. Set up the action definition file for a log file trap such that it has a unique name within the agent, and then restart the log file trapping function.
  3. In the Display/Edit Profiles window of IM Configuration Management - View, from the Operation menu, choose Rebuild Profile Tree to rebuild the profile tree.

(30) Actions to take when JP1/IM - View cannot display any of the log file traps that are active

Cause
The following are possible causes:
  • After the log file trapping function was started, the profile tree was not rebuilt.
    The log file trap may have been started or restarted after the Display/Edit Profiles window was started, after the profile tree was rebuilt, or after batch collection of profiles was executed.
  • The action definition file specified during startup of the log file trap is not found under JP1-Base-path\conf.

Corrective action
Take the corrective action that matches the cause.
  • You need to collect the latest profile list. In the Display/Edit Profiles window of IM Configuration Management - View, from the Operation menu, choose Rebuild Profile Tree to rebuild the profile tree.
  • Place the action definition file for the log file trap under JP1-Base-path\conf, and then restart the log file trapping function.
    After the log file trap is started, in the Display/Edit Profiles window of IM Configuration Management - View, from the Operation menu, choose Rebuild Profile Tree to rebuild the profile tree.

(31) Actions to take when the content of the profile settings file does not match the content of the valid configuration information

Cause
The following are possible causes:
  • After the settings file was edited, the edited content was not applied or the application operation failed.
  • Part of the description of the settings file is invalid.
    If part of the description of the settings file is invalid, the agent sometimes skips the invalid description when it applies the settings file. In this case, if you perform an application operation from IM Configuration Management - View, an error dialog box opens.

Corrective action
Take the corrective action that matches the cause.
  • In the Display/Edit Profiles window of IM Configuration Management - View, verify the content of the settings file, and then execute profile application and make sure that the applicaton operation terminates normally.
  • If application of the settings file fails, services may not operate according to the description in the settings file. Correct the description errors and then retry the operation.

(32) Actions to take when menu items such as Register Host and Edit IM Configuration are disabled in IM Configuration Management - View

Cause
Because the JP1 user who logged on to IM Configuration Management - View is not assigned IM Configuration Management permissions (JP1_CF_Admin, JP1_CF_Manager, or JP1_CF_User), the only operation that is allowed is viewing. The following are possible causes:
  • The instance of JP1/Base specified in the authentication server is Version 8 or earlier.
  • After the instance of JP1/Base specified in the authentication server was upgraded from Version 8 or earlier by means of overwrite installation, the JP1 user was not assigned IM Configuration Management permissions (JP1_CF_Admin, JP1_CF_Manager, or JP1_CF_User).
  • The JP1 user is not assigned IM Configuration Management permissions (JP1_CF_Admin, JP1_CF_Manager, or JP1_CF_User).

Corrective action
First, upgrade the instance of JP1/Base specified in the authentication server to Version 9 or later. Then, assign IM Configuration Management permissions (JP1_CF_Admin, JP1_CF_Manager, or JP1_CF_User) to the JP1 user, and have the user log in again.

[Contents][Back][Next]

[Trademarks]

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