jpomanevshow

Format

jpomanevshow
     [-h logical-host-name]
     [-F service-name]

To Page Top

Description

Analyzes the internal log of the event action control manager and displays the execution hosts that often send data to the manager and information about start conditional jobnet. You use this command when you want to identify a job that has caused a large number of events related to start conditions, as well as the agent that is to be specified in the arguments of the jpomanevreset command. (See Example.)

The targets of analysis are the logs that have been output within the last 24 hours. If there are wrapped logs, then only the remaining logs are to be analyzed. The target of analysis also covers only the logs related to start conditions, not covering the event jobs that is defined in the jobnets.

In the result of analysis, five start conditions are displayed, starting with those with the highest level of data sending. For each of the start conditions, the information that can identify the particular start condition and the number of logs during a certain period of time are displayed.

Before you can execute this command, make sure that the JP1/AJS3 host service is running.

To Page Top

Execution privileges

In Windows: Administrators privileges

In UNIX: Superuser privileges

To Page Top

Arguments

To Page Top

Notes

• Do not execute this command while JP1/AJS3 is starting.

• Always separate an option and its value by at least one space character.

• You cannot execute several instances of this command at the same time. Wait for one command to be completed before you move on to another command.

• If you execute the command when the folder used for storing the internal log of the event action control manager does not exist, the system operates as if there were no data, and the command is terminated normally. For details about the folder used or storing the internal log of the event action control manager, see 1.2.5 List of log files and directories in the manual JP1/Automatic Job Management System 3 Troubleshooting.

• If you specify the local host name in the -h option, the system will operate by assuming that a physical host is specified.

• On a Windows machine, before you execute this command, make sure that you open the Command Prompt window as an administrator. If the UAC function is disabled, you do not need to open the Command Prompt window as an administrator.

• If the default scheduler service name assumed when the -F option is omitted is not registered, the command outputs message KAVT8351-E to standard error output and terminates abnormally. Make sure that the default scheduler service name is registered on the command execution host, and then execute the command again.

  You can reference the -h option in the command line to identify the host where the command will be executed.

To Page Top

Return values

To Page Top

Output example

The following is an example of output obtained when you execute the command on the manager host:

Time for analysis=20XX/06/01 02:30:00 - 20XX/06/02 02:30:00
 
Agent=agent1
Scheduler service=AJSROOT1
Unit ID=2133
Execution ID=2000 (ID:@A2000)
Total count=233
Target time                   Count
20XX/06/01 22:00:00-22:59:59      1
20XX/06/01 23:00:00-23:59:59      1
20XX/06/02 00:00:00-00:59:59      1
20XX/06/02 01:00:00-01:59:59     30
20XX/06/02 02:00:00-02:30:00    200
 
Agent=agent1
Scheduler service=AJSROOT1
Unit ID=2134
Execution ID=2000 (ID:@A2000)
Total count=1
Target time                   Count
20XX/06/01 17:00:00-17:59:59      1

The content of each item output can be interpreted as follows:

Time for analysis

Indicates the time required for analysis. The time displayed here shows the time measured on the internal log and it may be different from the system time.

Agent

Indicates the name of the execution host sending data.

Scheduler service

Indicates the scheduler service name in which start conditions are defined.

Unit ID

Indicates the unit ID of the event job defined in the start conditions.

Execution ID

Indicates the execution ID for start conditions. The execution ID corresponds to the "Being executed" generation displayed on the Daily Schedule window or the Monthly Schedule window.

What is shown in parentheses corresponds to what is displayed on JP1/AJS3 - View.

Total count

Indicates the total number of entries that were stored in the internal log and that pertain to start conditions.

Target time

Indicates the target duration at which to display the number of logs per unit time. If no logs occur during the target duration, the target duration itself will not be output.

Count

Indicates the total number of log entries that were present during the target time and that pertain to start conditions.

To Page Top

Example

Suppose that there has been a rapid increase in the number of events that monitor start conditions. The entire system operating JP1/AJS3 will suffer from high loads because of frequent communication between the manager and the agent and frequent input/output operations of files for storing data temporarily. This makes the operator's action ineffective, thus leading to a major delay in the processing of other programs. In this case, you use the jpomanevshow command to identify the job and event responsible for the large number of events related to start conditions. You can return to normal operation if you eliminate the cause of the large number of monitoring conditions for the particular job and use the jpomanevreset command to remove the large number of event data items from the particular agent.

For details about the above procedures, see 2.5 Troubleshooting problems if processing of a jobnet with a start condition is delayed in the manual JP1/Automatic Job Management System 3 Troubleshooting.

To Page Top