SMP/E is IBM's tool for managing software installations on the z/OS mainframe. SMP/E manages software versions, helps apply patches and updates (PTFs), facilitates orderly testing and, if necessary, reversion to a previous state.
This section explains some of the basic terms and concepts used by SMP/E. If you need more detailed information on SMP/E, see the IBM documentation.
Tailored installation jobs
If applicable, this section also points out where SMP/E commands and actions are reflected in the tailored installation jobs. The standard installation assumes that BSA V7R1, Beta 23 V7R2, and Adabas Audit Data Retrieval V7R2 are installed in the same SMP/E environment.
The basic building blocks of software include object modules, skeletons, panels, and other types of data. All of these building blocks are called elements.
A SYSMOD is a package for SMP/E that includes the element together with information that SMP/E needs to install and track system modifications. Each SYSMOD is assigned a seven character SYSMOD ID to uniquely identify it.
There are four different categories of SYSMODs:
The seven character FMID (Function Module ID) identifies a piece of software and its release number.
For example, the FMID of BSA V7R1 is RBS7100.
The FMID enables SMP/E to identify the various building blocks as belonging to the same piece of software.
Modification control statements (MCS) at the beginning of the SYSMOD package provide management instructions for SMP/E. Each MCS start with ++ as the first two characters, for example, ++PTF(ptfnum) identifies a PTF SYSMOD and ++HOLD(reason) instructs SMP/E to keep a PTF in the global zone until the reason has been confirmed.
The CSI datasets contain all the information SMP/E needs to track the elements in the distribution and target libraries.
The CSI stores information in three zones:
Tailored installation jobs
I#BSAJ01 through I#BSAJ05 create a new SMP/E environment.
A distribution library contains all the elements that are used as input for running your system. One very important use of the distribution libraries is for backup. Should a serious error occur with an element on the production system, the element can be replaced by a stable level found in the distribution library.
A target library contains all the executable code needed to run the system.
Tailored installation jobs
I#BSAJ06 through I#BSAJ07 allocate and define libraries for BSA.
I#B23J01 defines the BSA libraries also for Beta 23.
I#B97J01 through I#B97J02 allocate and define libraries for Adabas Audit Data Retrieval.
SMP/E installs SYSMODs in your target and distribution libraries.
The three basic commands provided for this are RECEIVE, APPLY, and ACCEPT.
The RESTORE command reverts to a previous state. RESTORE is not possible after ACCEPT.
Tailored installation jobs
I#BSAJ08 through I#BSAJ09 do the RECEIVE/APPLY/ACCEPT for the BSA SYSMODs.
I#B23J02 through I#B23J04 do the RECEIVE/APPLY/ACCEPT for the Beta 23 SYSMODs.
I#B97J03 through I#B97J05 do the RECEIVE/APPLY/ACCEPT for the Adabas Audit Data Retrieval SYSMODs
Note: There is no ACCEPT in the tailored installation jobs for PTF SYSMODs, only RECEIVE and APPLY.