Implementation considerations for ARM

To implement ARM support for MainView AutoOPERATOR, you must modify the ARMPOLCY parameter in BBPARM member BBISSP00 (see Enabling ARM support). The following choices are available:

  • Do not implement ARM support.

  • Implement ARM support with the default ARM policy.

  • Implement ARM support with your own user-designed policy.

Default ARM policy

The default ARM restart policy is that ARM attempts to restart an abended Started Task up to three times in a five-minute interval. After three attempts and the Started Task has still failed to restart, ARM stops attempting restarts and a message is written to SYSLOG.

Therefore, if you choose to use the default ARM policy for MainView AutoOPERATOR, ARM will attempt to restart an abended MainView AutoOPERATOR subsystem up to three times in a five-minute interval.

The default ARM policy uses the same start command that was used to start the MainView AutoOPERATOR subsystem originally. After the third attempt, if MainView AutoOPERATOR has not successfully restarted, a message is written to SYSLOG and restart attempts stop.

If you decide that ARM should perform more restarts or perform them over a different period of time, you can write your own ARM restart policy. For more information, see User-defined ARM policy below. 

User-defined ARM policy

You might already have an ARM restart policy in place or you can create your own ARM restart policy.

To create your own policy, refer to the IBM publication Setting Up a Sysplex.In either case, MainView AutoOPERATOR provides support for a user-defined ARM restart policy. Enabling ARM support describes how to enter the name of a user-defined ARM restart policy in BBPARM member BBISSP00.

Note

Only one ARM policy can operate in an z/OS image at one time.




This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments