If OAM has been previously installed, you must carefully analyze the following steps for your particular installation. You will be given additional migration guidance for each step indicating that you need only review the step to ensure that you have completed it in your previous installation, or that you should perform the step regardless of whether you completed it in your previous installation, or that you should not perform the step. Remember, however, that each installation is unique, and you must carefully study these materials to ensure that you are taking the appropriate action for your installation environment.

1. 1 Changing DB2 installation parameters
2. 2 Changing CICS installation parameters
   Note: Perform these steps only if CICS is installed on your system.
   1. Update or create CICS PLT
   2. Update CICS CSD
   3. Update CICS SIT
   4. Connect DB2 to CICS
   5. Copy CBRICONN to DFHRPL
3. 3 Configure the z/OS Unix file system
   Notes:

   • For a new installation, configure the file system. If you are migrating to a new release, you can reuse your existing file system.
   • Perform this step only if you are using the file system for object support.
4. 4 Modifying the installation exit to manage deleted objects
   Notes:

   • For a new installation, evaluate and implement the auto-delete installation exit. If you are migrating to a new release, you can reuse your existing auto-delete installation exit.
   • Perform this step only if you are running OSMC for expiration processing.
5. 5 Changing system libraries
   1. Update IGDSMSxx PARMLIB member
      Note: Do not perform this step if you are using only DB2 sublevel storage (no file system, optical volumes, or tape devices) and you are not running OSMC for expiration processing.
   2. Updating the IEFSSNxx PARMLIB member
   3. Update SMFPRMxx PARMLIB member
   4. Update PROGxx PARMLIB member
   5. Update CONSOLxx PARMLIB member.
   6. Add the OAM object tape return to the MVS scratch volume exit routines to the PROGxx member
   7. Create or Update CBROAMxx PARMLIB members.
      Note: Perform this step only if you intend to start the OAM address space for object support. You need to start OAM in order to:

      • store objects in the file system or on tape or optical devices
      • delete objects from the file system and enable the file system delete task to delete objects from the FSDELETE table in DB2
      • use OSMC
      • join an OAMplex.
   8. 5h Updating the PROCLIB
      1. Modify, if necessary, then run CBRIPROC SAMPLIB job.
      2. Modify, if necessary, then run CBRAPROC SAMPLIB job.
         Note: Perform this step only if you start the OAM address space.
      3. Verify or create device numbers.
         Note: Perform this step only if you are using optical devices.
6. 6 Creating DB2 databases for object tables and directories
   1. Add additional steps to the database creation jobs, if necessary:

      (CBRIALC0 and CBRISQL0)

   2. Modify the OAM data set allocation jobs:
      (CBRIALC0, CBRIALCX, CBRIALCY)

      Note: If DB2 data sets are being placed in an SMS storage group, you must properly prepare the environment (that is, create ACS routines and the source control data set, and so on).
   3. Run the OAM data set allocation jobs:

      (CBRIALC0, CBRIALCX, CBRIALCY)

   4. Modify the OAM database definition jobs:

      (CBRISQL0, CBRISQLX, CBRISQLY)

   5. Run the OAM database definition jobs:

      (CBRISQL0, CBRISQLX, CBRISQLY)

      Note:

      Remember to modify the SAMPLIB jobs for your installation JOB card requirements and DB2 subsystem name and to start DB2 before running the SAMPLIB jobs.

   6. Modify OAM LOB data set allocation and definition job. (CBRILOB)
      Note: Perform this step ONLY if you intend to enable LOB support.
   7. Run the OAM LOB data set allocation and definition job. (CBRILOB)
      Note: Perform this step ONLY if you intend to enable LOB support.
7. 7 Creating the OAM configuration database
   1. Modify, if necessary, then run the CBRSAMPL SAMPLIB job (for first-time OAM installations).
      Note: Do not perform this step if you are using only DB2 sublevel storage (no file system, optical volumes, or tape devices) and you are not running OSMC for expiration processing. If you choose not to execute this step, then you need to modify the CBRPBIND job in SAMPLIB to validate the bind at run time (VALIDATE RUN) rather than validating the bind at bind time (VALIDATE BIND).
   2. Run the CBRSMR1B SAMPLIB job if you are migrating from any release earlier than z/OS V1R11.
      Notes:

      • Regardless of whether you intend to exploit the new function, you must modify and run this job.
      • This job adds new ODSTATF, ODRETDT and ODINSTID columns to the OAM Object Directory tables in DB2.
      • Do not perform this step at initial installation. Perform this step for migration purposes only.
   3. Run the CBRSMR1D SAMPLIB job if you are migrating from any release earlier than z/OS V1R13.
      Notes:

      • Regardless of whether you intend to exploit the new function, you must modify and run this job.
      • This job adds the File System Delete Table to the OAM Configuration Database.
      • Do not perform this step at initial installation. Perform this step for migration purposes only.
   4. Run the CBRSMKBO SAMPLIB job if your TAPEVOL table does not contain a CAPACITYO (capacity overflow) column.
      Notes:

      • Regardless of whether you intend to exploit the new function, you must modify and run this job.
      • This job adds the CAPACITYO, FRESPACEO, NUMLKBWO, NUMPKBWO, and NUMLKBDEO overflow columns to the TAPEVOL table.
      • Do not perform this step at initial installation. Perform this step for migration purposes only.
   5. Run the CBRSMVAF SAMPLIB job if your TAPEVOL table does not contain a VOLATTRF (volume attribute flags) column.
      Notes:

      • Regardless of whether you intend to exploit the new function, you must modify and run this job.
      • This job adds the VOLATTRF column to the TAPEVOL table.
      • Do not perform this step at initial installation. Perform this step for migration purposes only.
8. 8 Merging object tables and OCDB for an OAMplex
   1. Run the CBRSMERG SAMPLIB job.
      Note: Do not perform this step at initial installation. Modify and run this step for migration purposes. This job should only be run if you plan to merge multiple OAM configuration databases (OCDB) into a single shared OCDB for an OAMplex.
   2. Run the CBRSG100 SAMPLIB job.
      Note: Do not perform this step at initial installation. Perform this step only when all of the following conditions exist: you are setting up an OAMplex; you currently have multiple OAMs running on separate MVS images in a sysplex; and you want to merge two or more separate OAMADMIN tables, object storage databases, or both.
9. 9 Creating and binding DB2 packages
   1. Run the CBRPBIND SAMPLIB job.
      Note: For systems that are sharing DB2 within an OAMplex, the CBRPBIND job only needs to be run on one system in the OAMplex and, if you have mixed z/OS versions on your OAMplex, it should be run on the system that is running on the highest level of z/OS.
10. 10 OSR application plans
    1. Run the CBRIBIND SAMPLIB job.
    2. Run the CBRIGRNT SAMPLIB job.
    Note: Perform this step only if you are using only DB2 sublevel storage (no file system, optical volumes, or tape devices), and are not using OSMC for object expiration. If using a file system, optical devices, tape devices, or OSMC, then you need to perform 12 LCS, ISMF, and OSR application plans instead.
11. 11 OSMC application plans
    1. Run the CBRHBIND SAMPLIB job.
    2. Run the CBRHGRNT SAMPLIB job.
       Note: Do not perform this step if you are using only DB2 sublevel storage (no file system, optical volumes, or tape devices) and you are not running OSMC for expiration processing.
12. 12 LCS, ISMF, and OSR application plans
    1. Run the CBRABIND SAMPLIB job.
       Note: Do not perform this step if you are using only DB2 sublevel storage (no file system, optical volumes, or tape devices) and you are not running OSMC for expiration processing.
    2. Run the CBRAGRNT SAMPLIB job.
       Note: Do not perform this step if you are using only DB2 sublevel storage (no file system, optical volumes, or tape devices) and you are not running OSMC for expiration processing.
13. 13 Verifying DB2 installation
    1. Verify that all application BINDS have been run.
    2. Verify that all application plans have been authorized.
    3. Verify that all application plans have been created.
14. 14 Defining user catalogs
    1. Evaluate and implement user catalogs and policies.
15. 15 IPL the system
16. 16 Specifying the SMS definitions and programs used by OAM
    1. Define the base SCDS.
    2. Define libraries and drives in the OAM configuration database.
       Note: You must perform this step at initial installation. During migration, you might optionally perform this step if you are adding or changing libraries or drives. This step is required only if you are using optical devices.
    3. Define Object and Object Backup storage groups.
    4. Define storage classes.
    5. Define data classes.
    6. Define management classes.
    7. Define and test ACS routines.
    8. Validate and activate the SMS configuration.
17. 17 Run the OAM Installation Verification Program for object support, if you are storing objects.
18. 18 Adding new tape devices to the OAM object tape configuration