Using E2E Automation

The following topics describe how to use E2E automation.

Defining DMN and REF objects
Before starting the E2E agent, you should have defined the REF and DMN objects via the system automation customization dialog. For detailed description, see manual IBM Z System Automation Defining Automation Policy.
Defining cross-domain relationships
You can define relationships between a resource reference and other local resources of type APL, APG, MTR, or REF. The supported relationships include MAKEAVAILABLE, MAKEUNAVAILABLE, HASPARENT, HASPASSIVEPARENT, or FORCEDOWN.
Loading the E2E Automation configuration
After you define the DMN and REF objects and all relationships via the customization dialog, all data needed to perform end-to-end automation is stored into the normal system automation configuration file that you finally build via the customization dialog as usual.
Activating E2E Automation
Showing that E2E Automation is activated
You can find out that E2E automation is active by INGAMS command.
Status of an automation domain
End-to-end automation can be connected or disconnected to an automation domain. You connect an automation domain to end-to-end automation when you start the corresponding E2E automation adapter on the remote domain and the E2E agent is able to establish a TCP/IP connection to this E2E automation adapter.
Status of a resource reference
The status of the resource reference represents the status of the remote resource. If a remote resource is AVAILABLE or SOFTDOWN, the resource reference should also be AVAILABLE or SOFTDOWN.
Operational information
The operational information is not a status. It consists of a synonym and a self-explaining text. It is just an extra explanation for the current setting of observed and automation status. If the resource reference is not in the expected status, the operational information helps to understand the situation that leads to this status.
Commands supporting REF and DMN
The following system automation commands support REF and DMN objects.
Conflicting Goals of Different SA z/OS Automation Domains
This topic is specific to SA z/OS domains (SAplexes), but not to the domains managed by the Universal Automation Adapters. It describes why the status of a resource reference (REF) can differ from the status of its remote resource, and how service update of OA59243 can resolve this conflict.
User Credentials of the End-to-End Automation Manager
When the end-to-end automation manager issues requests against remote resources, it must authenticate itself to the first-level automation domains that host the remote resources. For authentication, the end-to-end automation manager uses the user credentials (user ID and password) that are specified in the credential file of the E2E agent.

Parent topic: Concepts of End-to-End Automation