Installation checklist

  1. SMP/E install the z/OS® DLA datasets. This process is detailed in the z/OS DLA Program Directory (publication number GI13-5562-00).
  2. Schedule a rollout of the DLA run-time environment to all z/OS images that will be the target of discovery.
  3. Roll out the DLA run-time environment to all target z/OS images:
    1. Make the target DLA datasets available on each z/OS image.
    2. Update the IPL process to APF-authorize the SIZDLOAD data set on each z/OS image (Optional for PoC phase if the site allows datasets to be APF authorized via the SETPROG z/OS command)
    3. Add IZDPDISC JCL PROC to a system PROCLIB data set on each z/OS image (Optional for PoC phase).
  4. Db2® customization is required for all Db2 subsystems that are the target of discovery:
    1. The DSNREXX interface must be bound to each Db2 subsystem where discovery is required. See the IBM® Db2 12 for z/OS Installation and Migration Guide for more information about how to bind the packages for DB2® REXX language support.
    2. The z/OS DLA user ID must have authority to issue the following DB2 DISPLAY commands and have read access to SYSIBM tables. Use the sample JCL IZDJGRANT in the SIZDSAMP library to assist in granting these authorities to the z/OS DLA user ID.
    3. If multiple versions of Db2 are installed on the operating system, a STEPLIB (or LINKLST entry) for the SDSNLOAD data set matching the Db2 version of the discovery target must be supplied.
  5. Define security access as required:
    1. The user ID that runs the z/OS DLA job or STC must have the following SAF authorities:
      1. READ access is recommended for all the data sets in the system PARMLIB concatenation used during IPL.
      2. If you have WebSphere® for MQ resources, ensure that all the required SAF authorities have access to run WebSphere for MQ discoveries.
      3. If RACF® is used to protect Db2 resources then authority is required to issue DB2 DISPLAY commands (including DISPLAY DB and DISPLAY GROUP) and to access (READ) SYSIBM resources using dynamic SQL.
  6. READ access is recommended to WebSphere HFS configuration files.
  7. The user ID that runs the discovery job must have an OMVS segment with authority to issue the netstat, host, and home commands.