Fields for Specifying Requests in ISPF

The Owner and Jobno fields and the S portion of the C/S field are display-only. You can type data into all other fields. The Filter row contains a series of mask fields, each corresponding to the column directly following it.

Filter Jobname

The mask for the Jobname field. The initial value is all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry.

An asterisk represents a single wildcard character in the position of the jobname where it is placed. For example, masks TST***** and ***JOB** would each result in the display of all job requests associated with jobname TSTJOB01 — assuming the rest of the request entry fields match their masks. However the masks TST*    , *JOB01  , and *JOB*   , would each result in the display of no job requests for jobname TSTJOB01, even if the rest of the request entry fields match their masks. Any character is valid in this field.

Filter Stepname

The mask for the Stepname field. The initial value is all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry.

An asterisk represents a single wildcard character in the position of the stepname where it is placed. For example, masks STEP****, ****01  , and ****01** would each result in the display of all job requests associated with stepname STEP01 — assuming the rest of the request entry fields match their masks. However the masks STEP*   , *01, and *01* would each result in the display of no job requests for stepname STEP01, even if the rest of the request entry fields match their masks. Any character is valid in this field.

Filter Procstep

The mask for the Procstep field. The initial value is all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry.

An asterisk represents a single wildcard character in the position of the procstep where it is placed. For example, masks PROC****, ****01  , and ****01** would each result in the display of all job requests for procstep PROC01 — assuming the rest of the request entry fields match their masks. However the masks PROC*   , *01, and *01* would each result in the display of no job requests for procstep PROC01  , even if the rest of the request entry fields match their masks. Any character is valid in this field.

Filter Program

The mask for the Program field. The initial value is all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry.

An asterisk represents a single wildcard character in the position of the program where it is placed. For example, masks PRGM**** and ****0001 would each result in the display of all job requests for program PRGM0001 — assuming the rest of the request entry fields match their masks. However the masks PRGM*    and *0001 would each result in the display of no job requests for program PRGM0001, even if the rest of the request entry fields match their masks. Any character is valid in this field.

Filter GHD

The mask for the Global Hold Date/Time GHD) option field. The initial value is an asterisk, which directs Xchange to display all job requests for which the rest of the request entry fields match their corresponding masks. This mask is saved upon exit and restored upon entry.

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

The mask for the YYYY/MM/DD and HH:MM:SS fields. The initial values are all asterisks, which directs Xchange to display all job requests for which the rest of the request entry fields match their 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 job 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 display for each entry. You can enter line commands under the C portion of the field. For a listing and description of the line commands, see Line Commands. Status codes are displayed under the S portion of the field. For a listing and description of the status codes, see Status-Codes.

Owner

The ID of the user who created the pattern job request when displayed on a request line (a line without a job number present)—or the ID of the user who initiated the job when displayed on a non-request line (a line with a job number present). This is a display only field. The Owner user ID on a request line is also used in external security checking. See Milestone-8-Configuring-Xchange-external-security.

Xchange may also display ERR= followed by a four-letter message code in the Owner field to indicate a problem with the pattern job request. For more information on message codes, see Owner-Field-Messages.

Jobname

The name of the MVS job or jobs for which to simulate the system date and time. You can specify a single job request or a number of job requests. To specify a single job request, you must enter a job name that exactly matches the name of the job being executed. To specify multiple job requests with a single entry, you may supply leading asterisks, embedded asterisks or trailing asterisks anywhere within the job name. A leading asterisk and an embedded asterisk represent a single character. A trailing asterisk represents one or more characters.

An error message is displayed if:

• You do not enter a job name. There is no default for the Jobname field.
• You specify a job name that is the same as a previous job pattern request.
• You specify more than one request for a job name.
• You enter only a single asterisk and nothing else for the job name. You must enter other characters.

Error messages and abend codes are documented in Xchange-Messages.

Stepname

The name of a specific step or steps within a job request. To specify a single step, enter the exact step name in this field. To specify multiple steps with a single entry, you may supply leading asterisks, embedded asterisks, or trailing asterisks anywhere within the step name. A leading asterisk and an embedded asterisk represent a single character. A trailing asterisk represents one or more characters. Specifying only an asterisk in this field requests all steps in a job request. The Stepname field defaults to an asterisk.

Procstep

The name of a procedure step or steps within a job request. To specify a single procedure step, enter the exact procedure step name in this field. To specify multiple procedure steps with a single entry, you may supply leading asterisks, embedded asterisks, or trailing asterisks anywhere within the procedure step name. A leading asterisk and an embedded asterisk represent a single character. A trailing asterisk represents one or more characters. Specifying only an asterisk in this field requests all procedure steps in a job request. The Procstep field defaults to an asterisk.

Program

The name of the program specified on the EXEC PGM= JCL statement. To specify a single program, enter the exact program name in this field. Individual subprograms cannot be independently exchanged, but any subprograms called by the program specified will also be exchanged. To specify multiple programs with a single entry, you may supply leading asterisks, embedded asterisks, or trailing asterisks anywhere within the program name. A leading asterisk and an embedded asterisk represent a single character. A trailing asterisk represents one or more characters. Specifying only an asterisk in this field requests all programs in a job request. The Program field defaults to an asterisk.

This field also displays a program name that was specified, either explicitly or implicitly, with the request parameter of an Xchange batch step or with the XCHANGE command from within a Code Debug TSO session.

GHD

The GHD field specifies the Global Hold Date/Time option. Setting this option to Y (YES) eliminates the running clock completely, from job start to the first date/time request and between date/time requests. The default is N (NO).

YYYY/MM/DD

The year, month, and day that you want Xchange to simulate. If the PREVDATE parameter is set to NO (see Task 3.2.2: Specify Xchange parameters), dates prior to today’s 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 enter just 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.

HH:MM:SS

The hour, minute, and second that you want Xchange to simulate for the specified date. 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 enter just the hour. This field defaults to the current hour, minute, and second for any values not specified.

Jobno

The low-order 5 position of the job number of the request. This is a display-only field. The first completed (C) request entry with a particular job number indicates only that a jobstep was executed that matched the corresponding request. Each additional completed entry (if any) with the same job number is the result of one or more actual date/time exchanges. See the Completed Pattern Job Requests figure.