Controlling the Secondary Automation Manager
Functions
If you enter command code A for a secondaryautomation manager, a panel is displayed where you can specify
the new mode of operation, as shown in Figure 1. Switching into
primary mode is considered a directed takeover.
Figure 1. INGAMS Command Dialog Panel to Control Secondary Automation Manager Functions
INGKYAM1 SA z/OS - Command Dialogs
Domain ID = IPUND ---------- INGAMS ---------- Date = 07/17/19
Operator ID = NETOP1 Sysplex = AOCAPLEX Time = 09:10:27
Specify or revise the following data:
Action => 1. Make primary Automation manager - Start =>
2. Enable Takeover File
3. Disable Takeover File
4. Suspend System
5. Resume System Automation manager => AOCA$$$$2
Target => AOCAPLEX System name, domain id or sysplex name
Command ===>
PF1=Help PF2=End PF3=Return PF6=Roll
PF12=Retrieve
Use this panel to initiate the following functions:
Make primary Automation manager
This allows you to change the operation mode of a
secondary automation manager to become primary (PAM). This is considered a
directed takeover. Optionally, you can specify the start mode for
the new PAM. Valid start modes are HOT, WARM or COLD. The default
is HOT.
Note: A primary automation manager cannot be changed to a
SAM.
Enable Takeover file
This causes the automation manager to start updating the Takeover file
for each work item that is processed. This is necessary after the
Takeover file has been enlarged or another error condition resolved.
Disable Takeover file
This causes the automation manager to stop writing to the Takeover file.
The Takeover file is freed from the automation manager.
Suspend System
This causes the automation manager to stop sending orders to the agent
running on the system specified left of the action. You can specify
more than one system name separated by a blank character. Specify *all to
suspend all systems that are controlled by the automation manager.
Resume System
This causes the automation manager to resume sending orders to the agent
running on the system specified left of the action. You can specify
more than one system name separated by a blank character. Specify *all to
resume all systems that are controlled by the automation manager.
Fill in the following fields:
Automation manager
Specify the name of the automation manager.
Target
The name of the system where the automation manager resides. This is
only necessary when the automation manager is not within the local sysplex.
You can specify either the system name, the domain ID or the sysplex
name.