SMP/E for z/OS User's Guide
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Defining zones for your system

SMP/E for z/OS User's Guide
SA23-2277-01

Once you have allocated and initialized the CSI data sets, you need to create within them the entries SMP/E uses to maintain your system. The first entries you need to define are the zone definition entries (GLOBALZONE, TARGETZONE, and DLIBZONE entries) which set up zones in CSI data sets.
  • GLOBALZONE entry. A global zone is created by defining a GLOBALZONE entry. The GLOBALZONE entry contains processing-related information for SMP/E. It is also used by SMP/E as an index to target and distribution zones, either in the same CSI or in different CSI data sets. The GLOBALZONE entry must be defined before you can do any other processing for that global zone.
  • TARGETZONE entry. A target zone is created by defining a TARGETZONE entry. The TARGETZONE entry contains information SMP/E uses to process a specific target zone and the associated target libraries. It must be defined before you can do any other processing for that target zone.
  • DLIBZONE entry. A distribution zone is created by defining a DLIBZONE entry. The DLIBZONE entry contains the information SMP/E uses to process a specific distribution zone and the associated distribution libraries. It must be defined before you can do any other processing for that distribution zone.

Figure 1 illustrates how zone definition entries define the relationships between zones.

Figure 1. Relationships between zone definition entries
Zone definition entries define the relationships between zones.
After you have defined the zones for your system, you can create other entries. SMP/E zones contain two basic types of entries:
  • Entries controlling SMP/E processing.

    You generally define processing control entries through the SMP/E Administration dialogs or with the UCLIN command. Table 1 summarizes the information specified in these entries.

  • Entries describing the structure and status of the target and distribution libraries.

    Status and structure entries are generally created by SMP/E when you install SYSMODs, run the JCLIN command, or copy entries from one zone to another. Table 2 summarizes the information specified in these entries.

SMP/E provides a member in SYS1.SAMPLIB (GIMSAMPU) containing sample UCLIN statements to define entries for a basic z/OS® system. You can access this member by use of standard system utilities. The sample definitions are syntactically correct and can be used as the basis for your CSI entries. This sample is not complete for all systems, but it is an example of the types of information various entries need. For examples of UCLIN to define entries, see SMP/E for z/OS Commands, which has the UCLIN syntax for each entry type. Also see the section on SMP/E data set entries in SMP/E for z/OS Reference, which contains a description of the syntax plus examples and notes on its use.

Table 1. Entries controlling SMP/E processing
Type of information Entry type Zone where defined
Global Target DLIB
Data set definitions for dynamic allocation1 DDDEF X X X
DLIB zone processing information DLIBZONE     X
Exception (held) SYSMODs2 HOLDDATA2 X    
FMIDs to limit the SYSMODs processed by an SMP/E command FMIDSET X    
Global zone processing information GLOBALZONE X    
Processing options3 OPTIONS X    
Target zone processing information TARGETZONE   X  
Utility program parameters4 UTILITY X    
Zone names to limit the SYSMODs processed by an SMP/E command ZONESET X    
  1. For more information about dynamically allocating data sets, see How to dynamically allocate data sets to be used during SMP/E processing.
  2. For more information about processing exception SYSMODs, see Managing exception SYSMODs. HOLDDATA entries cannot be updated by UCLIN or the Administration dialogs.
  3. For more information about defining information to be used during SMP/E's retry processing after x37 abends, see Recovering after errors from utility processing.
  4. For more information about defining utility programs and associated parameters, see Defining utility programs and associated parameters to SMP/E.
Table 2. Entries describing the status and structure of the target and distribution libraries
Type of information Entry type Zone where defined
Global Target DLIB
Assembler statements that can be assembled to create an object module ASSEM   X X
Data elements installed in the target or distribution libraries (data elements are elements other than macros, modules, or source) Data element entries   X X
Distribution libraries that were totally copied to target libraries DLIB   X X
Elements installed in a UNIX file system Hierarchical file system element entries   X X
Java™ Archive files JAR   X X
Java Archive update files JARUPD   X X
Load module information LMOD   X X
Macros that have been installed in the target or distribution libraries MAC   X X
Module source that has been installed in the target or distribution libraries SRC   X X
Modules used to create load modules in the target libraries MOD   X X
Program objects PROGRAM   X X
Software product information PRODUCT X    
Software product feature information FEATURE X    
SYSMODs that have been processed SYSMOD X X X
Parent topic: CSI data sets

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014