Controlling the System Image › Load a System Image

Load a System Image

You define the operations requirements of the resources to be managed on a system in a system image. You must create a system image definition before you can define the resources you want to manage.

The region loads a system image during region initialization. During operation, you may need to change the system image by loading another image.

Note: When you request to load a system image, the $RMEXSTR exit NCL procedure is executed before the starting process. This procedure may be customized at your site to perform any required tasks before any automated resources are started. The starting process cannot proceed if the exit sets a non-zero return code.

For products that use desired state automation, resources are started according to any relationships defined in the system image, and subject to resource availability.

To load a system image

1. Enter /RADMIN.I at the prompt.

   The ResourceView : System Image List appears.

2. Enter L beside the system image that you want to load.

   The LOAD Command Parameter Specification panel appears.

3. Complete the following fields:
   • SysName to be Loaded

     Enter ? and select a system image from the displayed prompt list.

   • Global Automation Mode

     Specify the global operation mode for your system image.

   • Perform COLD Start?

     If the Checkpoint Restart Status field is set to ACTIVE, you can enter NO in the Perform COLD Start? field to specify a warm load.

4. Press F6 (Action) to load the system image.

   The Command Confirmation panel appears.

5. Enter CONFIRM in the Response field.

   The system image is loaded.

   Important! Resources that are monitored by the region are defined to the system image. Loading a system image affects all users of this region and may influence the resources in the system image.

Checkpoint Restart Function

The checkpoint restart function lets you preserve manual overrides across system restarts.

Manual overrides are retained as follows:

• Checkpoint Restart Active with a Warm Start

  Previously-preserved overrides are applied; new overrides are preserved.

• Checkpoint Restart Active with a Cold Start

  Previously-preserved overrides are deleted; new overrides are preserved.

• Checkpoint Restart Inactive with a Warm Start

  Previously-preserved overrides are not applied; new overrides are not preserved.

• Checkpoint Restart Inactive with a Cold Start

  Previously-preserved overrides are deleted; new overrides are not preserved.