Takeover File

The takeover file is dynamically allocated during the initialization of the primary automation manager (PAM). The name of the takeover file is defined in the HSAPRMxx parmlib member. The name of the takeover file cannot be changed when an automation manager (PAM or SAM) is running. All automation managers (in the same XCF group) must use the same takeover file name.

The takeover file is allocated using the DD name HSATKOVR. Note that an automation manager started as a SAM does not allocate the takeover file.

If an allocation error or a VSAM open/read error occurs during a hot start or takeover processing, the operator is prompted to decide whether to continue with a Warm start and lose all the information that is stored in the takeover file or to retry reading the takeover file. If the operator continues with a Warm start and this fails too, the automation manager terminates, which causes another takeover.

If an error occurs while writing to the takeover file, the automation manager continues to run using the in-storage version of the resources' objects but disables updating of the takeover file. The in-storage state information of the resources is not written to the takeover file when the automation manager terminates. You thus lose the ability to continue with a hot start when switching the primary automation manager.

The automation manager allows you to repair the takeover file while the PAM and the SAMs are running. To do this:

  1. Disable the takeover file if this has not already been done by the PAM.
  2. Repair the file, for example, by enlarging it.
  3. Enable the takeover file again.