System SSL parts shipped in PDS and PDSE

pdsename.SIEALNKE PDSE contains members GSKSSL, GSKCMS31, GSKSRBRD, GSKSRBWT, GSKKYMAN, GSKSCTSS, GSKSRVR, GSKCMS64, GSKS31, GSKS64, GSKC31, GSKC64 and GSKSSL64 when the base FMID HCPT410 is installed. When JCPT411 is installed, members GSKSUS31, GSKS31F, GSKS64F, GSKC31F, GSKC64F and GSKSUS64 are also in the PDSE.

pdsname.SIEAHDR PDS contains header files GSKSSL, GSKCMS and GSKTYPES.

pdsename.SIEASID PDS contains side files GSKSSL, GSKCMS31, GSKSSL64 and GSKCMS64 when the base FMID HCPT410 is installed.

pdsname.SGSKSAMP PDS contains members GSKMSGXT, GSKRACF, GSKSRVR and GSKWTR.

pdsename.SIEAMIGE PDS contains member GSKSCTFT.

pdsname and pdsename are the names determined during installation. You need to know the name of this PDS or PDSE when you identify the STEPLIB in the runtime steps. See z/OS Program Directory for information about installing the System SSL.

Note:

The DLLs are shipped in PDSE form so the DLLs can be called from UNIX System Services file-system-based or PDSE-based programs.
The DLLs are not placed in SYS1.LPALIB during installation. The DLLs cannot be added to an LPALSTxx member since PDSE data sets are not supported in LPALSTxx. The DLLs can be added to the dynamic LPA by adding them to a PROGxx member.
The DLLs cannot be added to the LPA if System SSL is to be used in FIPS mode.

System SSL is designed to meet the National Institute of Standards and Technology (NIST) FIPS 140-2 criteria. For more information about enabling applications and running System SSL FIPS enabled applications, see System SSL and FIPS 140-2.