Update interval dialog options
The dialogs contain questions, directives, and data entry fields. You can enter the HELP command or press PF1 to obtain descriptions of the fields.
The following table lists the questions and directives that appear on the interval update dialog.
Interval dialog quick reference
Query | Page |
---|---|
Service name or description | Specify the name or description of the selected service interval. |
Specify scheduled service command | Enter the command text that you want to execute. The command must be a valid MainView SRM command. The command does not require any modifiers (for example, VSCAN SUF=01). |
On which system(s) should the command occur? | Use this option to enter the system ID where the command that is executing in this interval will run. You can assign a specific system, specify a set of systems by using a mask (a partial system name suffixed by an asterisk), or specify all systems by using an asterisk.
This parameter is required. The default for intervals that are created with the N (new) line command is all systems (*). |
Should this definition be active or inactive at SVOS start? | Use this option to specify the disposition of the interval when SVOS starts or when the interval is refreshed:
This parameter is required. Intervals that are created with the N (new) line command have a default of active. |
At what time of day should the command begin? | Use this option to specify the time that the interval should begin. Enter the time in military format (for example, 1320 = 1:20 P.M.)
This parameter is required. Intervals that are created with the N (new) line command have a default of 0800 (8:00 A.M.). Note: Start time (and start date) are used to calculate the number of total intervals, elapsed days, and qualified days that pass from one SVOS initialization to another. These options can be used to define time limitations for intervals. Setting a time of 0000 or using at product start causes a new start time and date at each SVOS start. Therefore, using total intervals, elapsed days, or qualified days to stop (expire) an interval in conjunction with at product start (or 0000 time) is not recommended. Entering 0000 for a start time or selecting at product start is useful only if you want the command defined for the interval to execute at the start of the SVOS address space. |
If 'at product start' align command | Use this option to specify the time alignment for the command if at product start was selected or a 0000 start time was entered. Selecting one of the options provides a consistent processing window for the command defined for the interval. If you do not specify this option, the time that SVOS initialized or the time that the interval first became active will be used without any alignment.
This selection is optional. |
How often should the command occur? | Use this option to specify the recurring interval time for the command, which is the duration in minutes between the executions of the recurring command.
This parameter is required. Intervals that are created with the N (new) line command have a default of 0060 (every hour). |
Which days of the week should this command occur? | Use this option to specify the day or days of the week on which the command should execute:
This selection is optional. Intervals that are created with the N (new) line command have a default of everyday. |
You can select specific weeks of the month to run the command in conjunction with the selected weekdays; for example, the second Tuesday of each month | If you want to execute the command on a day or days within a specific week or weeks within the month, you can select which weeks here. If you make a selection, the activity will execute only on the days within the weeks selected. _1st _2nd_ 3rd _4th If you select Tuesday for day of week and the second (2nd) for this option, the activity will execute on the second Tuesday of the month. This selection is optional. |
If there is a specific start date for this command enter it here | MMDDYYYY This option is in the extended dialog. Use this option to set a specific date for the interval to become active. The interval will not attempt to execute before the specified date. If no date is specified, the start date will be the date that the interval becomes active for the first time. Intervals that are created with the N (new) line command have a default of the date on which they were created. |
When should this command end each day? | Use this option to specify when the recurring command should stop executing within a 24 hour period:
This selection is optional. Intervals that are created with the N (new) line command have a default of never. |
If there is a specific end date or elapsed time frame for this command enter it here | Use this option to stop a recurring interval from processing on a specific date, after a set number of days or intervals. The counts that are calculated for the options (other than specific date) are valid through the recycling of the SVOS address space unless at product start or 0000 start time is used.
This selection is optional. Intervals that are created with the N (new) line command have a default of 00000000 for an end date. |
If you want this command to execute on specific dates, mark them here | Use this option to specify dates of the month on which you want the command to run. You can select any combination of dates from the first through the twenty-eighth. This option can be used in conjunction with other date options. If Tuesday was selected for day of week and the eighteenth, twenty-second, and twenty-fourth were selected in this option, the command will execute every Tuesday and on the eighteenth, twenty-second, and twenty-fourth of the month. This selection is optional. |
To have the command execute on the last specific day of the month, mark your selection here | Use this option to specify the last day in the month on which you want the command to run. _Sun _Mon _Tue _Wed _Thr _Fri _Sat You can select any combination of days. If Tuesday is selected in this option, the command will execute on the last Tuesday of the month. This option can be used in conjunction with other date options. If the 15th was selected in specific dates and Monday was selected in this option, the command will execute on the 15th of the month and the last Monday of the month. This selection is optional. |
To have the command execute on the last day of the month, mark your selection here | Use this option to cause the command to execute on the last day of the month. If selected, the command will run on the 28th, 29th (in leap year), 30th, or 31st of the month. This option can be used in conjunction with other date options. If the 15th was selected in specific dates and this option is also selected, the command will execute on the 15th and the last day of the month. This selection is optional. |
To have the command execute on the last weekday of the month, mark your selection here | Use this option to schedule the command to execute on the last weekday of the month. If selected, the command will run on the last Monday through Friday of the month. The day on which the command executes will vary depending on the month and year. This option can be used in conjunction with other date options. This selection is optional. |
To have the command execute on the last weekend day of the month, mark your selection here | Use this option to schedule the command to execute on the last weekend day of the month. If selected, the command will run on the last Saturday or Sunday of the month. Which day the command executes will vary depending on the month and year. This option can be used in conjunction with other date options. This selection is optional. |
To have a batch job execute after the command finishes processing, enter the member name here | Use this option to schedule the submission of a batch job. The job will execute after the interval command completes processing. Enter the name of the member that contains the batch job in the space provided. The member that contains the batch job must reside in the BBSLIB concatenation of the SVOS address space. This selection is optional. |
Comments
Log in or register to comment.