Configuring Job Queue Tracking

1 Background
2 Start Tracking for a Job Queue
- 2.1 Job Retention Period
3 End Tracking for a Job Queue

Background

Job queues that exist in an Independent Auxiliary Storage Pool (IASP) can have job lifecycle information tracked so that as jobs enter the system, begin running and complete, the information on the job’s lifecycle is stored in the IASP. This enables the simplified ability to restart these jobs after an unplanned outage. Since the job lifecycle information is tracked in the same place as your application data, the recovery point for your job lifecycle is the same as the recovery point for your business data.

Start Tracking for a Job Queue

The primary interface for configuring job queue tracking is the Work with ASP Job Queue (WRKASPJOBQ) command.

Type WRKASPJOBQ from a command line and press enter.
The screen populates with a list of IASP devices and nodes in the cluster that are potential hosts for the IASP device similar to figure 1 below:
Figure 1
Type 12 next to a node and press enter to work with tracked job queues for the specified node. The display will look similar to figure 2 below:
Figure 2
On the tracked job queues display type option 8 (start tracking) in the Opt field, along with a job queue name in the Job Queue field and the library of the job queue in the Library field and press enter to start tracking jobs in the job queue.

Tip: The job queue does not need to exist at the time of registering the job queue for tracking. However, the job queue will only be tracked if the job queue exists in a library within the specified ASP device. Job queue tracking does not track job queues in the system ASP (SYSBASE)

The display will now look similar to the figure 3 below. If the IASP is not currently available, the tracked jobs will display as *UNKNOWN:

Repeat the previous step to start tracking any additional job queues.

Reminder: The previous example started tracking for a job queue on node PROD. In many environments it is recommended to track the same job queue on other nodes such as HA and DR in the environment so that regardless of which node is currently the production, job queues are tracked as expected.

Shortcut: It is also possible to start Job Queue tracking using the Start Tracking Job Queue (STRTRKJOBQ) command. This command takes an ASP device, job queue, and optionally a retention period and cluster node. Using the following command would achieve the same result as the above example:
STRTRKJOBQ ASPDEV(MYIASP) JOBQ(PRODLIB/MYJOBQ) RETENTION(*NONE) NODE(PROD)

Job Retention Period

By default the job retention period is *NONE. This indicates that as soon as a job is completed, it will no longer appear as a tracked job. It is possible to specify a longer job retention period by doing one of the following:

If using the WRKASPJOBQ interface to start job queue tracking, press f4, instead of enter, to prompt for additional options when using option 8 to start tracking a job queue.
If using the STRTRKJOBQ command, press f4 to prompt on the command, followed by f10 to see the additional parameter: Job retention period.

A job retention period is specified in minutes. A job retention period of 60 would indicate a job should continue to be listed in the tracked jobs list for at least 60 minutes after the job completes.

End Tracking for a Job Queue

The primary interface for configuring job queue tracking is the Work with ASP Job Queue (WRKASPJOBQ) command.

Type WRKASPJOBQ from a command line and press enter.
The screen populates with a list of IASP devices and nodes in the cluster that are potential hosts for the IASP device similar to figure 4 below:
Type 12 next to a node and press enter to work with tracked job queues for the specified node. The display will look similar to figure 5 below:
On the tracked job queues display type option 9 (end tracking) in the Opt field next to the job queue you want to end tracking for and press enter to end tracking.
Repeat the previous step to end tracking any additional job queues.