Chapter17 Using SMPE..
Download
Report
Transcript Chapter17 Using SMPE..
Introduction to z/OS Basics
Chapter 17: Using SMP/E
© 2006 IBM Corporation
Chapter 17 SMP/E
Chapter objectives
After completing this
chapter, you will be able to
explain:
What SMP/E is
What system modifications
are
The data sets used by SMP/E
How SMP/E can help you
install and maintain products,
and monitor changes to
products
2
© 2006 IBM Corporation
Chapter 17 SMP/E
Key terms in this chapter
ACCEPT
distribution zone
APPLY
global zone
authorized program analysis
report (APAR)
HOLDDATA
consolidated service inventory
(CSI)
SYSMOD
distribution library (DLIB)
program temporary fix (PTF)
target library
zone
3
© 2006 IBM Corporation
Chapter 17 SMP/E
What is SMP/E?
SMP/E is the z/OS tool for managing the installation of
software products on a z/OS system and to track
modifications to those products.
SMP/E controls these changes at the component level by:
– Selecting the proper levels of code to be installed from a large number
of potential changes
– Calling system utility programs to install the changes
– Keeping records of the installed changes by providing a facility to
enable you to inquire on the status of your software and to reverse the
change if necessary.
All code and its modifications are located in the SMP/E
database called the consolidated software inventory (CSI),
which is comprised of one or more VSAM data sets.
4
© 2006 IBM Corporation
Chapter 17 SMP/E
The SMP/E view of the system…
z/OS is a complex system
comprising many different
smaller blocks of code.
RACF DB2
IS P F
Each of those smaller blocks of
code perform a specific function
in the system.
JE S
TSO
MVS
C IC S
S M P /E E R E P M Q
RMF
H T T P IM S
VTAM
W A S N e tvie w D F S M S P S F R R S
Each system function is
composed of one or more load
modules.
Load modules are created by
combining one or more object
modules and processing them
with a link-edit utility.
5
© 2006 IBM Corporation
Chapter 17 SMP/E
Elements of the system
Besides object modules and source code, most products distribute
many other parts such as macros, help-panels, CLISTs and other
z/OS library members.
These modules, macros and other types of data and code are the
basic building blocks of your system.
These building blocks are called elements.
Elements are associated with, and depend upon, other products or
services that may be installed on the same z/OS system.
6
© 2006 IBM Corporation
Chapter 17 SMP/E
What is a SYSMOD?
Over time, you will need to change the software on your z/OS system.
The combination of elements and control information is called a system
modification, or SYSMOD. It contains the information SMP/E needs to install
and track system modifications.
SYSMODs are comprised of two parts:
– Modification control statements (MCS) that indicate:
• What elements are being updated or replaced
• How the SYSMOD relates to product software and other SYSMODs
• Other specific installation information
– Modification text, which is the object modules, macros, and other elements
supplied by the SYSMOD.
7
© 2006 IBM Corporation
Chapter 17 SMP/E
Types of SYSMODS
There are four types of SYSMODs:
FUNCTION – Adds a new product or function
PTF – Provides an IBM correction to all z/OS installations
APAR – Provides a temporary fix to a specific z/OS installation
USERMOD – Adds an installation-provided modification.
8
© 2006 IBM Corporation
Chapter 17 SMP/E
Introducing an element into the system
To add new elements into your system, you install a function
SYSMOD.
A function SYSMOD is:
– a new product
– a new version or release of a product
– updated functions for an existing product into the system.
All other types of SYSMODs are dependent upon the function
SYSMOD.
9
© 2006 IBM Corporation
Chapter 17 SMP/E
Function SYSMOD…
10
© 2006 IBM Corporation
Chapter 17 SMP/E
Preventing or fixing problems with an element
When a problem with a software element is discovered, IBM
supplies its customers with a tested fix for that problem.
This fix comes in the form of a program temporary fix (PTF).
The PTF SYSMOD is used to install the PTF.
11
© 2006 IBM Corporation
Chapter 17 SMP/E
PTF SYSMOD…
12
© 2006 IBM Corporation
Chapter 17 SMP/E
Fixing problems with an element
Suppose you need to correct a serious problem that occurs on
your system before a PTF is ready for distribution? Here, IBM
supplies you with an authorized program analysis report or APAR.
An APAR is a fix designed to quickly correct a specific area of an
element or replace an element in error. Installing an APAR SYSMOD
updates the incorrect element.
The APAR SYSMOD “pre-reqs” a function SYSMOD. Also, it can
require the installation of other PTF or APAR SYSMODs.
13
© 2006 IBM Corporation
Chapter 17 SMP/E
APAR SYSMOD…
14
© 2006 IBM Corporation
Chapter 17 SMP/E
Customizing an element
z/OS provides certain modules that allow you to tailor IBM code to
meet your specific needs.
The USERMOD SYSMOD can be used to replace or update an
element, or to introduce a totally new user-written element into the
system.
USERMOD SYSMOD pre-reqs: a function SYSMOD, and possibly
other PTF, APAR, or USERMOD SYSMODs.
15
© 2006 IBM Corporation
Chapter 17 SMP/E
USERMOD SYSMOD…
16
© 2006 IBM Corporation
Chapter 17 SMP/E
Keeping track of the elements of the system
Some reasons for tracking system elements:
– A PTF might contain many element replacements that pre-req other
SYSMODs.
– The same module might be part of many different load modules. If so,
that module must be replaced in all the load modules in which it exists.
SMP/E relies on modification identifiers to identify elements
and their various modifications and updates.
Three modification identifiers are associated with each
element:
– Function Modification Identifiers (FMIDs)
– Replacement Modification Identifiers (RMIDs)
– Update Modification Identifiers (UMIDs),
17
© 2006 IBM Corporation
Chapter 17 SMP/E
How does SMP/E work?
Where changes are kept:
– Distribution libraries -- contain all the elements that are used as input
for running your system. Also important for backup.
– Target libraries -- contain the executable code needed to run the
system.
– consolidated software inventory (CSI) -- contains information about
the structure of a z/OS system.
– The CSI contains entries for the elements in the distribution and target
libraries, grouped into zones:
• Distribution zone
• Target zone
• Global zone
18
© 2006 IBM Corporation
Chapter 17 SMP/E
Relationship between SMP/E zones and libraries…
CSI
CSI
G lo b a l
Zone
T a rge t
Zone
T L IB s
19
CSI
D is trib u tio n
Zone
D L IB s
© 2006 IBM Corporation
Chapter 17 SMP/E
Working with SMP/E
The SMP/E process is performed by three simple basic
commands:
RECEIVE – place a SYSMOD into the SMP/E library and create the
CSI entries for them.
APPLY -- specifies which of the received SYSMODs are to be
selected for installation in the target libraries (TLIBs). SMP/E also
ensures that all other required SYSMODs (prerequisites) have been
installed in the proper sequence.
ACCEPT -- takes the selected SYSMODs and installs them into the
associated distribution libraries. SMP/E also ensures that the
correct functional level of each element is selected.
20
© 2006 IBM Corporation
Chapter 17 SMP/E
Other data sets used by SMP/E
SMPPTS (PTS) - temporary storage of SYSMODs waiting to
be installed.
SMPSCDS (SCDS) - backup copies of target zone entries
modified during APPLY processing.
SMPMTS (MTS) - stores copies of macros during installation
SMPSTS (STS) -stores copies of source during installation
SMPLTS (LTS) – stores the base version of a load module
Other utility and work data sets.
21
© 2006 IBM Corporation
Chapter 17 SMP/E
Summary
– In z/OS, the primary means for managing changes to the system
software is through SMP/E.
– SMP/E can be run either using batch jobs or using dialogs
– Software to be installed must be packaged as system modifications or
SYSMODs
– SMP/E JCL and commands are used frequently by system programmers
– The product and SYSMOD packaging will include the necessary MCS
statements
– A critical responsibility of the system programmer is to work with IBM
defect support when a problem surfaces in z/OS or option IBM products
– Problem resolution will require the system programmer to receive and
apply fixes to the enterprise system.
22
© 2006 IBM Corporation