Abstract for SMP/E User's Guide
Summary of changes
Changes made in SMP/E Version 3 Release 6
Changes made in SMP/E Version 3 Release 5
Changes made in SMP/E Version 3 Release 4
SMP/E primer
What is SMP/E, and why should I use it?
Understanding your system
Changing the elements of the system
Introducing an element—the function SYSMOD
Preventing or fixing problems with an element—the PTF SYSMOD
Fixing problems with an element—the APAR SYSMOD
Customizing an element—the USERMOD SYSMOD
SYSMOD prerequisites
Keeping track of the elements of the system
Tracking and controlling requisites
How does SMP/E work?
The distribution and target libraries
The consolidated software inventory (CSI)
The SMP/E zones
What are the basic SMP/E commands I need to know?
Setting the zone you want to work on
Receiving the SYSMOD into SMP/E's data sets
Applying the SYSMOD to the target libraries
Restoring the target libraries to the previous level
Accepting the SYSMOD and updating the distribution libraries
Displaying SMP/E data
Flow of SMP/E SYSMOD processing
Receiving the SYSMOD into SMP/E's data sets
What happens during RECEIVE processing
What happens during internet service retrieval
How SMP/E keeps track of RECEIVE processing
Using the RECEIVE command
Examples
Receiving SYSMODs and HOLDDATA
Receiving only HOLDDATA
Receiving only SYSMODs
Receiving SYSMODs and HOLDDATA for a specific product
Requesting a new PTF order with the RECEIVE ORDER command
Reporting output
Summary of the RECEIVE command
Applying the SYSMOD to the target libraries
What happens during APPLY processing
Selecting the SYSMODs
Selecting the elements
Checking the APPLY process
Updating the target libraries
How SMP/E keeps track of APPLY processing
Using the APPLY command
Examples
Applying PTF SYSMODs
Applying APAR and USERMOD SYSMODs
Applying SYSMODs for selected products
Applying SYSMODs having prerequisites
Applying SYSMODs using the CHECK operand
Reporting output
Summary
Restoring the target libraries to the previous level
What happens during RESTORE processing
Removing the SYSMODs
Selecting the elements
Checking the RESTORE process
Replacing the elements in the target libraries
How SMP/E keeps track of RESTORE processing
Using the RESTORE command
Examples
Restoring a single SYSMOD
Restoring SYSMODs using the GROUP operand
Restoring SYSMODs using the CHECK operand
Reporting output
Summary
Accepting the SYSMOD into the distribution libraries
What happens during ACCEPT processing
Selecting the SYSMODs
Selecting the elements
Checking the ACCEPT process
Updating the distribution libraries
How SMP/E keeps track of ACCEPT processing
Using the ACCEPT command
Examples
Accepting PTF SYSMODs
Accepting SYSMODs for selected products
Accepting SYSMODs having prerequisites
Accepting SYSMODs using the CHECK operand
Reporting output
Summary
Displaying SMP/E data
Using the query dialogs
Using the LIST command
Examples
Listing entries in a particular zone
Listing Specific Entries
Listing SYSMODs that are received but not installed
Reporting output
Using the REPORT commands
Example
Reporting output
SMP/E CSI application programming interface
Summary
SMP/E concepts
What is SMP/E?
What are SYSMODs?
Data sets used by SMP/E
How SMP/E can help you install and maintain products
Where to begin
Specifying the zone to be processed: SET
Installing SYSMODs
Loading SYSMODs into the SMPPTS: RECEIVE
Using internet service retrieval to request PTF or HOLDDATA: RECEIVE ORDER
Requesting a new PTF service order
Downloading pending orders
Installing SYSMODs in the target libraries: APPLY
Installing SYSMODs in the distribution libraries: ACCEPT
Building a system from a set of distribution libraries: GENERATE
Monitoring your system
Displaying information from the SMP/E database: LIST
Checking and comparing zone contents: REPORT
Managing the SMP/E database
Removing SYSMODs from the target libraries: RESTORE
Removing SYSMODs from the PTS: REJECT
Processing the SMP/E database to create, update, or delete a single entry: UCLIN
Processing the SMP/E database to update several entries of the same type: ZONEEDIT
Processing the SMP/E database to define the structure of the target libraries: JCLIN
Processing the SMP/E database to write information to the SMPLOG data set: LOG
Processing the SMP/E database to clean up the SMPLTS, SMPMTS, SMPSTS, and SMPSCDS data sets: CLEANUP
Managing zones
Copying a zone from one CSI to another: ZONECOPY
Copying a zone to a sequential data set: ZONEEXPORT
Copying a zone from a sequential data set to a CSI data set: ZONEIMPORT
Deleting a zone: ZONEDELETE
Merging zones: ZONEMERGE
Renaming a zone: ZONERENAME
Linking and relinking modules
Handling cross-zone link-edits: LINK MODULE
Relinking load modules that use CALLLIBS: LINK LMODS
General SMP/E processing
Requesting diagnostic processing: DEBUG
Resetting return codes: RESETRC
Preparing to use SMP/E
Authorizing use of SMP/E commands and services
Allocating and initializing data sets in the SMP/E database
CSI data sets
Deciding how to organize CSI data sets
Single-CSI structure
Multiple-CSI structure
Examples of CSI structures
Example 1: Using a separate global zone for each subsystem
Example 2: Using a single CSI for the whole system
Example 3: Using a master CSI and multiple CSIs
Example 4: Using a master CSI and a separate CSI for each zone
Example 5: Using a master CSI and one CSI per SREL
Catalog considerations
Allocating a CSI data set
Defining an alias entry for a user catalog
Defining zones for your system
Reorganizing a CSI data set to reclaim space
PTS data sets
SCDS data sets
How to dynamically allocate data sets to be used during SMP/E processing
Sources of information for dynamic allocation
DDDEF entries
SMPPARM member GIMDDALC
Standard defaults
How dynamic allocation works
Defining utility programs and associated parameters to SMP/E
Using default values for utility programs
Defining values for utility programs
Example: How to request the desired utility processing
Recovering after errors from utility processing
Overview of your input to retry processing
Example: How to request the desired retry processing
Connecting SMP/E dialogs to ISPF
Check for required programs
Add dialog modules to the PCF command table
Concatenate the dialog libraries
SMPTABL space allocation
Sample logon procedure
Connect the dialogs to ISPF
Customize the SMP/E dialogs
JOB statement customization
Setting up SMP/E for easier operation
Recommended values for OPTIONS entry
Sample UCLIN job
Activating the OPTIONS entry
Recommended DDDEF entries for link-edit utility output
Specifying automatic cross-zone requisite checking
Defining a default zone group
Specifying the zone group on a command
Define a ZONEINDEX for each zone
Cross-zone requisite checking
Bypassing unsatisfied cross-zone requisites
Resolving cross-zone requisites
Defining the information needed to invoke SMP/E
Required JCL statements
JOB statement
EXEC statement
DD statements
Sample cataloged procedure for SMP/E
How to determine the appropriate SYSLIB concatenation
Checking that you have the appropriate access
Defining exit routines
Preparing to use Internet service retrieval
Identity and authentication overview
Obtaining a user certificate
Uploading the user certificate to z/OS
Setting up z/OS security server RACF
Access to the RACDCERT command
Creating key rings
Enabling certificate authority certificates
Adding the user certificate to your RACF data base
Sharing a user certificate among multiple user IDs
Debugging key ring and certificate issues
Replacing a user certificate that expired
Refreshing RACF classes
Setting up alternate security products
eTrust® CA-ACF2 security for z/OS users
eTrust CA-Top Secret security for z/OS users
Defining the ORDERSERVER input for RECEIVE ORDER
Defining the CLIENT input for RECEIVE ORDER
Options that affect Java
Options that affect HTTPS operations
Options that affect FTP operations
Firewall servers
FTP.DATA configuration file
IBM's secure FTP server (FTPS)
Network configuration notes
Summary
Example
Preparing for secure Internet delivery
Secure Sockets Layer overview
Enabling certificate authority certificates
Access to certificate authority certificates
Displaying certificate authority certificates
Adding certificate authority certificates
Access for SMP/E to use certificate authority certificates
Refreshing RACF classes
Define CLIENT input for RECEIVE and GIMGTPKG
Options that affect HTTPS operations
Options that affect FTPS operations
Firewall servers
FTP.DATA configuration file
Example
Installing a new function
Introduction
RECEIVE-APPLY-ACCEPT method
The standard RECEIVE-APPLY-ACCEPT method
Preparing your system
Staging the SYSMODs: The RECEIVE process
Receiving the function SYSMOD
Updating the target libraries: The APPLY process
Checking the update: The APPLY CHECK process
Researching the APPLY CHECK reports
Getting additional SYSMODs
Updating the target library: The APPLY process
Testing the new function
Updating the distribution libraries: The ACCEPT process
Checking the update: The ACCEPT CHECK process
Researching the ACCEPT CHECK reports
Getting additional SYSMODs
Updating the distribution library: The ACCEPT process
Checking other zones for requisites: REPORT CROSSZONE
Installing preventive service
Introduction
CBPDO tapes
ESO tapes
A RECEIVE ORDER request
Preventive service process: Summary
Preparing your system
Staging the SYSMODs: The RECEIVE process
Updating the target libraries: The APPLY process
Checking the update (APPLY CHECK)
Researching the APPLY CHECK reports
Getting additional SYSMODs
Updating the target library (APPLY)
Installing PTFs that need special processing
Testing the new service level
Updating the distribution libraries: The ACCEPT process
Checking the update (ACCEPT CHECK)
Researching the ACCEPT CHECK reports
Getting additional SYSMODs
Updating the distribution library (ACCEPT)
Installing PTFs that need special processing
Installing corrective service
Introduction
Building or checking the fix
Preparing your system
Staging the SYSMODs: the RECEIVE process
Generating a service request using the RECEIVE ORDER Command
Updating the target libraries: the APPLY process
Checking the update (APPLY CHECK)
Researching the APPLY CHECK reports
Using HOLDDATA to assist in identifying fixes
Getting additional SYSMODs
Updating the target library (APPLY)
Testing the corrective service
Updating the distribution libraries: the ACCEPT process
Checking the update (ACCEPT CHECK)
Researching the ACCEPT CHECK reports
Using HOLDDATA to assist in identifying fixes
Getting additional SYSMODs
Updating the distribution library (ACCEPT)
Installing a user modification
Introduction
Preparing your system
Staging the SYSMODs: The RECEIVE process
Updating the target libraries: The APPLY process
Checking the update (APPLY CHECK)
Researching the APPLY CHECK reports
Updating the target library (APPLY)
Testing the USERMOD
Updating the distribution libraries: The ACCEPT process
Managing exception SYSMODs
Introduction
What SMP/E does with the HOLDDATA
Initial entry into staging data sets: RECEIVE
Updating target libraries: APPLY
Updating distribution libraries: ACCEPT
Removing HOLDDATA from SMP/E data sets
During RESTORE processing
With the REJECT command
Sources of HOLDDATA
CBPDO tapes
ESO tapes
PSP information
Automated service delivery package
How to process HOLDDATA
Processing HOLDDATA from a CBPDO tape
Processing HOLDDATA from an ESO
Processing HOLDDATA from PSP files
Example of processing HOLDDATA
Creating cross-product, cross-zone load modules: The LINK MODULE command
When to use LINK MODULE
How to use LINK MODULE
Displaying the data managed by SMP/E: The LIST command
Introduction
Listing all the SMP/E data
Listing by specific entry type
Listing specific entries
Listing by FMID or FMIDSET
Listing to compare two zones
Summary
Changing the data SMP/E manages: The UCLIN command
Introduction
When to use UCLIN
How to use UCLIN
Identifying cross-zone requisites: The REPORT CROSSZONE command
Introduction
Identifying zones to be processed
Running the REPORT CROSSZONE command
Installing the SYSMODs
Identifying installed SYSMODs affected by error holds: The REPORT ERRSYSMODS command
Introduction
Running the REPORT ERRSYSMODS command
Installing the SYSMODs
Listing the source IDs in a zone: The REPORT SOURCEID command
Introduction
Running the REPORT SOURCEID command
Listing the SYSMODs
Comparing the SYSMODs installed in two zones: The REPORT SYSMODS command
Introduction
Running the REPORT SYSMODS command
Installing the SYSMODs
Building a user modification
Choosing between a USERMOD and a function SYSMOD
Creating the MCSs
The ++USERMOD MCS
The ++VER MCS
Specifying the proper system release
Specifying the FMID value
Specifying the proper requisites
Relationships to earlier versions of the elements
Relationships to Other SYSMODs
Specifying superseded SYSMODs
The ++JCLIN MCS
++MOD and ++ZAP MCSs
++MAC and ++MACUPD MCSs
++SRC and ++SRCUPD MCSs
The ++PROGRAM MCS
Data element MCSs
Hierarchical file system element MCSs
Examples of USERMODs
Example 1: Updating a module
Example 2: Replacing a module
Example 3: Adding new modules
Example 4: Replacing a macro or source code
Example 5: Updating a macro or source code
Example 6: Adding new source code
Example 7: Adding new source code that uses an IBM-supplied macro
Example 8: Adding a new module that uses an IBM-Supplied macro
Determining which SYSMODs led others to fail: The causer SYSMOD summary report
Introduction
Using causer SYSMOD information
Resolving errors for all SYSMODs that failed
Resolving errors for a single SYSMOD that failed
Example
Java archive update exploiter's guide
JAR replacements in FMIDs
JAR updates in PTFs
JAR replacements in PTFs
Migration
Migration overview
Terms you need to know
SMP/E release levels
Developing a migration strategy
Reviewing changes to SMP/E processing
Reviewing changes to SMP/E interfaces
SMP/E V3R6 overview
Multitasking using GIMDDALC SYSPRINT allocation
Adding SAF checks to SMP/E processing (IO11698)
Cross Global Zone Reporting
SYSMOD Comparison HOLDDATA Report
Retention of HOLDDATA (IO13643)
SMP/E V3R5 overview
Enhanced utility input
Coexistence considerations
Migration tasks
Long SOURCEID support
Coexistence considerations
ZONEMERGE command
Coexistence considerations
Migration tasks
HTTPS and FTP enhancements
HOLDDATA report changes
BYPASS(HOLDSYS) message severity changes
Migration tasks
ZONEEDIT enhancement
RECEIVE ORDER processing enhancements
Programmatic PSP-bucket processing
SMP/E V3R4 overview
Enhancement to the RECEIVE command
ORDERSERVER data set
CLIENT data set
Coexistence considerations
Impacts to SMP/E zone entries
ORDER entry in the global zone
ORDER RETENTION subentry on the OPTIONS entry
Coexistence considerations
ICSF not required for GIMZIP and RECEIVE FROMNETWORK
Improved load module build processing
SMP/E order management dialog
SMP/E query dialog
SMP/E V3R3 overview
GIMGTPKG service routine
Enhancements to GIMZIP and GIMUNZIP service routines
RECEIVE FROMNETWORK FTP interface enhancements
Migration tasks
REJECT CHECK command
Extended RECEIVE SOURCEID processing
SPCLCMOD and CMWA
SMP/E V3R2 overview
LINK LMODS command
REPORT CALLLIBS command removal
UPGRADE command
Coexistence considerations
GIMXSID service routine
GIMZIP: Archive segmentation
Coexistence considerations
GIMZIP: User defined subdirectories
Coexistence considerations
Java archive files
Coexistence considerations
Smaller SMPLTS data set
Coexistence considerations
DUMMY data set for SYSDEFSD
Coexistence considerations
SMP/E dialog customization
Migration tasks
GIMUTTBL removal
Migration tasks
SMP/E V3R1 overview
Defining exit routines using SMPPARM member GIMEXITS
Migration tasks
Dynamic allocation using SMPPARM member GIMDDALC
Migration tasks
Enhanced link name values
Coexistence considerations
Migration tasks
Removal of function to create backup IEANUC01 load modules
Migration tasks
Conditional JCLIN processing
Coexistence considerations
Network delivery of SMP/E input
Coexistence considerations
AMODE=64 and COMPAT=PM4 link edit parameters
Selected SMP/E data sets may now reside in a UNIX file system
HFS data set identification
SMPPTS spill data sets
HOLDDATA summary reports
SMP/E load modules and service routines moved to SYS1.MIGLIB
GIMXTRX service routine
OS/390 version 2 release 7 SMP/E overview
SMP/E planning and migration assistant
Data element reformatting
Coexistence considerations
Description for a SYSMOD
Improved protection for UNIX file system files
Coexistence considerations
Pre-built load module support
Product data
Sequential data set support
Coexistence considerations
Shell script support
Symbolic link support
OS/390 version 2 release 5 SMP/E overview
CBIPO dialogs
Client code installation
Coexistence considerations
Global zone merge
Library change interface
Coexistence considerations
Improved load module build processing
Load module return code
Coexistence considerations
Performance improvements
PTF compaction in SMPPTS data set
Coexistence considerations
Enhanced RECEIVE command processing
Coexistence considerations
Reduced SMP/E message output
Coexistence considerations
GIMAPI: All entries and subentries support
GIMAPI: Version support
Coexistence considerations
OS/390 version 1 release 3 SMP/E overview
API for user access to the CSI
Enhanced cross-zone requisite checking
Coexistence considerations
Enhanced exception SYSMOD report
Coexistence considerations
Enhanced ++IF FMID processing
Enhanced internal HOLD SYS processing
Coexistence considerations
Enhanced ZONEEDIT command
Enhancements to the binder utility in DFSMS/MVS
Coexistence considerations
System/390 service update facility
OS/390 version 1 release 2 SMP/E overview
BLOCKSIZE=8800 for SMP/E data sets
BUILDMCS command
Coexistence considerations
Bypassing system holds for specific SYSMODs
FMIDSET selection
Receiving relative file data sets created from PDSEs
SMP/E dialogs: FIND command
SMP/E GIMOPCDE member moved from PARMLIB
Recommended service upgrade (RSU)