Policy interval dialogs
The short version is the initial dialog that is displayed when you work with policy intervals. This dialog covers the basic requirements for setting up an interval.
You can choose to display the extended dialog by entering EX on the COMMAND line of the dialog. To get back to the short version, enter SH on the COMMAND line of the extended dialog. You can toggle between the dialogs as needed.
The dialogs include 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 short and extended versions of the policy interval dialog.
Policy interval dialog quick reference
Query | Description |
---|---|
Policy name | This field specifies the name of the selected policy. |
What data should be collected? | Use this option to select the type of data to be collected during the interval:
This selection is required. Intervals that are created with the N (new) line command have a default of pool and volume space. |
Do you want to include catalog information with data set collection? | Use this option to determine whether to collect catalog information:
|
Do you want to obtain data set applications with data set collection? | Use this option to specify whether to include data set applications with data set collection:
|
What activities should be performed on the data? | Use this option to select the activity that will execute against the collected data during the defined interval:
Intervals that are created with the N (new) line command have a default of logging. |
On which systems should the activity occur? | Use this option to enter the system ID where the activity (Collection, Logging, or Logging and Automation) for this interval will run. You can assign a specific system, assign 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. Intervals that are created with the N (new) line command have a default of all systems (*). |
At what time of day should the activity 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 activity defined for the interval to execute at the start of the SVOS address space. |
If 'at product start' align activity | Use this option to specify the time alignment for the activity 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 activity 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 (refreshed) will be used without any alignment.
Use this option to set the alignment to the number of minutes that are specified past the hour regardless of when SVOS was started. If SVOS started at 9:10 A.M. and this option was set to 05 minutes past the hour, the start time would be set to 10:05 A.M. The format for this option is mm; valid values for mm are 01-59.
This selection is optional. |
How often should the activity occur? | Use this option to specify the recurring interval time for the activity, which is the duration in minutes between the executions of the recurring activity.
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 activity occur? | Use this option to specify the day or days of the week on which the activity 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 activity in conjunction with the selected weekdays; for example, the second Tuesday of each month | This option is in the extended dialog. If you want to execute the activity 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 only execute 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. |
Should this definition be active or inactive at SVOS start? | This option is in the short dialog. 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. |
How often do you want a full scan to run? | This option is in the short dialog. A full or partial scan can run to collect data for the interval. A partial scan can take less execution time but it does not collect all metrics. Use this option to indicate how often to run a full scan.
Example: If you enter Every 5 Intervals , a partial scan runs each time the interval executes, for five executions; on the sixth execution, a full scan runs. |
If there is a specific start date for this activity 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 activity end each day? | This option is in the extended dialog. Use this option to specify when the recurring activity 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 activity enter it here | This option is in the extended dialog. 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 activity to execute on specific dates, mark them here | This option is in the extended dialog. Use this option to specify dates of the month on which you want the activity to run. You can select any combination of dates from the 1st through the 28th. This option can be used in conjunction with other date options. If Tuesday was selected for day of week and the 18th, 22nd and 24th were selected in this option, the activity will execute every Tuesday and on the 18th, 22nd and 24th of the month. This selection is optional. |
To have the activity execute on the last specific day of the month, mark your selection here | This option is in the extended dialog. Use this option to specify the last day on which you want the activity to run during each month. _Sun _Mon _Tue _Wed _Thr _Fri _Sat You can select any combination of days. If Tuesday is selected in this option, the activity will execute on the last Tuesday of the month. This option can be used in conjunction with other date options. If the fifteenth was selected in specific dates and Monday was selected in this option, the activity will execute on the fifteenth of the month and the last Monday of the month. This selection is optional. |
To have the activity execute on the last day of the month, mark your selection here | This option is in the extended dialog. Use this option to cause the activity to execute on the last day of the month. If selected, the activity will run on the twenty-eighth, twenty-ninth (in leap year), thirtieth or thirty-first of the month. This option can be used in conjunction with other date options. If the fifteenth was selected in specific dates and this option is also selected, the activity will execute on the fifteenth and the last day of the month. This selection is optional. |
To have the activity execute on the last weekday of the month, mark your selection here | This option is in the extended dialog. Use this option to schedule the activity to execute on the last weekday of the month. If selected, the activity will run on the last Monday through Friday of the month. The day on which the activity 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 activity execute on the last weekend day of the month, mark your selection here | This option is in the extended dialog. Use this option to schedule the activity to execute on the last weekend day of the month. If selected, the activity will run on the last Saturday or Sunday of the month. Which day the activity 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 activity finishes processing, enter the member name here | This option is in the extended dialog. Use this option to schedule submitting a batch job. The job will execute after the interval activity 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.