|
|
|
|
|
There are several ARM policy parameters you can choose to determine where, under what circumstances, and how many times, IOAGATE is to be restarted. Some of these restart parameters are described in the following table.
Table 170 Restart parameters
Parameter |
Description |
|---|---|
TARGET_SYSTEM |
Systems on which IOAGATE can be restarted in a cross-system restart. |
ELEMENT |
Element name that represents IOAGATE. This must exactly match the ARMELEM ECAPARM parameter. |
RESTART_ATTEMPTS |
Maximum number of times that the operating system should attempt to restart IOAGATE. This limit prevents the operating system from continually restarting an element that is recursively terminating. |
TERMTYPE |
Specifies under which condition the operating system should restart IOAGATE. Valid values are:
|
RESTART_METHOD |
Specifies the command text that the operating system is to use to restart the element. RESTART_METHOD. (BOTH,PERSIST) indicates that the operating system is to use the command text that previously started IOAGATE. |
To obtain information about elements of the automatic restart manager while the system is active, you can issue the D XCF,ARMSTATUS,DETAIL MVS operator command. For more information about this command, see the discussion about displaying cross system coupling facility (XCF) information, in the IBM publication MVS System Commands.
Parent Topic |