Specifying Xchange Requests by Execution Date/Time/Constant Using the ISPF Interface

You can also specify Xchange requests that will only trigger date/time substitution upon a matching job’s execution if the current date and time is greater than or equal to the Beginning Execution Date and Time and less than or equal to the Ending Execution Date and Time specified in the request. The simulated date and time are calculated from a Constant number of Days, Hours, and Minutes before or after the Beginning Execution Date and Time.

The first request shown in the following figure instructs Xchange to simulate a date 30 Days, 4 Hours, and 4 Minutes after the Beginning Execution Date, or 2019/05/31 at 10:04:00. The simulated date and time will only be substituted when Job TSTJOB01 is executed on 2019/05/01 beginning at 6:00:00 through the end of the day.

Request Settings by Execution Date

------------------ Request Settings by Execution Date ------- Row 1 to 7 of 14
COMMAND ===>                                                   SCROLL ===> PAGE
                                                               System ID: AC12
Line Commands: H - Set and Hold R - Reset D - Delete
Status Codes: Q - Queued P - Pending A - Active N - Not Active * - Error

                                                 Beg Exec/End Exec
                                                 **** ** ** ****** - Constant -
Filter:      ******** ******** ******** ******** **** ** ** ****** **** ** ** *
C/S Owner    Jobname Stepname Procstep Program YYYY/MM/DD HHMMSS Days Hr Mn I
_ Q YOURUID TSTJOB01 *_______ *_______ *_______ 2019 05 01 060000 0030 04 04 +
                                                 2019 05 01 235959
_ Q YOURUID TSTJOB02 *_______ *_______ *_______ 2019 05 02 060000 0030 04 04 -
                                                 2019 05 02 235959
_            ________ ________ ________ ________ ____ __ __ ______ ____ __ __ _
                                             ____ __ __ _____

The second request shown in the Request Settings by Execution Date figure instructs Xchange to simulate a date 30 Days, 4 Hours, and 4 Minutes prior to the Beginning Execution Date specified, or 2019/04/01 at 1:56:00. The simulated date and time will only be substituted when Job TSTJOB02 is executed on 2019/05/02 beginning at 6:00:00 through the end of the day, providing that BMC PARMLIB Xchange parameter PREVDATE is set to YES.

These requests will remain queued until such time as they are deleted or expire.

Pressing PF3/End from the Request Settings by Execution Date screen will return you to the main ISPF Simulated Date Time Settings screen (see the following figure).

Queued Execution Date/Time/Constant requests are displayed with a Status of X to distinguish them from other types of requests. The Date and Time displayed here for these requests is the Simulated Date and Time. It is calculated when the request is created from the Constant values provided as an offset from the Beginning Execution Date and Time provided on the Request Settings by Execution Date screen.

Tip

The Request Settings by Execution Date screen remains unchanged and displays only requests, not messages.

Simulated Date Time Settings Screen Showing Execution Date/Time/Constant Requests

BMC AMI DevX Xchange ---- Simulated Date Time Settings ---- Row 1 to 14 of 14
COMMAND ===>                                                 SCROLL ===> CSR
                                                             System ID: CW40
Type Legal on the command line for Copyright/Trade Secret Notice Information
Line Commands: S - Set H - Set and Hold R - Reset D - Delete A - Set Active
Status Codes: Q - Queued P - Pending A - Active E - Executing * - Error
               C - Completed N - Not Active X - Queued Exec D/T
Filter:      ******** ******** ******** ******** * **** ** ** ** ** **
C/S Owner    Jobname Stepname Procstep Program GHD YYYY/MM/DD HH:MM:SS Jobno
_ X YOURUID TSTJOB01 *_______ *_______ *_______ N 2019 05 31 10 04 00
_ C YOURUID TSTJOB01 *_______ *_______ *_______ N 2019 05 31 10 04 00 23284
_ C YOURUID TSTJOB01 GO______ ________ XGBASMLE N 2019 05 31 10 04 00 23284
_ X YOURUID TSTJOB02 *_______ *_______ *_______ N 2019 04 01 01 56 00
_ C YOURUID TSTJOB02 *_______ *_______ *_______ N 2019 04 01 01 56 00 23286
_ C YOURUID TSTJOB02 GO______ ________ XGBASMLE N 2019 04 01 01 56 00 23286
_            ________ ________ ________ ________ _ ____ __ __ __ __ __
_            ________ ________ ________ ________ _ ____ __ __ __ __ __

Execution Date/Time and Constant Fields

Use the Beginning Execution Date and Time fields to specify the earliest Date and Time of any planned executions of a matching pattern job request. Use the Constant fields to specify how far before or after the Beginning Execution Date and Time you want Xchange to simulate the date and time. Use the Ending Execution Date and Time fields to specify the latest Date and Time of any planned executions of a matching pattern job request. When a program of a matching pattern job request is executed between the Beginning Execution Date and Time and Ending Execution Date and Time, inclusive, date and time substitution will occur. Otherwise, it will not. The Simulated Date and Time is calculated at the time the request is created from the Constant number of Days, Hours, and Minutes before or after the Beginning Execution Date and Time.

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

Tip

Only those fields unique to Xchange’s Execution Date/Time/Constant format are described in this section. For descriptions of other fields, see Fields or Constants-Fields.

Filter Beginning and Ending Execution Date (YYYY/MM/DD) and Time (HH:MM:SS)

The masks for these fields are identical to those on the Simulated Date Time Settings screen. The only difference is the meaning of the Date and Time fields that these masks represent. For more detailed information, see Fields.

Filter Constant Days, Hours (Hr), Minutes (Mn), and Indicator (I)

The masks for these fields are identical to those on the Simulated Date Time Settings screen in Offset Format. The only difference is the meaning of the Constant fields that these masks represent. For more detailed information, see Constants-Fields.

Beginning Execution Date (YYYY/MM/DD)

The Beginning Execution Date represents the earliest date that a program of a matching pattern job request can execute for Date/Time substitution to occur. If the BMC PARMLIB Xchange parameter PREVDATE 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:

YYYY	1900 to 2041 (2099 if POSTEPOC parameter is set to YES)
MM	01 to 12
DD	01 to 28 (February);
	01 to 29 (February during a leap year);
	01 to 30 (April, June, September, and November); or
	01 to 31 (January, March, May, July, August, October, and December).

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 only the year, because it is always required. This field defaults to the current month and day if not specified. 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 enter February on July 31.

Beginning Execution Time (HH:MM:SS)

The Beginning Execution Time represents the earliest time that a program of a matching pattern job request can begin execution for Date/Time substitution to occur.

HH	00 to 23
MM	00 to 59
SS	00 to 59

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 only the hour, because it is always required. This field defaults to the current minute and second if these values are not specified.

Ending Execution Date (YYYY/MM/DD)

The Ending Execution Date represents the latest date that a program of a matching pattern job request can execute for Date/Time substitution to occur. If the BMC PARMLIB Xchange parameter PREVDATE 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:

YYYY	1900 to 2041 (2099 if POSTEPOC parameter is set to YES)
MM	01 to 12
DD	01 to 28 (February);
	01 to 29 (February during a leap year);
	01 to 30 (April, June, September, and November); or
	01 to 31 (January, March, May, July, August, October, and December).

Ending Execution Time (HH:MM:SS)

The Ending Execution Time represents the latest time that a program of a matching pattern job request can execute for Date/Time substitution to occur.

HH	00 to 23
MM	00 to 59
SS	00 to 59

Constant Days

Constant Days represents a constant number of Days before or after the Beginning Execution Date and Time used to calculate the simulated date and time. Valid entries are from 0 to 9999. The default is 0.

Constant Hours (Hr)

Constant Hours represents a constant number of Hours before or after the Beginning Execution Date and Time used to calculate the simulated date and time. Valid entries are from 0 to 23. The default is 0.

Constant Minutes (Mn)

Constant Minutes represents a constant number of Minutes before or after the Beginning Execution Date and Time used to calculate the simulated date and time. Valid entries are from 0 to 59. The default is 0.

Constant Indicator (I)

Constant Indicator represents the direction in relation to the Beginning Execution Date and Time used to calculate the simulated date and time.

Valid entries are + (plus) for an offset after the Beginning Execution Date and Time and - (minus) for an offset before the Beginning Execution Date and Time. The default is +. If the BMC PARMLIB Xchange parameter PREVDATE is set to NO (see Task-3-2-2-Specify-Xchange-parameters), date/time offsets into the past are not allowed.