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 HSISCUST member in the hsi.SHSISAMP data set with the following parameters:
    • DBTYPE=DB2
    • REPZSCHM=REPHLQ1
    • GKBZSCHM=GKBHLQ1
    • NOTFSCHM=NOTHLQ1
    • DB=REPDB1
    • DBGKB=GKBDB1
    • DBNOT=NOTDB1
  2. Submit the HSISCUST job.
  3. Create the Repository and GKB databases and grant access to them:
    1. Run the HSISDB01 job to create storage groups.
    2. Run the HSISDB02 job to create the GKB database and database objects.
    3. Run the HSISDB03 job to create the Repository database and database objects.
    4. Run the HSISDB04 job to create the Notifications database and database objects.
    5. Run the HSISGKBL job to load GKB data.
    6. Run the HSISGRNT job to grant DBADMIN access to IBM Z Software Asset Management administrator.
    7. Optional - Run the HSISGRTB 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 HSISINQZ job on all four z/OS® LPARs to collect Inquisitor data: MVSA, MVSB, MVSC, and MVSD. The default setting is PLX=N.
    2. Transfer the collected Inquisitor data to the central site via file transfer protocol (FTP).
    3. Run the HSISIQIM 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 HSISINQZ job.
    2. Run the HSISINQZ job on any z/OS® LPAR to collect Inquisitor data. The z/OS® LPAR could be MVSA, MVSB, MVSC, or MVSD.
    3. Transfer the collected Inquisitor data to the central site via FTP.
    4. Run the HSISIQIM job to import Inquisitor data into the Repository database for the z/OS® LPAR, where you previously ran HSISINQZ.
    5. Repeat steps a - d for any z/OS® LPAR - MVSA, MVSB, MVSC, or MVSD, every time a new scan is required.
    Note:
    It is very important to understand that setting PLX=Y will work only if all LPARs belonging to a sysplex have DASD volumes that are 100% shared. If one LPAR contains DASD volumes that are unique to that LPAR, then PLX=Y must NOT be used. Instead PLX=N must be set and run separately for all LPARs belonging to the sysplex.
  6. Collect and import Inquisitor data for UNIX for all z/OS® LPARs the first time:
    1. Run the HSISINQU 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 HSISIQIM job to import Inquisitor data for UNIX® into the Repository database for each z/OS® LPAR.
    4. Repeat steps a - c for every z/OS® LPAR every time a new scan is required.
  7. Collect and import Usage Monitor data:
    1. Run the HSISUMON 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 HSISUIMP job to import Usage data into the Repository database for each LPAR.