Implementing a Local System Image of the Managed Resources › 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.

When checkpoint restart is active, any override placed on a resource is stored in the resource definition as checkpoint data. This checkpoint data is applied automatically to the resource when you load the system image with a Warm Start, restoring previously placed overrides.

When checkpoint restart is inactive, any override placed on a resource is not stored as checkpoint data; however, previously stored data is retained. With checkpoint restart inactive, a Warm Start does not apply any stored checkpoint data.

Note: Setting checkpoint restart inactive does not clear the stored checkpoint data. If you later set checkpoint restart to active, then a Warm Start applies the previously stored checkpoint data.

If you no longer want to restore previously placed overrides, load the system image with a Cold Start. All checkpoint data is cleared from the resource definitions, and the resources are loaded without overrides.

Cold Start also clears checkpoint data from the following resources:

• Resources in shared system images (both active and inactive) that satisfy the following conditions:
  • The resource has the local system as the home system.
  • The resource is not active on another system.
• Resources in z/VM system images where the z/VM system image has the local system as the home system

Note: The local system is where the system image is being loaded.