Appendix D. Samples provided in hlq.SIZDSAMP

The following samples are provided in hlq.SIZDSAMP.

Member in SIZDSAMP and the description are as follows:
IZDJRUN
Batch job JCL to run the DLA.
  • This invokes the IZDPDISC proc with an override on the output data set name since batch jobs don't allow system symbols.
  • This enables users to perform discovery without issuing a console command.
IZDPDISC
JCL PROC to run the DLA.
  • The PROC may be invoked as a started task or a batch job.
  • This procedure may be copied to a JES PROCLIB or invoked via a JCLLIB control statement in the JCL.
  • The default output datasets use the &SYSNAME system symbol to ensure a unique name within a Sysplex.
  • Having a started task enables discovery to be initiated via a console command, for example, include S IZDPDISC, as part of the normal post IPL start up process to pick up any system configuration changes.
IZDCDEF
Default DLA configuration parameter deck in IZDPDISC.

This configuration parameter deck is coded to show and cause discovery of the default resources. This includes z/OS®, Z Series Computer System and Sysplex, as well as application subsystems (such as Db2® subsystems and MQ subsystems). By default, discovery is limited to 100 resources per CICS®, IMS or Db2 plus WebSphere® and MQ discovery. The output from default discovery is placed in several books including ZOSBASE (basic z/OS and hardware information), ZOSTASK (z/OS address space related data), and individual books (one for each of the CICS, IMS, Db2, WebSphere and MQ subsystem that are discovered) that are named using the jobname or STC name of the discovered subsystem.

IZDJFTP
Batch job JCL to run the FTP only.

This invokes the IZDPFTP proc with an override on the output data set name since batch jobs don't allow system symbols.

This enables users to perform FTP without running discovery.

IZDPFTP
JCL PROC to FTP the IdML members to the Discovery Library File Store.
  • The PROC may be invoked as a started task or a batch job.
  • This procedure may be copied to a JES PROCLIB or invoked via a JCLLIB control statement in the JCL.
  • IZDJDISC invokes this proc.
IZDCFTPI
Initial FTP statements used to PUT members to the Discovery Library File Store. For more information, see Target DLFS FTP server.
IZDCBASE
DLA configuration parameter deck to discover ZOSBASE only.
IZDCTASK
DLA configuration parameter deck to discover ZOSTASK only.
IZDCIMS
IZDCIMS IMS default parameter member.

The default member for IMS discovery IZDCIMS is coded to cause IMS only discovery. Additional non-IMS information is only discovered where it relates to IMS or is necessary for naming rules or IMS relationships.

The output for IMS discovery is placed in several books each book named using the jobname or STC name of the discovered IMS control region.

IZDCDB2
DLA configuration parameter deck to discover Db2 subsystems, including all attributes. Additional non-Db2 information is only discovered where it related to Db2 or is necessary for naming rules or Db2 relationships.

The output for Db2 discovery is placed in several books each book named using the jobname or STC name of the discovered Db2 master region.

IZDCCICS
DLA configuration parameter deck to discover CICS regions, including all attributes. Additional non-CICS information is only discovery where it relates to CICS or is necessary for naming rules or CICS relationships.

The output from CICS discovery is placed in several books each book named using the jobname or STC name of the discovered CICS region.

IZDCMQ
DLA configuration parameter deck to discover MQ subsystems, including all attributes. Additional non-MQ information is only discovered where it relates to MQ or is necessary for naming rules or MQ relationships.

The output for MQ discovery is placed in several books each book named using the jobname or STC name of the discovered MQ master address space.

IZDCWAS
DLA configuration parameter deck to discover WebSphere Application Severs, including all attributes. Additional non-WebSphere information is only discovered where it relates to WebSphere or is necessary for naming rules or WebSphere relationships.

The output for WebSphere discovery is placed in several books each book named using the jobname or STC name of the discovered WebSphere region.