Migrating, installing, and customizing OAM

This topic explains how to install OAM, customize it for your business and processing environments, and verify that the installation is complete and correct. First, decide on your installation scenario: Are you installing OAM for the first time, migrating to a new release of OAM, merging separate OAM systems into an OAMplex, moving an OAM system to another system, or adding OAM systems to an OAMplex? Use the following roadmap to guide you to the correct procedure for your installation scenario.

Subtask	Associated procedure (see . . . )
Verifying hardware and software prerequisites.	Verifying hardware and software prerequisites
Preparing the processing environment.	Preparing the processing environment
Installing OAM for the first time.	Table 1 High-level installation and migration checklists
Migrating to a new version of OAM.	Table 1 High-level installation and migration checklists
Moving OAM to another system.	Procedures for moving OAM to another system
Merging OAMs into an OAMplex.	Merging OAMs into an OAMplex
Adding OAM systems to an OAMplex.	Adding OAM systems to an existing OAMplex

In addition to these basic installation requirements, this topic also describes an optional auto-delete installation exit that you can use to further customize your installation.

To simplify the installation process, a library of sample jobs and other useful data sets (SAMPLIB) is shipped with the product. This topic includes instructions for using SAMPLIB; Sample library members contains listings of many of the SAMPLIB members. Before running any SAMPLIB job, remember to change the JCL to reflect your installation’s requirements (for example, accounting information and data set names).

Related reading: See z/OS MVS JCL Reference for additional information.

Note: Unless otherwise indicated, once you migrate to the current release, you do not need to do anything to migrate backward to the previous release level other than to run the BIND jobs.