Prev | Table of Contents | Next

7. PJS Utilities

The Personal Job Scheduler system provides several utilities to help install and maintain PJS. Only the Site Administrator, a systems programmer, the person who installs PJS, or a systems operator should use any of the PJS Utilities.

The following utilities will be discussed:

Utility Name | Utility Description (Relevant Section)
PJSQINIT | PJS Request Queue Initialization Utility (Section 7.1)
PJSQMNT | PJS Request Queue Maintenance Utility (Section 7.2)

The PJS Request Queue Initialization Utility (PJSQINIT) initializes a new PJS Request Queue data set.

The PJS Request Queue Maintenance Utility (PJSQMNT) cleans up the PJS Request Queue and the PJS JCL Spool.

7.1 The PJS Request Queue Initialization (PJSQINIT) Utility

PJSQINIT is a utility that initializes a new PJS Request Queue data set. In most cases, a PJS Request Queue is initialized only during PJS installation.

Before you run PJSQINIT, the PJS Request Queue must be defined and allocated with IDCAMS. The new PJS Request Queue data set must be defined with RECSZ(144,4084), KEYS(17,0), and SHR(2). Most other data set attributes can be changed to optimize VSAM processing. For most sites, 1 or 2 cylinders of space should be sufficient.

The PJS Request Queue is initialized by writing a Queue Control Record into an empty VSAM KSDS.

PJSQINIT has no input parameters. The following DD statements are required:

PJSQ is the PJS Request Queue data set.

SYSOUT is the message data set, usually SYSOUT=*.

SYSABEND is the dump output data set, usually SYSOUT=*.

The member DEFPJSQ in the PJSINST library provides a sample job to define and initialize the PJS Request Queue data set. This job should be tailored to fit your installation standards, paying particular attention to the job card, the PJS Request Queue data set name, the volume serial number, and the allocation quantity.

7.2 The PJS Request Queue Maintenance (PJSQMNT) Utility

PJSQMNT is a utility that performs several maintenance functions on the PJS Request Queue and the PJS JCL Spool. This utility should be run periodically to eliminate out‑of‑date records from these PJS data sets.

PJSQMNT performs the following functions:

1. Deletes old job requests.

2. Deletes unreferenced event records.

3. Deletes unreferenced owner records.

4. Deletes unreferenced PJS JCL Spool members.

5. Re‑synchronizes PJS JCL Spool record counts.

6. Compresses the PJS JCL Spool data set.

Deletion of old job request records is controlled by the CMPTIME, DISTIME, and ERRTIME options in the PJS Options Table (PJSOPT). For more information on PJSOPT, please refer to Chapter 3.

PJSQMNT enqueues the PJS Request Queue while it runs: no other access is allowed when PJSQMNT runs. You can use PJS to schedule PJSQMNT to run at relatively quiet times of day. Since PJS is usually used to run jobs off‑hours, it's a good idea to run this utility late in the morning or early in the afternoon.

PJSQMNT has no input parameters. The following DD statements are required:

SYSOUT is the message data set, usually SYSOUT=*.

SYSABEND is the dump output data set, usually SYSOUT=*.

The member PJSQMNT in the PJSINST library provides a sample job to run the PJS Request Queue Maintenance Utility. This job should be tailored to fit your installation standards, paying particular attention to the job card. It's a good idea back up the PJS Request Queue and the PJS JCL Spool before you run this utility.

Prev | Table of Contents | Next

Copyright © Northrop Grumman, 1990, 2004. All rights reserved.