The DFHAUPLE procedure, shown in
Figure 1, is tailored to your CICS environment and stored in the
CICSTS31.XDFHINST
library when you run the DFHISTAR job. (For information about DFHISTAR, see
the CICS® Transaction Server for z/OS® Installation
Guide.) It consists of the following steps:
- ASSEM: This step puts your table definition macros into a temporary partitioned
data set (PDS) member that is used as input to the ASM and SMP steps. The
BLDMBR step subsequently adds further members to this temporary PDS.
- ASM: In this assembly step, SYSPUNCH output goes to a temporary sequential
data set. This output consists of IEBUPDTE control statements, lin-edit control
statements, SMP control statements, and the object deck.
- BLDMBR: In this step, the IEBUPDTE utility adds further members to the
temporary PDS created in the ASSEM step. These members contain link-edit
control statements and SMP control statements, and the object deck from the
assembly step.
- LNKEDT: The link-edit step uses the contents of the PDS member LNKCTL
as control statements. The object code produced in step 2 comes from the
temporary PDS. The output goes to the load library that is specified by the
NAME parameter on the procedure. You must specify NAME=SDFHAUTH for the CLT,
RST, and SIT, and NAME=SDFHLOAD for all the others.
- ZNAME: This step creates a temporary data set that passes to the SMP/E
JCLIN job step; it contains a SET BDY command that defines a target zone name.
This tells SMP/E which target zone to update.
- SMP: The SMP step uses the temporary PDS members MACROS, SMPCNTL, SMPJCL1,
SMPJCL2, LNKCTL, SMPEOF, and the object deck to update the control data set
(CDS).
- DELTEMP: This final step deletes the temporary partitioned data set, &&TEMPPDS.
This step must run successfully if you want SMP to reassemble CICS tables
automatically when applying later maintenance.
Figure 1. Assembling and link-editing the control tables
using the DFHAUPLE procedure