Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 - Print Option Description and User's Guide


4.1 Collecting information about job operation

The collection of job operation information involves taking the job information managed by JP1/AJS3 - Manager and recording it in a job operation information file. Job operation information files have the extension .aoi. The information in these files is the basis for the documents output by JP1/AJS3 - Print Option.

If you intend to collect job operation information on a regular basis, you can use the jprcollect command to automate the process. If you want to check the current status of job activity to assist tasks like system design, you can collect job information from the user interface by opening the Collecting Job Operation Information window.

JP1/AJS3 - Print Option Manager collects jobnet definitions, jobnets registered for execution, execution schedules, and execution results. This information is collected by the ajsprint and ajsshow commands provided by JP1/AJS.

You can make sure that JP1/AJS3 - Print Option Manager only collects the information you need by specifying criteria that define the range of information to be collected. You can limit collected information to specific units, or a specific time period.

To collect jobnet execution schedules and execution results, specify a time period by entering a start date and end date. If you do not specify a time period, JP1/AJS3 - Print Option Manager only collects jobnet definitions, not execution schedules and execution results.

To limit collection to specific units, specify the name of the job, jobnet, or job group whose information you want to collect. To explain the concept of units, an overview of jobnet definitions in JP1/AJS is given below.

Processing in JP1/AJS is defined by combining and correlating related processes. Individual processes are defined as jobs, and a collection of jobs to be executed in a defined order is defined as a jobnet. You can also create job groups that you can use to group jobnets by category.

The following figure shows the relationship between jobs, jobnets, and job groups.

Figure 4‒1: Relationship between jobs, jobnets, and job groups

[Figure]

Among the jobs you can define in JP1/AJS are those that define processing, send and receive events, and evaluate processing results against specified conditions. You can also register user-defined processing as a job.

In a jobnet, you can define post-processing to perform when a job terminates abnormally, additional jobnets, and other elements in addition to jobs. You can define all manner of jobnets by combining and correlating jobs.

Units such as jobnets and job groups used in jobnet definitions are called unit.

The following table lists and describes each type of unit.

Table 4‒1: Unit types and descriptions

Unit

Description

Generic name

Individual name

Job group

Root job group

The highest-level job group. A root job group is always defined in JP1/AJS. The name of the scheduler service serves as the root job group name.

The default job group name is /.

Nested job group

A job group defined under the root job group.

Planning group

A planning group can only be created directly under a job group. You can then switch between the root jobnets created under the planning group.

Jobnet

Root jobnet

The highest-level jobnet in a job group.

Nested jobnet

A jobnet defined in a root jobnet.

Remote jobnet

A jobnet that is registered for execution on another host when the jobnet starts.

Job

A collection of elements such as commands, shell scripts, and Windows executable files.

Manager unit

Manager job group

A unit that links job groups or jobnets defined in JP1/AJS3 - Manager on a remote host.

Manager jobnet

The information you can collect depends on the type of unit specified, as shown in the following table. JP1/AJS3 - Print Option Manager collects information for all units defined under the specified unit.

Table 4‒2: Collected job operation information

Unit specified for collection

Information that can be collected

Generic name

Individual name

Job group

Root job group

  • Definition information

  • Execution schedules and execution results#1, #2

Nested job group

  • Definition information

  • Execution schedules and execution results#1, #2

Planning group

  • Definition information

  • Execution schedules and execution results#1, #2

Jobnet

Root jobnet#3

  • Definition information

  • Execution schedules and execution results#1

Other than root jobnet

  • Definition information

  • Execution schedules and execution results#1

Job

  • Definition information

  • Execution schedules and execution results#1

Manager unit

Manager group

Cannot be collected#4

Manager jobnet

Cannot be collected#4

#1

JP1/AJS generates execution schedules and execution results when a unit is submitted for execution. For this reason, you can only collect execution schedules and results when you specify units that have been submitted for execution. JP1/AJS keeps a certain number of generations of execution results. If you want to collect results for every execution of a given unit, you need to change the number of saved generations in JP1/AJS. The default is 1 generation.

#2

If you specify a job group that contains units that have been submitted for execution and those that have not, you can only collect execution schedules and execution results for the units that have been submitted for execution.

#3

If you use the jobnet release functionality, you can collect jobnet definition information and execution results by release ID.

For details on the jobnet release functionality, see the manual JP1/Automatic Job Management System 3 Overview.

#4

You cannot collect information for a manager job group or a manager jobnet. This information can only be collected by an operation on the link-destination JP1/AJS3 - Manager host for the unit.

When you collect information for a planning group, information is collected for all units in the planning group regardless of whether they are running. The following figure shows how the acquired information changes depending on the unit you specify.

Figure 4‒2: Range of information acquired

[Figure]

Legend:

[Figure]: The range of information collected when you specify Job group 1. JP1/AJS3 - Print Option Manager collects information for all units.

[Figure]: The range of information collected when you specify Planning group.

[Figure]: The range of information collected when you specify Job group 2.

[Figure]: The range of information collected when you specify Jobnet 6.

When units are defined under a planning group, JP1/AJS3 - Print Option Manager collects information not just for running units (Jobnet 1 in the figure), but also for units that are not running (Jobnet 2 and Jobnet 3 in the figure).

You cannot output job operation information for more than the maximum number of units to a single document. When collecting information for a document, make sure that the number of units for which data is being collected does not exceed the maximum.

You can set the maximum number of units in the Environment Settings window, in a range from 32,000 to 150,000. For details on how to set this parameter, see 7.19 Environment Settings window.

When JP1/AJS3 - Manager is operating in a cluster environment, collect job operation information from the active node. When doing so, specify the name of the scheduler service on the logical host as the service name.