Preparing the configuration profiles by running the KCIJPDLn jobs
By running the KCIJPDLn jobs in PARMGEN, the function of IBM Discovery Library Adapter for z/OS (DLA) is used to automatically discover the properties of online subsystems and other z/OS resources. These details are then included within the PARMGEN runtime environment (RTE) configuration user profiles, which reduces the time and effort in creating accurate configuration files.
Before you begin
- The KCIJPDLA composite job must run authorized. Dynamic SETPROG APF statement is included in
this job. If the z/OS DLA SMP/E target load library (GBL_TARGET_IZDHLQ.SIZDLOAD)
is in a NONSMS-managed volume, the dynamic SETPROG APF statement must specify the VOL() volume
parameter. For example:
If you supplied a GBL_TARGET_VOLUME value during KCIJPCFG "Set up/Refresh PARMGEN work environment" processing (KCIP@PG2 panel), then the KCIJPDLA or the KCIJPDL1 job's SETPROG statement will include the tailored VOL() parameter. If this is not the volume that the SIZDLOAD data set is on, customize the VOL() parameter accordingly. Otherwise, the DLADISC step will encounter the following error message:// SETPROG APF,ADD, // DSN=IBM.TARGET.SIZDLOAD,VOL(VOL001)
IZD0021E APF Discovery requested but not running APF Authorized
Note: It is ideal to run the DLADISC discovery function (KCIJPDL1 job function of the KCIJPDLA composite job) when the z/OS resources you plan to monitor are active. - If you are staging the z/OS DLA IDML data sets for other LPARs, you can use the
/*JOBPARM= parameter.
If you use the SYSAFF parameter, the LPAR must belong in the same JES Multi-Access Spool (MAS) Complex. If it is not in the same MAS, an alternative is to route the job by using the /*ROUTE XEQ parameter.JOBPARM SYSAFF=&SYSNAME. JOBPARM SYSAFF=*
ROUTE XEQ &SYSIPHOSTNAME
- The user ID that runs the KCIJPDLA or KCIJPDL1 job must have the following RACF authorities:
- READ access for all the data sets in the system PARMLIB concatenation that are used during IPL.
- READ access to profiles in the MQCMDS class (if active) to allow the z/OS DLA to run MQ
DISPLAY
commands via the MQ command interface. - If RACF is used to protect Db2 resources, then authority is required to run Db2
DISPLAY
commands and to access (READ) SYSIBM resources by using dynamic SQL. In addition, for the Db2 version autodiscovery, the z/OS DLA extracts the Db2 version via the Instrumentation Facility Interface (IFI). The ID that runs the KCIJPDLA or KCIJPDL1 job must have the appropriate authorization to issue the Db2 commands. Otherwise, the PARMGEN DLA jobs will not be able to set values to the KD2_DBnn_DB2_VER LPAR RTE profile parameter in the WCONFIG(RTE_NAMES) LPAR RTE profile. - READ access to WebSphere configuration files. An OMVS segment with authority to issue the
netstat
,host
, andhome
commands.
During SMP/E installation of DLA, the following SMP/E target data sets are allocated
and processed:
- gbl_target_hilev.SIZDEXEC
- gbl_target_hilev.SIZDINST
- gbl_target_hilev.SIZDLOAD
- gbl_target_hilev.SIZDMAPS (applicable for FMID HIZD310)
- gbl_target_hilev.SIZDMESG
- gbl_target_hilev.SIZDSAMP
Note: If you have a separate SMP/E
installation of the DLA, you can still use the PARMGEN z/OS DLA integration jobs (KCIJPDLA or
KCIJPDL1). If you have a separate SMP/E environment where the z/OS DLA target data sets exist,
modify the KCIJPDLn jobs to point to the appropriate
IZDHLQ=DLA_FMID SMP/E target high-level qualifier. Review the
KCIJPDLn jobs for more information.
About this task
- TCP/IP information
- z/OS information such as active PARMLIB members, IPL information, authorized programs
- System z hardware information such as serial numbers, LPARs, and z/VM guest information
- CICS information such as transactions, programs, and files
- Db2 for z/OS information such as databases and table spaces
- IMS information such as transactions, programs, and databases
- WebSphere information such as cell, node, and configuration files
- IBM MQ information such as queue managers, queues, channels, and ports
- Address space information such as type, data set allocations, program name, and TCP/UDP ports
- DASD volume information
Procedure
Use one of the following ways to run the KCIJPDLn jobs: