Prev | Table of Contents | Next

3. PJS Specification Conventions

Some value specifications are used in many PJS commands and parameters. This manual will refer to the information in this chapter. All specifications and descriptions are valid under TSO or ISPF. Any exceptions will be discussed in Chapter 4 and Chapter 5.

The following specifications will be discussed:

· The owner‑ID specifies who plans to work on a job request, calendar, or event. The owner‑ID is part of the request‑ID, the calendar‑ID, and the event‑ID. For more information, please refer to Section 3.1.

· The request‑ID specifies who "owns" a job request. For more information, please refer to Section 3.2.

· The calendar‑ID specifies who "owns" a calendar. For more information, please refer to Section 3.3.

· The event‑ID specifies who "owns" an event. For more information, please refer to Section 3.4.

· Time Specifications are used to specify values such as the time of submission. For more information, please refer to Section 3.5.

· Date Specifications are used to specify values such as the first date of submission or the dates on a PJS calendar under TSO. For more information, please refer to Section 3.6.

· Job Request Status Values describe the various status values that a PJS Job Request can have. For more information, please refer to Section 3.7.

3.1 The owner‑ID

This value specifies who "owns" a given PJS entity:

owner‑ID specifies who "owns" the job request, calendar, or event on which you plan to work. Ordinarily, you will specify the owner‑ID as part of a request‑ID, a calendar‑ID, or an event‑ID.

In most cases, owner‑ID is only a synonym for a user‑ID. However, site standards can ascribe other meanings to the value of owner‑ID; for example, your site may define an owner‑ID as either a user‑ID or a TSO group name.

Under TSO, the default is your TSO user‑ID. Under ISPF, the default is the value saved in the ISPF profile. If you plan to work on a job request, a calendar, or an event under the default, you can omit this specification.

Only authorized users can work on another owner's job requests, calendars, or events. Because authorization is site‑specific, your site may restrict your access to other user‑IDs or owner‑IDs.

A valid value is 1 through 8 characters long. The first character must be alphabetic. For more information on valid values you can specify for owner‑ID, please contact your Site Administrator.

3.2 The request‑ID

The request‑ID identifies individual job requests. When you work with a job request, you will need to specify a request‑ID in the [owner‑ID.]req‑number format, where:

owner‑ID specifies who "owns" the job request. For more information on owner‑ID, please refer to Section 3.1.

req‑number is the number PJS assigns to the job request after it has been created. You cannot specify a req‑number for a job request you plan to add to the PJS Request Queue.
If you plan to work on existing job requests, you must specify a req‑number. A valid value is 1 through 3 digits long. If you have forgotten the req‑number, you can display a list of your job requests under TSO or ISPF.

3.3 The calendar‑ID

The calendar‑ID identifies individual calendars. If you work with a calendar, you will need to specify a calendar‑ID in the [owner‑ID.]cal‑name format, where:

owner‑ID specifies who "owns" the job request. For more information on owner‑ID, please refer to Section 3.1.

cal‑name is the name of the calendar. A valid value is 1 through 8 characters long. The first character must be alphabetic.
If you create a calendar, you must specify a valid and distinct calendar name. If you plan to work on an existing calendar, the cal‑name must exist.

3.4 The event‑ID

The event‑ID identifies individual events and job request events. If you work with an event, you will need to specify an event‑ID in the [owner‑ID.]event‑name format, where:

owner‑ID specifies who "owns" the job request. For more information on owner‑ID, please refer to Section 3.1.

event‑name is the name of the event or job request event. A valid value is 1 through 8 characters long. The first character must be alphabetic.
If you specify a new job request event, you must specify a valid and distinct event name. If you plan to work with an existing event, the event‑name must exist.

3.5 Time Specifications

When you work with job requests, you will need to specify values such as the time you want PJS to submit a job for execution. PJS enables you to specify an absolute time or a relative time.

3.5.1 Absolute Time

An absolute time is a fully specified time, for example, 10:22 or 10:22PM.

To specify an absolute time, use the hh:mm[AM|PM] format:

hh is the hour. If you specify AM or PM, hh must be between 01 and 12. If you do not specify AM or PM, the 24‑hour clock is assumed, and hh must be between 00 and 23.

mm is the minute. Valid values are 00 through 59.

AM means that the specified time is between midnight and noon. 12:00 AM is midnight.

PM means that the specified time is between noon and midnight. 12:00 PM is noon.

3.5.2 Relative Time

A relative time does not require a time specification, but you do have to specify a number. That number is added to the current system time to determine the time of submission. For example, if you plan to run a job "an hour from now," you can enter a relative time value of 1.

To specify a relative time, use one of the following formats:

*+hh to add the number of hours (hh) to the current system time.

*+:mm to add the number of minutes (mm) to the current system time.

*+hh:mm to add the number of hours (hh) plus minutes (mm) to the current system time.

In each of the above cases:

hh is the number of hours to be added to the current system time. Valid values are 00 through 99.

mm is the number of minutes to be added to the current system time. Valid values are 00 through 99.

3.6 Date Specifications

When you work with job requests, you may need to specify values such as the day on which PJS will submit a job for execution. If you use TSO calendar commands, you will need to specify date values. PJS enables you to specify an absolute date or a relative date.

3.6.1 Absolute Date

An absolute date is a fully specified date, for example, 10/22/2002. Normally PJS accepts and displays dates in U.S. format (that is mm/dd/yyyy). Your installation may have changed this to use the European date format (that is dd/mm/yyyy). If you are not sure which format your installation uses, check with the person who installed PJS.

To specify an absolute date in U.S. format, use the mm/dd/yyyy format. To specify an absolute date in European format, use the dd/mm/yyyy format. In both cases:

mm is the month. Valid values are 01 through 12, i.e., January through December.

dd is the day of the month. Valid values are 01 through 31.

yyyy is the year. This may be a 2‑digit year, or a 4‑digit year. 2‑digit years are assumed to be in the 21st century, i.e. 2000 through 2099. Valid values are 00 through 99, or 2000 through 2099.

The rest of this document assumes your installation uses the U.S. data format. If you are using the European data format, simply replace the U.S. format shown with the European format.

3.6.2 Relative Date

A relative date does not require a date specification, but you do have to specify a number. That number is added to the current system date to determine the day of submission. For example, if you plan to run a job "a week from today," you can enter a relative date value of 7.

To specify a relative date, use the *+ddd format, where:

*+ indicates a relative date.

ddd is the number of days to be added to the current system date. Valid values are 001 through 999.

3.7 Job Request Status Values

The Job Request Status indicates the current state of processing for a job request. The following are the possible values for the Job Request Status:

WAIT means that the job request is waiting, either for it’s submit time, or for it’s events to be posted.

COMPLETE means that the job request is finished. The job will not be submitted again unless the job request is changed. To change the status back to WAIT, modify the job request, entering a new Start Date and Start Time and either the ENABLE TSO command option, or enter YES in the Enabled input field of the Modify Job Request ISPF panel.

DISABLED means the job request is on the PJS Request Queue but is not active. This status is usually set by the user “disabling” the job request. It can also be set if the Submit Window Time for the job request was exceed, if the Window Option is also set to DISABLE. To change the status back to WAIT, modify the job request with either the ENABLE TSO command option, or enter YES in the Enabled input field of the Modify Job Request ISPF panel.

ERROR means that the PJS System Task encountered an error while processing this job request. To change the status back to WAIT, correct the error, then modify the job request with either the ENABLE TSO command option, or enter YES in the Enabled input field of the Modify Job Request ISPF panel.

SUBMIT means that the job request is being processed by the PJS System Task. The job request cannot be modified until this process completes. The user cannot change this status. If this status persists contact your PJS site administrator.

Prev | Table of Contents | Next

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