SMP/E data sets for inventory, zones, and libraries

To install z/OS® elements in target and distribution libraries, SMP/E uses a database made up of several types of data sets.

SMPCSI (CSI) data sets

SMPCSI (CSI) data sets are VSAM data sets used to control the installation process and record the results of processing. A CSI can be divided into multiple partitions through the VSAM key structure. Each partition is referred to as a zone.

There are three types of zones:

A single global zone is used to record information about SYSMODs that have been received into the SMPPTS data set. The global zone also contains information enabling SMP/E to access the other two types of zones, information about system utilities that SMP/E calls to install elements from SYSMODs, and information allowing you to tailor SMP/E processing.
One or more target zones are used to record information about the status and structure of the operating system (or target) libraries. Each target zone also points to the related distribution zone, which can be used during APPLY, RESTORE, and LINK when SMP/E is processing a SYSMOD and needs to check the level of the elements in the distribution libraries.
One or more distribution zones are used to record information about the status and structure of the distribution libraries (DLIBs). Each DLIB zone also points to the related target zone, which is used when SMP/E is accepting a SYSMOD and needs to check if the SYSMOD has already been applied.

There can be more than one zone in an SMPCSI data set (in fact, there can be up to 32766 zones per data set). For example, an SMPCSI data set can contain a global zone, several target zones, and several distribution zones. The zones can also be in separate SMPCSI data sets. One SMPCSI data set can contain just the global zone, a second SMPCSI data set the target zones, and a third SMPCSI data set the distribution zones.

SMPPTS (PTS) data set

An SMPPTS (PTS) data set is a data set for temporary storage of SYSMODs waiting to be installed. The PTS is used strictly as a storage data set for SYSMODs. The RECEIVE command stores SYSMODs directly on the PTS without any modifications of SMP/E information. The PTS is related to the global zone in that both data sets contain information about the received SYSMODs. Only one PTS can be used for a given global zone. Therefore, you can look at the global zone and the PTS as a pair of data sets that must be processed (for example, deleted, saved, or modified) concurrently.

SMPSCDS (SCDS) data set

The SMPSCDS (SCDS) data set contains backup copies of target zone entries modified during APPLY processing. Therefore, each SCDS is directly related to a specific target zone, and each target zone must have its own SCDS. SCDS data sets are used by SMP/E to store backup copies of target zone entries modified during APPLY processing. Therefore, each SCDS is directly related to a specific target zone, and each target zone must have its own SCDS.

SMP/E also uses the following data sets:

The SMPMTS (MTS) data set is a library in which SMP/E stores copies of macros during installation when no other target macro library is identified. Therefore, the MTS is related to a specific target zone, and each target zone must have its own MTS data set.
The SMPSTS (STS) data set is a library in which SMP/E stores copies of source during installation when no other target source library is identified. Therefore, the STS is related to a specific target zone, and each target zone must have its own STS data set.
The SMPLTS (LTS) data set is a library that maintains the base version of a load module. The load module in this library specifies a SYSLIB allocation in order to implicitly include modules. Therefore, the LTS is related to a specific target zone, and each target zone must have its own LTS data set.
Other utility and work data sets.

SMP/E uses information in the CSI data sets to select proper element levels for installation, to determine which libraries should contain which elements, and to identify which system utilities should be called for the installation.

System programmers can also use the CSI data sets to obtain the latest information on the structure, content, and status of the system. SMP/E provides this information in reports, listings, and dialogs to help you:

Investigate function and service levels
Understand intersections and relationships of SYSMODs (either installed or waiting to be installed)
Build job streams for SMP/E processing.

Figure 1 shows sample job control language (JCL) for creating the CSI data sets.

Figure 1. JCL for defining a CSI VSAM data sets

//DEFINE	    JOB  'accounting info',MSGLEVEL=(1,1)
//STEP01    EXEC PGM=IDCAMS
//CSIVOL    DD	   UNIT=3380,VOL=SER=volid,DISP=SHR
//SYSPRINT  DD	   SYSOUT=A
//SYSIN     DD   * 
  DEFINE CLUSTER(                             -
                 NAME(SMPE.SMPCSI.CSI)        -
                 FREESPACE(10 5)              -
                 KEYS(24 0)                   -
                 RECORDSIZE(24 143)           -
                 SHAREOPTIONS(2 3)            -
         VOLUMES(volid1)                      -
                 )                            -
             DATA(                            -
                  NAME(SMPE.SMPCSI.CSI.DATA)  -
                  CONTROLINTERVALSIZE(4096)   -
                  CYLINDERS(250 20)           -
                 )                            -
            INDEX(                            -
                  NAME(SMPE.SMPCSI.CSI.INDEX) -
                  CYLINDERS(5 3)              -
                 )                            -
          CATALOG(user.catalog)
/*