Applying Maintenance with SMP/E
| We recommend that you check for any critical HIPER PTFs before proceeding with the installation. PTFs are available at https://go.compuware.com or by contacting BMC Customer Solutions at 1-800-538-7822. For telephone numbers in other geographies, see the list of worldwide offices at http://www.compuware.com. See Information for Customer Solutions for more information. |
For Strobe Release 18.02, refer to the Maintenance chapter of the Compuware Installer Mainframe Products SMP/E installation Guide for the procedures to install preventive maintenance using SMP/E. A link to this document was included to the e-mail you were sent regarding Receive From Network (RFN) using SMP/E for your order of Compuware mainframe products. This document is also included on the Compuware product documentation site at https://go.compuware.com.
After you have completed the maintenance procedures using SMP/E, return here to complete Update Runtime Libraries below and Maintaining Strobe for Db2/DDF and Strobe SQL Analysis on page 164 if your site is licensed for Strobe for Db2/DDF and Strobe SQL Analysis support.
Update Runtime Libraries
If you have created separate runtime libraries, then after the successful completion of all Strobe SMP/E maintenance activities and appropriate testing, the content of these libraries must be replaced.
| If you have made any updates outside of SMP/E to your runtime libraries and you want to preserve them, you must do so before replacing the library. |
The SMP/E target libraries listed in the following table typically have corresponding runtime copies.
SMP/E Target Libraries That Typically Have Corresponding Runtime Copies
Library | Description |
|---|---|
SSTRAUTH | StrobeAuthorized Load Library |
SSTRCLST | StrobeCLIST/EXEC Library |
SSTRLOAD | StrobeUnauthorized Load Library |
SSTRMENU | StrobeISPF Message Library |
SSTRMSGS | StrobeMessages Library |
SSTRPARM | StrobeParameter Library |
SSTRPENU | StrobeISPF Panel Library |
SSTRPROC | StrobePROC Library |
SSTRSAMP | StrobeSample Library |
SSTRSKEL | StrobeISPF Skeleton Library |
Maintaining Strobe for Db2/DDF and StrobeSQL Analysis
| If your site is not licensed for StrobeDb2/DDF and StrobeSQL Analysis support, skip this and the following next two sections below. |
All of Strobe’s DBRMs are created with VERSION(strobe_value). The strobe_value consists of the Stroberelease, compile date, and PTF level: for example, VERSION(180200.31JAN17.PTF.SGABAS). Db2 versioning provides a mechanism where multiple versions of a program can exist. Therefore, when new DBRMs are received with maintenance, the BINDs should take place prior to copying the corresponding load modules into their appropriate load libraries.
Binding New Db2 Version-Specific StrobeSQL Analysis (SQLAF) Packages
If the PTF received affects an SQLAF program that contains SQL, the PTF will include a new DBRM. Execute the SBDB2UPG job to bind the DBRM into a new StrobeSQL Analysis package for each Db2 subsystem set up to run Strobe. It is not necessary to bind the Strobeplan STRANANA again. StrobeSQL Analysis requires iStrobeand Strobefor Db2.
Binding a New Strobefor Db2/DDF Package
If the PTF received affects a Strobefor Db2 program that contains SQL, the PTF will include a new STRDFIFM DBRM. Execute SBDB2UPG to bind the new STRDFIFM DBRM received to the Db2 subsystems that may be measured. It is not necessary to bind the Strobeplan STRANANA again.
If your