Using Jobclass Support

Beginning with Release 3.1, Xchange features improved flexibility to allow users to set Xchange requests based on execution jobclass. A running time clock for all programs run under that jobclass will be started at the moment the request is first used and will run parallel to real time. The request, including its displacement from the real time and date, is retained until you delete it with the D (Delete) line command or reset it with the R (Reset) line command.

If an individual Xchange request is entered on the Simulated Date Time Settings screen for a job that happens to run in a class for which there is an active jobclass request, the date/time fields from the individual request will be used instead of the jobclass screen's date/time fields because specific individual requests always take precedence over jobclass requests.

In order for a class to be eligible for jobclass processing, it must have been defined with the Xchange parameter CLASS. For more information, see Task-3-2-2-Specify-Xchange-parameters. When the JOBCLASS primary command is entered on the command line of the Xchange Date Time Settings screen, the screen is displayed in jobclass format as shown in the following figure. All the classes that were designated with the CLASS parameter are displayed.

Simulated Date Time Settings Screen for Jobclass Support

Primary Commands-Using Jobclass Support

Enter primary commands in the COMMAND field at the top of the Simulated Date Time Settings screen. Except for the PRIMARY command shown as follows, only the standard ISPF primary commands are supported when in jobclass format. The END command returns to the standard Simulated Date Time Settings screen. The RETURN command returns you to ISPF.

PRIMARY

Display the list of valid primary commands.

Line Commands-Using Jobclass Support

The line commands described as follows can be entered if the user has the necessary authority. For more information on authority for jobclass line commands, see Milestone-8-Configuring-Xchange-external-security.

Three line commands are available for each of the jobclasses displayed on the Simulated Date Time Settings screen in jobclass format. If your site is using Xchange external security (SECUSE=YES,SECDFLT=DENY), the TSO userID of the person entering the line command must have update access to the JOBCLASS pseudo-data set name as described in Milestone-8-Configuring-Xchange-external-security. If that update access is not established, a NAUT (not authorized) error will be displayed under the Imsg column. If Xchange external security is not used (SECUSE=NO), any user can enter line commands on the Simulated Date Time Settings screen in jobclass format.

Status Codes-Using Jobclass Support

Status codes are displayed in the S portion of the C/S field next to each Xchange jobclass request. Any of the following status codes can be displayed:

Fields-Using Jobclass Support

Line commands can be entered next to each jobclass request in the C portion of the C/S field, and the desired date and/or time can be entered in the Requested Time fields. The S portion of the C/S field and the Imsg, Jobclass, and Current Simulated Time fields are display-only. The Filter row contains a series of mask fields, each corresponding to the column directly following it.

Filter Requested Time YYYY/MM/DD, HH:MM:SS

The mask for the Requested Time YYYY/MM/DD and HH:MM:SS fields. The initial values are all asterisks, which directs Xchange to display all jobclass requests for which the rest of the request entry fields match their corresponding masks. These masks are saved upon exit and restored upon entry.

An asterisk represents a single wildcard character in the position of the date or time where it is placed. For example, masks 20** and **25 would each result in the display of all jobclass requests for year 2025 — assuming the rest of the request entry fields match their masks. A mask of all blanks is valid. A combination of blanks and asterisks, or numeric data and asterisks, is also valid. If you enter all numeric data, validation rules are equivalent to that of the request entry date and time fields.

C/S

The command and status fields for each jobclass request. You can enter line commands in the C portion of the field. Status codes are displayed in the S portion of the field.

Imsg

The informational message area for each entry. When an asterisk (*) is displayed in the S portion of the C/S field, an informational error message will be displayed in the Imsg field.

Jobclass

The jobclass of each entry is displayed in this field. All jobclasses displayed have been defined with the Xchange parameter CLASS.

Requested Time YYYY/MM/DD

The year, month, and day that you want Xchange to simulate for jobs running in this jobclass. If the PREVDATE parameter is set to NO (Xchange CMSC PARMLIB member), dates prior to the current date are not allowed. The following entries are valid:

If you enter a value for the day (DD), the month and year are required. If you enter a value for the month (MM), the year is required. You can just enter the year. This field defaults to the current year, month and day. If you leave the DD field blank, an error will occur if the current day of the month is invalid for the month you specified — for example, if you entered February on July 31.

Requested Time HH:MM:SS

The hour, minute and second that you want Xchange to simulate for jobs running in this jobclass. The following entries are valid:

If you enter a value for seconds (SS), the hour and minutes are required. If you enter a value for minutes (MM), the hour is required. You can just enter the hour. This field defaults to the current hour, minute, and second for any values not specified.

Current Simulated Time YYYY/MM/DD and HH:MM:SS

These fields contain the date and time of the first time request issued by the first job running in this jobclass. These fields will remain blank until this occurs. Once these fields are populated, they will not change until the jobclass request is either deleted (D) or reset (R). This date/time field is used as the baseline from which Xchange creates a “delta” used to simulate a running time for all jobs executing in this jobclass.

PF Keys-Using Jobclass Support

Xchange supports the standard default ISPF keys.

Additional Considerations-Using Jobclass Support

The following limitations and special concerns apply to Xchange jobclass support:

• Jobclass support is limited to batch jobs. Started Tasks (STCs) and TSO Users (TSUs) are unaffected by jobclass requests.
• Specific, non-jobclass requests which cover jobs running in the same class as an active jobclass request override that jobclass request. The date/time of the non-jobclass request is used for the exchange.
• Batch CICS/IMS regions that run in a class that happens to be covered by an active jobclass request will be exchanged at the region level.
• A batch job will not be exchanged if the class under which it runs is not defined to Xchange with the parameter CLASS. Such jobs are displayed on the Simulated Date Time Settings screen with a JAUT error message.