Included members

You can divide the HFM2PARM across multiple members using the include specification. The format for an included member is as follows:

Multiple levels of include nesting are supported, circular (recursive) definitions will result in an error and Z Data Tools will not initialize.

Empty included members are ignored.

Example 1:

Suppose in a sysplex environment there are 4 z/OSĀ® images, with system IDs SYS1, SYS2, SYS3, and SYS4. Z Data Tools is available on all images, with different auditing requirements on each image.

Include members can be used to code this as follows:

Member HFM2PARM

<Z SYS1>
%HFMPSYS1
</Z>
<Z SYS2>
%HFMPSYS2
</Z>
<Z SYS3>
%HFMPSYS3
</Z>
<Z SYS4>
%HFMPSYS4
</Z>

Member HFMPSYS1

FMAUDIT SAF_CTRL=YES

Member HFMPSYS2

FMAUDIT SAF_CTRL=NO

Member HFMPSYS3

FMAUDIT SAF_CTRL=NO

Member HFMPSYS4

FMAUDIT SAF_CTRL=YES

This has the advantage of consolidating all the options for each z/OS image in a specific member.

If you used Method 1 to add member HFM2PARM to the logical parmlib concatenation (see Defining the HFM2PARM member for more information), be careful to avoid any conflicts between included member names and existing member names in the logical parmlib concatenation.