Storing configuration files and policy definition files

You can store configuration files and policy definition files in the z/OS® UNIX file system or in traditional MVS™ data sets.

Some definitions are shared by all TCP/IP stacks on a z/OS image, and some definitions are specific to individual TCP/IP stacks on a z/OS image.

For example, if you are using the z/OS UNIX file system to store your configuration files and policy definition files, a directory structure for z/OS image SYSA with TCP/IP stacks TCPIP1 and TCPIP2 might look as follows:

Similarly, you can use MVS partitioned data set (PDS) or partitioned data set extended (PDSE) libraries to store the configuration files and policy definition files as follows:

You can maintain a number of members in each of these libraries, using your own naming convention or the following suggested naming convention:

The following example shows the IKE daemon configuration file and the IPSec policy definitions for stack TCPIP1 as members of PDS or PDSE libraries:

USER.LPAR1.POLTRANS.SYSA.IKED(CONF)
USER.LPAR1.POLTRANS.SYSA.TCPIP1(IPSPOL)