Scenario 5: Implementing in a sysplex environment

This deployment scenario is for a sysplex environment, where the DASD is fully shared across all z/OS® LPARs that belong to the sysplex. This special deployment is similar to the deployment scenarios 1, 2, or 3, but the implementation steps are slightly different. This approach is intended to achieve operational efficiency by processing only a single z/OS® LPAR within a sysplex.

About this task

The example deployment is for a Db2® database environment and includes the key parameters that influence this scenario. For this scenario, assume that the sysplex contains four z/OS® LPARs: MVSA, MVSB, MVSC, and MVSD.

Procedure

  1. Customize an instance of the HZASCUST member in the hza.SHZASAMP data set with the following parameters:
    • DBTYPE=DB2
    • REPZSCHM=REPHLQ1
    • GKBZSCHM=GKBHLQ1
    • DB=REPDB1
    • DBGKB=GKBDB1
  2. Submit the HZASCUST job.
  3. Create the Repository and GKB databases and grant access to them:
    1. Run the HZASDB01 job to create storage groups.
    2. Run the HZASDB02 job to create the GKB database and database objects.
    3. Run the HZASDB03 job to create the Repository database and database objects.
    4. Run the HZASGKBL job to load GKB data.
    5. Run the HZASGRNT job to grant DBADMIN access to Z Asset Optimizer administrator.
    6. Run the HZASGRTB job to grant SELECT access to database tables.
  4. Collect and import Inquisitor data for all z/OS® LPARs the first time:
    1. Run the HZASINQZ job on all four z/OS® LPARs to collect Inquisitor data: MVSA, MVSB, MVSC, and MVSD.
    2. Transfer the collected Inquisitor data to the central site via file transfer protocol (FTP).
    3. Run the HZASIQIM job to import Inquisitor data into the Repository database for each z/OS® LPAR.
  5. Collect and import Inquisitor data only for a single z/OS® LPAR in subsequent scans:
    1. Set PLX=Y in the Inquisitor HZASINQZ job.
    2. Run the HZASINQZ job on the first z/OS® LPAR, MVSA, to collect Inquisitor data.
    3. Transfer the collected Inquisitor data to the central site via FTP.
    4. Run the HZASIQIM job to import Inquisitor data into the Repository database for the z/OS® LPAR MVSA only.
    5. Repeat steps a - d for z/OS® LPAR MVSA every time a new scan is required.
  6. Collect and import Inquisitor data for UNIX for all z/OS® LPARs the first time:
    1. Run the HZASINQU job on all four z/OS® LPARs to collect Inquisitor data for UNIX®.
    2. Transfer the collected Inquisitor data for UNIX® to the central site via FTP.
    3. Run the HZASIQIM job to import Inquisitor data for UNIX® into the Repository database for each z/OS® LPAR.
  7. Collect and import Inquisitor data for UNIX only for a single z/OS® LPAR in subsequent scans:
    1. Set PLX=Y in the Inquisitor HZASINQU job.
    2. Run the HZASINQU job on the first z/OS® LPAR, MVSA, to collect Inquisitor data for UNIX.
    3. Transfer the collected Inquisitor data to the central site via FTP.
    4. Run the HZASIQIM job to import Inquisitor data for UNIX into the Repository database for the z/OS® LPAR MVSA only.
    5. Repeat steps a - d for z/OS® LPAR MVSA every time a new scan is required.
  8. Collect and import Usage Monitor data:
    1. Run the HZASUMON job on all z/OS® LPARs to collect usage data.
    2. Transfer the collected Usage Monitor data to the central site via FTP.
    3. Run the HZASUIMP job to import Usage data into the Repository database for each LPAR.