Defining SNA data sets

This section describes z/OS® data sets that you need to define or modify for z/OS V2R1 Communications Server. Table 1 shows the z/OS data sets that contain information for z/OS V2R1 Communications Server, and Table 2 shows the z/OS data sets that contain information for both VTAM and NCP.

Enterprise Extender requires IP data set definitions in addition to the SNA data sets. See z/OS Communications Server: IP Configuration Guide for more information.

These tables show the data sets and the approximate storage requirements for any new data sets and for any existing data sets whose requirements might have changed since your last installation.
Tip: The data sets referenced in this section are not necessarily under the SYS1 HLQ. In fact, the entire name for some data sets can be different.
Table 1. z/OS data sets containing information for z/OS Communications Server
Name of data set Contents Comments
SYS1.DSDB1 Data files of APPN directory information Required for APPN directory checkpointing function; must be allocated before z/OS Communications Server initialization.

This data set cannot be allowed to span multiple volumes.

SYS1.DSDB2 Data files of APPN directory information Required for APPN directory checkpointing function; must be allocated before z/OS Communications Server initialization.

This data set cannot be allowed to span multiple volumes.

SYS1.DSDBCTRL Current status of SYS1.DSDB1 and SYS1.DSDB2 Required for APPN directory checkpointing function; must be allocated before z/OS Communications Server initialization.

This data set cannot be allowed to span multiple volumes.

SYS1.DUMPxx  Records of SVC DUMP Required for diagnosis.
SYS1.LINKLIB  z/OS Communications Server initialization module, ISTINM01, which is used when z/OS Communications Server is started Required.
Logon manager load modules Required for logon manager.
SYS1.LOGREC  z/OS Communications Server error records Required.
SYS1.LPALIB  z/OS Communications Server load modules and user-written exit routines to be loaded into the shared link pack area Required.
SYS1.MACLIB  z/OS Communications Server application program interface macros Required.
SYS1.MIGLIB  z/OS Communications Server formatted dump routines for the interactive problem control system (IPCS) and the z/OS Communications Server VIT Analysis Tool module, ISTRAFT1, which is used for problem diagnosis Required.
SYS1.NUCLEUS  z/OS Communications Server resident SVCs and abnormal termination modules Required.
SYS1.PARMLIB  IBM-supplied and installation-created members, which contain lists of system parameter values Required. This may also be a data set in the logical parmlib concatenation.
SYS1.PROCLIB  JCL for started tasks Required for logon manager.
SYS1.SBLSCLI0 IPCS REXX execs and CLISTs Required for z/OS Communications Server dump analysis enhancements and VIT analysis. See z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for more information.
SYS1.SBLSKEL0 ISPF skeletons for the IPCS dialog Required for z/OS Communications Server dump analysis enhancements and VIT analysis. See z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for more information.
SYS1.SBLSMSG0 ISPF messages for the IPCS dialog Required for z/OS Communications Server dump analysis enhancements and VIT analysis. See z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for more information.
SYS1.SBLSPNL0  ISPF panels for the IPCS dialog Required for z/OS Communications Server dump analysis enhancements and VIT analysis. See z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for more information.
SYS1.SBLSTBL0 ISPF tables for the IPCS dialog Required for z/OS Communications Server dump analysis enhancements and VIT analysis.
SYS1.SISTASGD  ASN.1 and GDMO syntax data sets Included for reference by CMIP services application programmers.
SYS1.SISTASN1  Contains two categories of data set members:
  • ACYPRES: List of abstract syntax notation 1 (ASN.1) definition data sets. This is a member of a partitioned data set.
  • The members listed in ACYPRES.
Required for CMIP services. See SYS1.SISTASN1 for a description.
SYS1.SISTCLIB  z/OS Communications Server load modules to be loaded into common service area and extended common service area (CSA/ECSA) storage Required.
SYS1.SISTCMIP Directory definition file. The member name of the directory definition file is ACYDDF. Required for CMIP services. See SYS1.SISTCMIP for a description.
SYS1.SISTDAT1 Online tools Optional. Use this library only if you intend to use the online information tools included with z/OS Communications Server.
SYS1.SISTDAT2 Message skeleton file for translation Required. See z/OS Communications Server: SNA Network Implementation Guide.
SYS1.SISTGDMO  Compiled definitions for the ISO standard, Guidelines for the Definition of Managed Objects (GDMO). This is a partitioned data set consisting of one member, ACYGDMO. Required for CMIP services.

Member name ACYGDMO must be included on the DD statement for SISTGDMO in the VTAM start procedure:

//ACYGDMO DD SYS1.SISTGDMO(ACYGDMO),DISP=SHR.

SYS1.SISTMAC1  z/OS Communications Server macros used to build user tables and parameter lists to build installation exits Required.
SYS1.TRACE  GTF trace records Required to run external trace.
Note: For information about using multiple SYS1.TRACE data sets, see the z/OS MVS Diagnosis: Tools and Service Aids.
SYS1.TRSDB Network topology database Required for APPN topology database checkpointing function; must be allocated before initialization.

This data set cannot be allowed to span multiple volumes.

Dynamic I/O configuration data sets Dynamically created definitions of devices with all associated LUs Optional; includes USER1.AUTO.VTAMLST and a catalog entry checkpoint data set. Required for dynamic I/O configuration.

Table 2 shows the z/OS data sets that contain VTAM information and NCP information if there is an NCP owned by that VTAM.

Table 2. z/OS data sets containing information for both VTAM and NCP
Name of data set Contents Comments
SYS1.ASAMPLIB  Sample of network operator command table and sample JCL for installation Required for installation. Provided by IBM®.
SYS1.SAMPLIB  Alterable copy of sample network operator command table, sample JCL for installation, and command lists for dynamic I/O Required for installation. Provided by IBM.
SYS1.SSPLIB NCP loader utility program Required; added when NCP is installed. See SYS1.SSPLIB for information on SYS1.SSPLIB requirements.
NCP dump utility program Required; added when NCP is installed. See SYS1.SSPLIB for information on SYS1.SSPLIB requirements.
NCP dump bootstrap program Required; added when NCP is installed. See SYS1.SSPLIB for information on SYS1.SSPLIB requirements.
SYS1.VTAMLIB 
  • Load modules for z/OS Communications Server
  • User-defined tables, default tables, and exit routines
Only z/OS Communications Server load modules are required. Must be listed in an IEAAPFxx parmlib member.
SYS1.VTAMLST  z/OS Communications Server definition statements and start options Required; created by user before starting z/OS Communications Server. You can modify this data set, but you need to be very careful about the relationship between z/OS Communications Server and NCP definition statements. For example, changing a VTAMLST member without changing a corresponding NCP definition statement can cause serious errors that are difficult to diagnose.
Configuration restart data sets z/OS Communications Server status of minor nodes for each major node Required if a warm restart is to be used. Created by user before starting z/OS Communications Server.
SYS1.NODELST  z/OS Communications Server status of major nodes Required if restart of all previously active major nodes is desired.
NCP load library NCP load modules Each NCP stored as a separate member of library. Created during NCP generation. Must be an APF-authorized library.
NCP dump data set Dump records for NCP Required if z/OS Communications Server is requested to provide a dump of NCP. Created by user before starting z/OS Communications Server.
SYS1.LDRIOTAB Dump records for loader channel I/O trace Required to hold loader channel I/O trace dumps. Created by user before starting z/OS Communications Server.
CSP and MOSS dump data set Dump records for CSP and MOSS Required if z/OS Communications Server is requested to provide a dump of CSP or MOSS and if the user wants to store the CSP or MOSS dump in a unique data set. Created by user before starting z/OS Communications Server.