Automatic restart manager (ARM) registration failure

Failure of the Advisor or Agent to properly register with ARM is indicated by a warning-level message written to the log file. This log message is a result of the IXCARM call failing with the return code and reason codes indicated in the log message. See z/OS MVS Programming: Sysplex Services Reference for information about interpreting the IXCARM return code and reason code.

One of the common causes of failure is the lack of a security profile. See the EZARACF sample for instructions on how to add an ARM security profile for the application.

When you are using sysplex subplexes, do the following:

Define an ARM policy with the TARGET_SYSTEM keyword to indicate which systems the element can be restarted on to ensure that the application is restarted only on a system that is in the same subplex.
Restart the Advisor and Agent on a VTAM® system that has been started with an XCFGRPID start option that corresponds with the vv portion of the sysplex_group_name in the Advisor and Agent configuration files, and has an available TCP/IP stack with a GLOBALCONFIG XCFGRPID parameter that corresponds with the tt portion of the sysplex_group_name in the Advisor and Agent configuration files.
If there are multiple TCP/IP stacks in a subplex, ensure the IP addresses used by the Advisor and Agents are DVIPAs defined within a VIPARANGE statement on each of the stacks in the subplex.