Versions Compared

Old Version 1

changes.mady.by.user Brian Nordland

Saved on

compared with

New Version 2

changes.mady.by.user Brian Nordland

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

  1. 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:

    The first panel of the Work with ASP Job Queue display panel that shows an IASP called MYIASP with Nodes PROD, HA, DR and Flash. None of the nodes have any tracked job queues.Image Removed

    Status
    titleUnknown Attachment

  2. 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:

    Image Removed

    Status
    titleUnknown Attachment

  3. 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.

Panel
panelIconIdatlassian-light_bulb_on
panelIcon:light_bulb_on:
panelIconText:light_bulb_on:
bgColor#E3FCEF

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:

...

Status
titleUnknown Attachment

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

Note

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.

Panel
panelIconId23e9
panelIcon:fast_forward:
panelIconText⏩
bgColor#B3F5FF

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)

...

  1. 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:

    Image Removed


    Status
    titleUnknown Attachment

  2. 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:

    Image Removed


    Status
    titleUnknown Attachment

  3. 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.

  4. Repeat the previous step to end tracking any additional job queues.

Note

Reminder: The previous example ended tracking for a job queue on node PROD. In many environments the same job queue may be tracked on multiple nodes, so this process may need to be repeated by selecting the appropriate node on the WRKASPJOBQ display.

Panel
panelIconId23e9
panelIcon:fast_forward:
panelIconText⏩
bgColor#B3F5FF

Shortcut: It is also possible to end Job Queue tracking using the End Tracking Job Queue (ENDTRKJOBQ) command. This command takes an ASP device, job queue, and a cluster node. Using the following command would achieve the same result as the above example:
ENDTRKJOBQ ASPDEV(MYIASP) JOBQ(PRODLIB/MYJOBQ) NODE(PROD)