Schedules for data protection reports and scheduled object auditing requests for all-objects and prioritized objects audits are typically set to run by frequency and time of day. They can also be set to run on specific dates or days of the week, or on relative days of the month.
Schedules for prioritized object auditing requests identify the range of time during which requests can be submitted every day and identify other criteria for determining how MIMIX prioritizes which objects are to be audited.
The following parameters are available on the SETMMXSCD command.
Schedule type
Specifies the type of event that the schedule is for. You must specify a value.
-
Use *AUDIT for either type of automatically submitted audits. When specified, you must also specify values for Audit rule and Data group definition.
-
Use *PROC for data protection reports. When specified you must also specify values for Procedure and Node (system definition).
Audit rule
Specifies the audit rule for which scheduling and object selection criteria will be set for the specified data group.
Data group definition
Specifies the three-part qualified name of the data group definitions to which the specified scheduling and priority auditing criteria applies for the specified audit rule.
Procedure
Specifies the name of the data protection report procedure to which the specified scheduling criteria applies.
Node (system definition)
Specifies the node (system definition) to which the specified procedure and scheduling criteria applies.
Schedule
Specifies the scheduling information for the specified data protection report procedure or audit. MIMIX uses this information to automatically submit requests to run the report or audit.
-
When the Schedule type is *AUDIT, the values you specify for Schedule elements determine when audits that compare all objects selected by data group configuration entries for the specified rule are performed.
-
When the Schedule type is *PROC, the values you specify for Schedule elements determine when the procedure will run on the node to check whether existing libraries, directories, or folders on that node are protected by MIMIX replication.
Scheduled dates are entered and displayed in job date format. When the job date format is Julian, the equivalent month and day are used to determine when to schedule requests.
State
Specify whether the schedule is enabled or disabled for the specified procedure or audit. The value *ENABLED is required to allow automatic submission.
Frequency
Specifies how often MIMIX submits a request to run the scheduled activity. The values specified for other elements further qualify the specified frequency.
Scheduled date
Specifies a date, in job date format, on which MIMIX submits the request. If the job is to be submitted more than once, this date is used to calculate subsequent submission dates.
Scheduled day
Specifies the days of the week on which MIMIX submits the request. If today is the day of the week that is specified and the scheduled time has already passed, the request is submitted on the next occurrence of a specified day.
For example, if *FRI is specified for Scheduled day and 12:00:00 is specified for Scheduled time and you are setting this policy at 11:00 a.m. on a Friday, the request is submitted the same day. If you are setting the policy at 4:00 p.m. on a Friday or at 11:00 a.m. on a Monday, the request is submitted the following Friday.
Scheduled time
Specifies the time on the local system at which MIMIX submits the request on the scheduled date or day. Although the time can be specified to the second, the activity involved in submitting a job and the load on the system may affect the exact time at which the job is submitted.
Time can be specified with or without a time separator.
Without a time separator, specify a string of 4 or 6 digits (hhmm or hhmmss) where hh = hours, mm = minutes, and ss = seconds. Valid values for hh range from 00 to 23. Valid values for mm and ss range from 00 to 59.
With a time separator, specify a string of 5 or 8 digits where the time separator specified for your job is used to separate the hours, minutes, and seconds. If this command is entered from the command line, the string must be enclosed in apostrophes. If a time separator other than the separator specified for your job is used, this command will fail.
Relative day of month
Specifies the relative day of the month on which MIMIX submits the request. A relative day is only valid when the schedule Frequency is *MONTHLY and Scheduled day is a value other than *NONE.
For example, if you specify *MONTHLY for Frequency, *TUE for Scheduled day, and 1 for Relative day of the month, the job is submitted on the first Tuesday of every month.
Priority audit
Specifies when priority-based audit requests for the specified data group and audit rule are allowed to automatically start and how often replicated objects are eligible for auditing based on their priority classification. A prioritized audit can run multiple times during the specified range, approximately once per hour or more often. This parameter is ignored for schedule types of *PROC.
The #DGFE rule does not support priority auditing. The priority audit value for #DGFE audit is always set to *DISABLED and cannot be changed.
State
Specifies whether priority auditing is enabled or disabled for this data group and audit rule. The value *ENABLED is required to allow automatic submission.
Start after
Specifies the time after which priority-based audits are allowed to start. This is the beginning of a range of time during which priority-based audits can start each day. The value *ANY allows priority-based audits to run repeatedly throughout the day.
Start until
Specifies the end of the time range during which priority-based audits are allowed to start. Priority-based audits can start until this time. This value is ignored when Start after is *ANY.
New objects selected
Specifies the frequency at which new objects are considered for auditing. A new object is one that has not been audited since it was created.
Changed objects selected
Specifies the frequency at which changed objects are considered for auditing. A changed object is one that has been modified since the last time it was audited.
Unchanged objects selected
Specifies the frequency at which unchanged objects are considered for auditing. An unchanged object is one that has not been modified since the last time it was audited.
Audited with no diff.
Specifies the frequency at which objects with no differences are considered for auditing. An object with no differences is one that has not been modified since the last time it was audited and has been successfully audited on at least three consecutive audit runs.