Summary of Changes

This document contains information previously presented in IBM System Automation for z/OS 4.1 End-to-End Automation.

The following section lists important or major changes to this document.

  • Enhancements by OA59243 (Dec 2020)
    • Using the NetView Event/Automation Service (E/AS) as message broker is now optional. If E/AS is not available, an own communication channel between the primary system automation agent and the end-to-end automation adapter will be established that requires no further configuration.
    • To resolve the conflicting goals of different SA z/OS automation domains, a new advanced automation option AOF_E2E_REMOTE_REQ_PROPAGATION is introduced. Set it to YES to activate the propagation of START/STOP requests on a remote resource to the corresponding REF resource. Therefore, the E2E automation manager knows about requests of a local automation manager and thus is enabled to show the correct status of a referenced resource.
    • The E2E automation adapter can optionally provide its IP address instead of its hostname, when joining SMU. You can achieve this behavior by setting the new option eez-remote-contact-hostname-resolve-ip to true. After this setting, the automation adapter will use its IP address to receive synchronous requests from the SMU server.
  • System Automation 4.2 now supports network isolation for E2E Automation components via multiple TCP/IP stacks. See Setup TCP/IP Stack Name in a TCP/IP Multi-Stack Environment.
  • End-to-end automation configuration now supports system symbols in the configuration files. See Support of MVS System Symbols in Configuration Files.
  • The SSL configuration file can now be customized using an alternative way, that is, creating certificates residing in RACF. See Setting Up E2E Automation RACF Keyrings.
  • The eez-functional-authentication parameter is added into the automation adapter master configuration file. This parameter can switch on or off E2E adapter RACF checking for requests sent from the SMU functional user ID.
  • The E2E adapter and agent are enhanced to support TLS version 1.2. E2E_SSL_VERSION is added into the configuration file ingadapter.properties. INGAGT_SSL_VERSION is added into the configuration file inge2eagt.properties.
  • You can add user-specific Java system properties by specifying the new E2E_USRJP parameter in the automation adapter environment configuration file and the new INGAGT_USRJP parameter in the automation agent environment configuration file.
  • You can add user-specific classpath by specifying the new E2E_USRCP parameter in the automation adapter environment configuration file and the new INGAGT_USRCP parameter in the automation agent environment configuration file.
  • Two new USS problems are documented: problems with wrong USS code pages and problems with missing program-controlled settings. See USS problems.