Specifying Restart Parameters

Restart parameters can be specified when registering the element through the IXCARM macro, in the element restart exit, or in the ARM policy. The hierarchy for parameters used during a restart is:

The element restart exit overrides the installation-written policy.
Installation-written policy parameters override parameters specified on the IXCARM macro.
Parameters specified on the IXCARM macro override policy defaults.

Note: If the element restart exit or active policy alter the original method of start, the security environment the job was originally started under will not be changed.

Significant restart parameters are:

How an element should be restarted.
For started tasks, specify restart text to provide text that differs from the original START command text (referred to as persistent command text). For abstract resources, specify restart text to restart the abstract resource. If restart text is not supplied for abstract resources on registration, or in the automatic restart management policy, or by an installation-written element restart exit, no restart will be performed. For elements that represent jobs, use the RESTART_METHOD statement in the automatic restart management policy to provide restart text that differs from the original JCL (referred to as persistent restart text) used to submit the job.

Start text (STARTTXT keyword on IXCARM) is overridden by RESTART_METHOD in the active ARM policy.
The circumstances (element or system termination) under which the element is to be restarted.
The type of termination (TERMTYPE keyword on IXCARM) is overridden by TERMTYPE in the active ARM policy.

Note that for an element that represents an abstract resource, the element can only be restarted for a system failure, regardless of the TERMTYPE specification in the active ARM policy. Therefore, if the installation does not want the element started for a system failure, specify RESTART_ATTEMPTS(0) in the ARM policy.
How long it will take the element to re-register.
To ensure that the restart of a given element completed successfully, automatic restart management uses a time limit between the restart of an element and its re-registration. This limit is called the restart timeout threshold. If an element could take a long time to restart, code this parameter to keep the program from being de-registered.

The restart timeout threshold (RESTARTTIMEOUT keyword on IXCARM) is overridden by RESTART_TIMEOUT in the active ARM policy.