End of support

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Policy interval dialogs

This section describes the options that are found in the short and extended versions of the policy dialog.

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:

  • Pool and volume space

    Collects volume and pool space information

  • Data set space

    Collects data set information

  • Data set space with Bscan

    Collects data from the BCDS

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 not include Catalog information

    Does not attempt to retrieve catalog information.

  • Obtain Catalog information from the VVDS first

    Collects catalog information from VVDS first; if the VVDS is not found, retrieves data from the catalog.

  • Obtain Catalog information only from the Catalog

    Collects catalog information from the catalog and does not use VVDS data.

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:

  • Yes

    Includes application data.

  • No

    Does not include application data.

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:

  • Logging

    If pool and volume data is being collected and you select logging , the data will be written to the MainView SRM space collection database, as defined in the SMDBASxx member that is defined in your SVOS PARMLIB concatenation. If data set information is being collected during the interval, the data will be written to the VSCAN Master file.
     

  • Automation

    Automation will be performed against the data collected; logging will not occur. For automation to occur, at least one solution name must be coded as part of the solution list for the interval. Enter AUTO on the COMMAND line of the policy update dialog to display the automation solutions dialog where the solution names can be entered. The named solutions should match those listed in the active RLST member of the AUTO function that is related to the data that is being collected.
     

  • Logging and automation

    Logging and automation will occur against the data that is being collected.

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.

  • Specific system

    The activities that are defined for the interval will run only on the system that is specified, regardless of systems on which the policy member SMPOLIxx is active. If SYSA is entered, the activity will run only on SYSA.
     

  • System mask / asterisk

    Systems will execute the defined activity if they match the masking criteria where the SMPOLIxx member is shared and active. If SY* is entered, the SVOS address space on any system with the name starting with SY will execute the activity (assuming the policy definition is defined and active on those systems). If an asterisk (*) is entered, all systems where the policy member is active will execute the activity. Using an asterisk or mask can cause duplicate data to be logged and, if automation is selected, duplicate automation processing. For more information, see Sysplex considerations when using policies to manage pools, storage groups, and volumes.

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.)

  • HHMM

    The start time is the initial time the interval can become active and it is used to calculate the subsequent execution of intervals based on the interval time that is supplied. A start time of 1320 together with an interval time of 60 minutes will cause the interval activity to run at 1320, 1420, 1520, and so on in a 24-hour cycle unless an end time is supplied.

    The time that the interval actually starts depends on when the interval is activated. That is, if the SVOS address space initializes at 2:00pm (1400) and the start time for the interval is defined as 1:20pm (1320) with an interval time of 60 minutes, the interval will first execute at 2:20pm (1420). If you use the same parameters but have SVOS initialize at 9:00 A.M., the interval first executes a 9:20 A.M. (assuming no stop time was supplied). If you specify a stop time of 6:00 P.M. (1800) for the interval, creating an operation window of 1:20 P.M. to 6:00 P.M., and SVOS initialized at 9:00 A.M., the interval will not execute until 1:20 P.M.

    Entering 0000 for a start time is the same as selecting at product start, which is an option available in the extended dialog. To enter midnight, type 2400.

  • At product start

    This option is available in the extended dialog. This option causes the activity to execute immediately upon SVOS initialization and sets the interval start time to that time. This set time will be used as the start time for the interval until the next SVOS initialization or until a specific start time is defined for the interval. If at product start or 0000 start time is defined for the interval and SVOS initializes at 9:13 A.M., the interval will execute at 9:13 A.M., its start time will be set to 9:13 A.M., and the recurring intervals will be calculated from 9:13 A.M. If the interval is created after SVOS initialization, the interval time will be the first time that the interval becomes active by using the R (refresh) command.

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.

  • At the top of the hour

    Use this option to set the alignment to the top of the hour regardless of when SVOS was started. If SVOS started at 9:10 A.M., using this option would cause the start time to be set at 10:00 A.M. The subsequent execution of the activity will be calculated from 10:00 A.M.

  • Minutes past the hour

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.

  • At midnight

    This option adjusts the execution interval times based on the recurring interval time to ensure that execution occurs at midnight. If SVOS started at 6:10 P.M. and the interval time was 0090 minutes, the first execution would be at 6:10 P.M. followed by 7:30 P.M., 9:00 P.M., 10:30 P.M., midnight, 1:30 A.M., and so on.

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.

  • MMMM

    Valid entries are 0001–1440. If 0060 is entered, the interval will execute every hour. Entering 1440 causes the interval to execute once a day. This selection is the same as selecting once each day, which is an option in the extended dialog.

  • Once each day

    This option is in the extended dialog. It causes the interval to execute once a day and is the same as entering 1440.

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:

  • _Sun _Mon _Tue _Wed _Thr _Fri _Sat

    You can select any one, a combination, or all of the days.

  • Everyday

    Select everyday to schedule the activity seven days a week. Use this option instead of marking each individual day.

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.

  • Active

    Select active to cause the interval to be added to the policy queue and allow the activity to execute at the specified times.

  • Inactive

    Select inactive to cause the interval to be added to the policy queue but prevent the activity from executing at the specified times.

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.

  • Always

    Select Always to run a full scan each time an interval executes.
     

  • Never

    Select Never to never run a full scan.
     

  • Every__Intervals

    Select Every__Intervals to run a full scan after a specified number of intervals.

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.

  • Never

    Specifying never allows the interval to recur indefinitely unless an end date or other limitation (elapsed days, days processed or total intervals) has been specified.
     

  • Intervals a day

    With this option you can limit the number of times the interval will execute within a 24 hour period. After the interval count has been reached the activity will stop recurring until the next day where it will start the count over. This field accepts a four-digit number (0001-1440). If the number entered exceeds the number of interval occurrences that can occur within a 24 hour period based on the interval time, this option will be ignored.
     

  • HHMM

    Use this option to set a specific time in military format when the interval should stop executing. When this time is reached, the interval will stop recurring until the next defined start time occurs. If a start time of 0800 (8:00 A.M.) was entered and an end time of 2300 (11:00 P.M.) was entered, the activity will execute at its interval cycle from 8:00 A.M. until 11:00 P.M. Processing for the interval will resume at 8:00 A.M. the following day.

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.

  • Elapsed days

    By selecting elapsed days, the recurring interval will stop processing after the specified number of calendar days is reached. The days are calculated from the start date that is defined for the interval. If the number 10 is entered and the interval starts the first of the month it will execute through the tenth of the month. The field accepts a four digit number (0001-9999).
     

  • Days processed

    By selecting days processed, the recurring interval will stop processing after the specified number of processing days is reached. The days are calculated from the start date that is defined to the interval and increments for the days that the interval is actually processing. If the number nine is entered and the interval executes only once a week, the interval will run for nine weeks before it expires. If the interval is set to run three times a week, it expires after three weeks. The field accepts a four digit number (0001-9999)
     

  • total intervals

    By selecting total intervals, you can limit the total number of occurrences that the interval will have. After the specified number is reached, the interval becomes expired and will not execute again unless the interval definition is updated. This field accepts a four-digit number (0001-9999).
     

  • MMDDYYYY

    Enter the specific date that the recurring interval should stop executing (expire). The interval will stop executing on the specified date and will not execute again unless the definition is updated.

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.

Was this page helpful? Yes No Submitting... Thank you

Comments