|
|
|
While creating a monitor definition, you can specify monitoring by day-of-week, time, and date. You can specify scheduling criteria for individual monitor definitions, or select from permanent "shift" definitions that are defined by the administrator. For example, you might have schedules for weekend processing that can be reused every weekend.
To create a schedule for a monitor:
The Administration Option Menu displays.
CA MAT ------------------ Administration Option Menu ------------------------ OPTION ===> 1 Associations - Define module/Csect functions Userid: TUNUSER 2 Pseudo - Define pseudo groups Server ID: MATUNER 3 Content Help - Update content-sensitive help Status: ACTIVE 4 Scheduling - Create monitor schedules Release: 8.5.00 5 Registration - Shared source listing registration S System Settings - View system settings for clients U User Settings - View user settings for clients I Environment - Display CA MAT and environmental information Enter an option or press END to return to the CA MAT Primary Option Menu
The Monitor Schedules panel displays.
CA MAT ------------------ Monitor Schedules ------------- Row 1 to 4 of 4 COMMAND ===> SCROLL ===> HALF Primary commands: ADD name Server ID: MATUNER Status: INACTIVE Line commands: S - Edit D - Delete C - Copy LC Schedule Description Modified By: On: At: ________ ________________________________ ________ __________ __________ ------------------------------------------------------------------------------- __ SCHED1 Weekdays after 1800 BMVJJM1 2005/06/27 09:56:47.2 __ SCHED2 Weekends BMVJJM1 2005/06/27 09:58:00.9 __ SCHED3 0600 to 1700 BMVJJM1 2005/06/27 09:58:23.0 __ SCHED4 2005/07/01 BMVJJM1 2005/06/27 10:00:56.9 ********************************* End of Table ********************************
The commands and fields that are available on this panel are described next.
This field is used to specify a new schedule name (1- to 8-characters). The Monitor Scheduling Criteria panel displays, where you can specify the days and times for a monitor to run.
This field is used to edit an already existing schedule.
This field is used to delete the schedule.
This field is used to copy the schedule.
This field displays the 1- to 8-character name of a schedule.
This field displays the up-to 25-character optional description of the schedule (up to 25 characters).
This field displays the user ID of the last user who edited or created the schedule
This field displays the date the schedule was created or last edited.
This field displays the time the schedule was created or last edited
The Monitoring Scheduling Criteria panel displays.
CA MAT ---------------- Monitoring Scheduling Criteria ----------------------- COMMAND ===> Schedule: SCHDA01 Description ===> Monday Date range: Valid dates Starting ===> &MONDAY Ending ===> &MONDAY (YYYY/MM/DD) Monitor request valid for ===> (days) Day of week settings: Day of week Weekdays / Monday Thursday Sunday selection criteria Weekends or Tuesday Friday / Specific days . . Wednesday Saturday Generic time ranges: Monitor valid 1 ===> ===> (hhmm 24 hour clock) during time 2 ===> ===> ranges of 3 ===> ===> 4 ===> ===> Enter END to save parameters or CANCEL to exit without change. Trilog AG., Confidential and Proprietary Information
The commands and fields that are available on this panel are described next.
Indicates the name of the schedule.
Enter a starting date in YYYY/MM/DD format for the monitor schedule to begin.
Enter an ending date in YYYY/MM/DD format for the monitor schedule to end. CA Mainframe Application Tuner will not start a monitor session on or after this date.
You can also use the following variables instead of dates in the Starting and Ending fields:
CA Mainframe Application Tuner calculates these variables into the correct dates for you.
When using a variable for the starting date, the current day is always used as the starting date, or the next occurrence of that day. For example, if the current day is Wednesday and you specify &WEDNESDAY as the variable, the schedule starts that day. However, if the current day is Wednesday and you specify &MONDAY as the variable, the schedule starts the following Monday.
Specify from 1 to 9999 days duration for the monitor. This field is used in conjunction with the Starting field only. When you use this field, do not use the Ending field.
Specify a slash (/) if you want the schedule to run on weekdays during the period.
Specify a slash (/) if you want the schedule to run on weekends during the period.
When creating the schedule, place a slash (/) next to Weekdays or Weekends or, select specific days by placing a slash next to Specific days and also placing a slash next to names of the days.
Specify a slash (/) if you want the schedule to run on certain days during the period. You must select each day with a slash.
Specify a slash (/) next to each day that you want the monitor to run.
Specify in HHMM format (up to four times) during which you want the monitor to run. If no range is specified, the monitor is valid for the entire 24 hour day.
The table in the section Create a Monitor Schedule shows an example of a completed Monitoring Scheduling Criteria panel.
CA MAT ---------------- Monitoring Scheduling Criteria ----------------------- COMMAND ===> Schedule: SCHONE Description ===> Date range: Valid dates Starting ===> 2007/06/16 Ending ===> (YYYY/MM/DD) Monitor request valid for ===> 20 (days) Day of week settings: Day of week Weekdays Monday Thursday Sunday selection criteria Weekends or Tuesday / Friday / Specific days . . Wednesday / Saturday Generic time ranges: Monitor valid 1 ===> 1200 ===> 1300 (hhmm 24 hour clock) during time 2 ===> ===> ranges of 3 ===> ===> 4 ===> ===>
When you invoke a monitor with a schedule, the monitor remains invoked until the end of the schedule. However, the monitor only starts if the target job is executed during the specified time range of the schedule. After the end of the schedule is reached, the monitor is stopped automatically.
To exit this panel without specifying a schedule, press Cancel. Pressing End associates a schedule with the monitor request.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |