Installing from Pax Files Using the SAMPJCL Method › Deploy Products › Deploying Agent Technology on Multiple Systems › Copy Your Agent Technology Installation

Previous Topic: Deploying Agent Technology on Multiple Systems

Next Topic: Deploying Event Management on Multiple Systems

Copy Your Agent Technology Installation

Use the following procedure to copy your Agent Technology services installation onto a second z/OS image. This procedure assumes that Agent Technology services have been successfully installed and tested on at least one z/OS image.

To copy your Agent Technology installation

  1. Confirm that the target system meets the minimal system requirements for z/OS Agent Technology.
  2. Backup your existing Agent Technology zFSs on the source LPAR. This backup should be taken when the Agent Technology services are down, after the aws_sadmin Store has been properly initialized and the Agent MIBs have been loaded. The zFS files are VSAM linear data sets. Use IDCAMS REPRO to back up the data sets.
  3. Make the Agent Technology CNSMLOAD, CNSMJCL, CNSMOPTV, and MIBLIB partitioned data sets accessible on the target system, either through shared DASD or by copying the files.
  4. Tailor and submit CNSMJCL(B6DI0015) on the target system to define the user ID AWADMIN and group AWGROUP to the security system, if required.
  5. Tailor and submit SAMPJCL( B6D1ALLU) to allocate and format only the Read-Write zFS on the target system. Be sure to remove the steps that allocate and format the Read-Only zFS (jobsteps DEFINRO and FMTRO).
  6. Restore the backup file of the Read-Write zFS from Step 2 into the newly allocated Read-Write zFS on the target LPAR
  7. Tailor and submit SAMPJCL( B6D2MKD) to create the mount points for the zFS files and mount the RW zFS just created and formatted. Remove the step that mounts the RO zFS.
  8. Make the Read-Only zFS, which was created by the initial installation, available to the target system in read-only mode.
  9. Update your BPXPRMxx member on the target system to add the MOUNT directories for the new zFSs.
  10. Perform the following configuration tasks on the target LPAR:
    1. Modify your agentworks.profile script in the root Agent Technology directory to reflect the new environment.

      Pay particular attention to the environment variables:

      • AWORKS_MVS_PREFIX designates the prefix for your Agent Technology z/OS files.
      • AGENTWORKS_DIR designates the Agent Technology home directory.
      • RESOLVER_CONFIG designates the DSN for the TCPIP.DATA file. This reference must correlate to the DSN specified by the SYSTCPD DD statement for the TCP stack running on the new system. A member name must be included if the data set is a PDS.
    2. Modify member ENVFILE in yourCNSMOPTV. If you share your CNSMOPTV between multiple z/OS images, you may need to create a new unique member for the new system. This is the case only if you need to modify the contents on the ENVFILE member for the new LPAR. When modifying or creating this file, pay particular attention to AGENTWORKS_DIR, which designates the Agent Technology root directory.
    3. Modify all scripts, configuration files, and JCL members as necessary for the target LPAR.
      • Scripts--Aside from the changes to the agentworks.profile script mentioned previously, you may also need to modify your install_mibs script located in the $AGENTWORKS_DIR/services/tools directory to include or exclude agents that either will or will not be running on the target system.
      • Configuration Files--The file most likely to require change is the aws_sadmin.cfg file. This file, located in the /cai/agent/services/config/aws_sadmin directory, contains the trap destinations where traps will be sent, as well as SNMP community strings.
      • JCL--If JCL changes are required, such as to reference a different ENVFILE, you should create a unique copy of the JCL for the new system.
    4. The process of copying and restoring the Read-Write zFS to a new system image also copies the aws_sadmin Store files. This is not appropriate for your target systems unless you are running the same releases of agents across all your systems. If you are running different releases, you need to run the procedures found in the previous section titled Build the aws_sadmin Store files.
    5. Within UNIX System Services, after the agentworks.profile script has been invoked, run the awftest tcpip utility. This utility verifies that the TCPIP stack has been properly configured. Do not attempt to start your Agent Technology services until this utility runs without error.
  11. Start your Agent Technology services on the target LPAR.