Setting the Status or Attribute of a Resource or Application Group
INGKYST1 SA z/OS - Command Dialogs
Domain ID = IPUFP ---------- INGLIST ---------- Date = 04/08/05
Operator ID = NETOP1 Sysplex = KEY1PLEX Time = 17:25:08
Resource . . : AM/APL/KEY4
Description. : Primary Automation Manager
Action to be performed ==> current setting
1. Set START Type
Parm
2. Set STOP Type
Parm
3. Set Automation Flag NO YES
4. Set Hold Flag YES NO
5. Set Group failed flag (Yes or No)
6. Set Observed Status AVAILABLE
7. Set Automation Status IDLE
8. Set Agent Status UP
Command ===>
PF1=Help PF2=End PF3=Return PF6=Roll
PF12=Retrieve
- Set the start or stop type to be used the next time
- Turn the automation manager's Global Automation flag on or off
The automation manager checks the Global Automation flag before it sends any order to the automation agent to start or stop the specific resource. The purpose of this flag is to prevent (if flag is set to NO) or enable (if flag is set to YES) the starting or stopping of resources from the point of view of the automation manager. This can be done for resources that reside on systems that are currently inactive, for example, to prevent the startup of the resource at IPL time of the system.
- Turn the automation manager's Hold flag on or off
The Hold flag specifies whether the resource is to be started. The Hold flag can be set only if the resource is down, that is if its observed status is either HardDown, SoftDown, SysGone, or Unknown. When the Hold flag is set to YES, the specific resource is set in compound status of DENIED unless there is a start request or a vote against it.
For instance, when an APL with default desired status of AVAILABLE is a member of a BASIC group and it has no other vote against it, this APL will be in status DENIED. When an operator issues a start request for it, the APL is started.
- Turn the Group Failed flag on or off
The Group Failed flag is set when any member of the group (BASIC, MOVE, or SERVER) enters a HardDown state (CTLDOWN, BROKEN, or STOPPED). The flag is not cleared automatically by a subsequent successful start or restart of the APG's members. It remains set until manually cleared. Its sole purpose is to support the MakeAvailable/passive/WhenGroupHasNotFailed relationship. The usage is for situations where the start or restart of a dependent resource must be prevented until a certain recovery-related action is performed.
- Update the observed status
- Update the automation status
- Update the agent status
- Action
- This identifies what to update. This is a one-digit numeric character ranging from 1 to 8. Depending on the specified action, fill out the appropriate field.
- START type
- Specify the new start type if action 1 is entered. Specify a question mark (?) to see a list of defined startup types. To reset the start type to its default, specify NORM.
- STOP type
- Specify the new stop type if action 2 is entered. Valid shutdown types are NORM, IMMED, and FORCE. To reset the stop type to its default, specify NORM.
- Group failed flag
- Specify YES or NO if action 5 is entered.
- Observed Status
- Specify the new observed status if action 6 is entered. You can abbreviate the observed status, for example, you can enter AV for available. Here is a list of possible observed status values and their shortest possible abbreviations: AVAILABLE (A), UNKNOWN (U), SYSGONE (SY), SOFTDOWN (SO), HARDDOWN (H), STARTING (STAR), DEGRADED (D), STOPPING (STO), PROBLEM (P), WASAVAILABLE (W), and STANDBY (STAN).
- Automation Status
- Specify the new automation status if action 7 is entered. You can abbreviate the automation status. Here is a list of possible Automation Status values and their shortest possible abbreviations: UNKNOWN (U), IDLE (ID), ORDERED (O), BUSY (B), DENIED (D), PROBLEM (P), and INTERNAL (IN).
- Agent status
- Specify the automation agent status if action 8 is entered. The agent status can be one of the following: CTLDOWN, RESTART, UP, MOVED, AUTODOWN, or ENDED.
- The resource is down, that is, its observed status is either HardDown, SoftDown, SysGone, or Unknown.
- The automation manager is not in the process of starting the resource.
If the resource has a start vote that is propagated from a SERVER group, the resource is started even when the Hold flag is set to YES.