4.1.2 Monitoring the execution time of jobnets

Depending on the execution status of the host where JP1/AJS3 is installed, jobnets might not start or end at the specified time. A delayed jobnet might affect succeeding jobnets and might cause overall processing to be delayed.

When you monitor JP1/AJS3 normal operation, you must monitor the following items:

The execution time of a jobnet itself
Delayed starting and delayed ending of a jobnet

The following table describes the methods you can use to monitor execution time and delays.

Table 4‒2: Methods for monitoring execution time and delays
Method	Description
JP1/AJS3 - View windows	You can use the following windows to monitor execution time and delays: JP1/AJS3 - View window (Summary Monitor window) Jobnet Monitor window (definition window format) Monthly Schedule window (calendar format) Daily Schedule window (chart format) The following are the default colors used to indicate delays. Check for items displayed in any of the following colors. Start delay: Pink Start delay + Running: Dark pink End delay: Orange End delay (Running): Dark orange
Web GUI windows	JP1/AJS3 - Web Console allows users to check the delay statuses, start times, scheduled end times, and actual end times of jobnets by using a web browser. JP1/AJS3 - Web Console can also be used to check the progress of a jobnet in terms of the proportion of jobs under that jobnet that have ended successfully.
User application	Original applications (user applications) developed or implemented by using the API released by JP1/AJS3 can be used to check the delay statuses and start times of jobnets.
Command	`ajsshow` command This command outputs information about a jobnet or a job registered for execution to the standard output file. The information output includes the previous execution results, current status, and next execution schedule.
Log data	Information such as whether starting or ending of a jobnet was delayed is output to a JP1/AJS3 scheduler log file. Use a tool such as a text editor to check the log file. The default locations of these log files are as follows: When a log file is output for each scheduler service: In Windows, if the installation folder is the default installation folder or is in a folder protected by the system: `%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name\ajs-log1.log` `%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\schedule\scheduler-service-name\ajs-log2.log` The default for `%ALLUSERSPROFILE%` is `system-drive\ProgramData`. A folder protected by the system is a folder in any of the following: - `system-drive\Windows` - `system-drive\Program Files` - `system-drive\Program Files (x86)` In Windows, if the installation folder is other than the above: `JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log1.log` `JP1/AJS3-Manager-installation-folder\log\schedule\scheduler-service-name\ajs-log2.log` In UNIX: `/var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajs-log1.log` `/var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajs-log2.log` When a log file is output for each host: In Windows, if the installation folder is the default installation folder or is in a folder protected by the system: `%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\ajs-host-log1.log` `%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log\ajs-host-log2.log` The default for `%ALLUSERSPROFILE%` is `system-drive\ProgramData`. A folder protected by the system is a folder in any of the following: - `system-drive\Windows` - `system-drive\Program Files` - `system-drive\Program Files (x86)` In Windows, if the installation folder is other than the above: `JP1/AJS3-Manager-installation-folder\log\ajs-host-log1.log` `JP1/AJS3-Manager-installation-folder\log\ajs-host-log2.log` In UNIX: `/var/opt/jp1ajs2/log/ajs-host-log1.log` `/var/opt/jp1ajs2/log/ajs-host-log2.log`
Windows event log or syslog	When the `NETSYSLOG` and `JOBSYSLOG` environment setting parameters are set, information such as whether the start or end of a jobnet was delayed and whether the end of a job was delayed is output to the Windows event log or to syslog. The following describes the event IDs, facilities, and message IDs for a delayed start and a delayed end. Delayed-start event Event ID: 30275 Facility: `LOG_DAEMON` Message ID: KAVS0275-I Delayed-end event Event ID: 30276 Facility: `LOG_DAEMON` Message ID: KAVS0276-I Event ID: 30248 Facility: `LOG_DAEMON` Message ID: KAVS0248-I
JP1 event	When a jobnet is scheduled with a JP1 event reception monitoring job defined, the jobnet can be monitored automatically at a specified date and time or at specified intervals. The following describes the event IDs for a start-delay JP1 event and an end-delay JP1 event. Delayed-start event JP1 event ID: 00004122 Delayed-end event JP1 event ID: 00004123 and 00004127

For details about the items displayed in the windows and the operating procedures, see the JP1/Automatic Job Management System 3 Operator's Guide.

For details about the ajsshow command options and output examples, see ajsshow in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about the scheduler log output format, see C. Log Information in the manual JP1/Automatic Job Management System 3 Troubleshooting.

For details about JP1 events, see A. JP1 Events Issued by JP1/AJS3.

To Page Top