|
|
|
The desired state information specified in a service or a resource definition determines its status. The definition can include an availability map that schedules changes to the default availability. Timers activate these changes.
Note: The default desired state determines the default availability of a service or resource. The state is set in the AUTOIDS parameter group during region initialization. The Customizer : Parameter Groups panel lists the region parameter groups. Enter the /PARMS shortcut to access the panel.
Availability maps enable you to schedule changes to the default availability requirements of one or more services or resources. The service image and each system image have its own set of availability maps. You define an availability map (for example, MAP1) and attach as many services or resources to the map as required. Because availability maps are not limited to a seven-day cycle, you can define changes to the availability requirements that apply daily, on the same day every week, on the same date every month, for a specific date and time, and so on. You can also suppress changes temporarily and update timer information at any time.
An availability map has two parts: a map definition and a timer definition. The map definition contains information about the map itself. The timer definition contains information about when to change the desired state of the services or resources that use this map. The timer definition can also contain information about when to change the operation mode and when to start processes to perform special tasks.
Creating an availability map has the following two stages:
Note: For information about how availability and resource relationships affect operations, see the Reference Guide.
The following rules apply to availability maps:
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |