SMP/e Basics – Installation steps for CA Database Management

Solutions for IMS R14

By Ajay Sharma, Kushal K Brahma, Saaikrishnan P.S.

Agenda• Introduction to IBM tools and ISVs• Brief introduction to CA Database Management Solutions• Brief introduction to CA Database Copier• CA website – Acquiring the product• What is SMP/e?• SMP/e Terminologies• Receive, Apply and Accept (concept of SMP/e zones)• SMP/e datasets• SMP/e HOLDs• SMP/e MCS statements• Miscellaneous• SMP/e environment in AVIVA.

Introduction• In IMS, IBM has provided some standard default backup utilities to make

backup copies of a database, DEDB area, or HALDB partition. E.g. – DFSUDMP0 - Image Copy Utility (Copies from memory dump)– DFSUDMT0 - Image Copy 2 Utility (Uses functions fo DFSMS)– DFSUICP0 - Online Image Copy Utility

• With enterprise level backup of databases being more important by the day, IBM and other ISV (Independent Software Vendors) built on the above mentioned utilities to create optimized backup utilities, which improves productivity and have minimal effects to the running system. Some major tools with enhanced backup capabilities are:-

– IBM High Performance Image Copy Utility– BMC Image Copy Plus– CA Database Copier– NEON Eclipse Backup and Recovery Utilities

CA Database Management Solutions

• The CA Database Management Solutions for IMS for z/OS provide power and flexibility for optimal performance, efficient database administration, reliable backup and recovery, and IMS TM management. These interoperable, practical products improve service levels, data availability, and application responsiveness across IMS for z/OS.

• CA Database Management Solutions is a collection of 6 utilities which provide a complete database management capability to the user. These utilities include:-

– CA Database Analyzer for IMS for z/OS– CA Database Organizer for IMS for z/OS– CA Database Copier for IMS for z/OS– CA High Performance Recovery for IMS for z/OS– CA Secondary Index Builder for IMS for z/OS– CA Secondary Index for IMS for z/OS

CA Database Copier• CA Database Copier provides streamlined processes for creating

timely, current image copies of your IMS data—without impacting information availability or draining critical system resources. In this way, CA Database Copier helps you effectively back up your IMS data and maximize the value and performance of your IMS personnel—while making image copies a core component of your enterprise’s overall backup and recovery strategy.

• With a wide range of flexible image copy capabilities, CA Database Copier helps you create comprehensive, timely backups of the data residing in your IMS environment. Specifically, the product helps you:

– Optimize backup performance without taxing IMS resources– Improve the productivity of your IMS management and administration personnel– Create backups with minimal impact on data availability.

CA Website• You can log in to https://support.ca.com to acquire a product or any product

related information, including corrective fixes (PTF/APAR), product documents and raising support requests.

• You can enter the site with you CA login ID (your email ID) and password. – Note: You would require your organizations site ID to be able to see the list of

software's and materials licensed for your organization.• Under the “Support” section go to the “Download Center” and then click on

“Products”.• In the following screen enter the name of the product you want to download,

select the release and gen level and hit “Go”.• Custom build the package you want to download by selecting the products

you want and then click on “View Download Cart” to download the products you selected.

• You can download the product via CA Download Manager, IE default downloader or request for a FTP download.

– Note: Use FTP to directly download the pax files to your z/OS unix environment or you would have to upload the file to the system unix path.

SMP/e• System Modification Program Extended (SMP/e) is used to install and

maintain software on your z/OS system. • It enforces the list of fixes required to be present are either available or

already installed. • It prevents back-leveling user changes applied with a USERMOD.• It maintains a log you can use as an audit trail, plus changes are

timestamped should you decide to use the online query tool.• ISPF based queries or batch jobs can list specific information about the

objects maintained by SMP/E.• SMP/E is an integral part of the installation, service, and maintenance

processes for z/OS and OS/390 software products and product packages, such as CBPDO, ProductPac, RefreshPac, and selective follow-on service for CustomPac. In addition, SMP/E can be used to install and service any

software that is packaged in SMP/E system modification (SYSMOD) format.

SMP/e Terminologies• APAR (authorized program analysis report) • CSI (consolidated software inventory)• CBPDO (custom built product delivery option)• DDDEF (Dynamic Dataset Definition)• FMID (Function SYSMOD)• LMOD (Load module)• MCS (Modification control statements) • NPRE (Negative Pre-REQuisite)• PTF (program temporary fix) • PTS (PTF temporary store)• RMID (Replacement Modification Identifier)• SYSMOD (system modification) • USERMOD (user modification) • UCLIN (SMP/E control statement)• UMID (Update Modification Identifier)

Concept of SMP/e zones• SMP/E works with three major components: GLOBAL, TARGET, and DLIB.• The GLOBAL component maintains high level information about the products

installed in target zones, maintenance for those products, and information about the zones. It is a staging area for products and fixes before they are applied.

• The TARGET component is comprised of a handful of SMP/E data sets and the product specific data sets. These data sets are the ones you use with the product.

• The DLIB component houses a backout version of code. For some products, like IMS, at least one is required to "gen" the run-time parameters. Keep this in mind when you plan for disaster recovery!

SMP/e commands and what they do?• Receive - makes known to the GLOBAL CSI.• – Similar to unzipping a pc based program and “cab” files that are used to install a

product.• Apply - makes known to the TARGET CSI.• – Builds and copies the elements used to run the product.• Accept - makes known to the DISTRIBUTION CSI.• – Copies elements to the backup libraries.• Reject - tells the GLOBAL zone to forget about it.• Restore - Rebuilds the Target version from what has been accepted. Similar to ctrl-z

or “undo”.

SMP/e datasets• Apart from the standard TLIB (target libraries) and DLIB (distribution libraries) which

are product specific and are used to run the products. We need to maintain some SMP/e related datasets as well. These datasets are:-

• SMPCSI (CSI) data sets are VSAM KSDS data sets used to control the installation process and record the results of processing. A CSI can be divided into multiple partitions through the VSAM key structure. Each partition is referred to as a zone.

• An SMPPTS (PTS) data set is a data set for temporary storage of SYSMODs waiting to be installed.

• The SMPSCDS (SCDS) data set contains backup copies of target zone entries modified during APPLY processing.

• The SMPMTS (MTS) data set is a library in which SMP/E stores copies of macros during installation when no other target macro library is identified.

• The SMPSTS (STS) data set is a library in which SMP/E stores copies of source during installation when no other target source library is identified.

• The SMPLTS (LTS) data set is a library that maintains the base version of a load module.

• The SMPTLIB data sets (TLIBs) are used as temporary storage for relative files that are loaded from SMPPTFIN during RECEIVE processing.

• SMPPTFIN – Contains the MCS provided by the vendor.• SMPHOLD – Contains the HOLDs relating to specific SYSMODs.

SMP/e HOLDsWhen you apply maintenance, you normally encounter SMP/E hold data. HOLDs are used to control the dependencies of SYSMOD, so that a specifictask is carried out before the modification statements can be implemented for aproduct set. Some types of common holds that you may encounter are:-• ACTION - You must perform special processing either before or after you apply this

sysmod.• BIND (DB2 only) – The associated plan or package should be rebinded after this fix is

applied• DEP - This sysmod has a dependency that you must externally verify.• DELETE - This sysmod deletes a load module. You cannot reverse this type of

sysmod with the SMP/E RESTORE command.• DOC - There is a documentation change with this sysmod.• ENH – This implies that the hold is an enhancement to an existing feature.• ERROR - This implies that the associated SYSMOD is in error. These type of

maintenance cannot be applied unless the fix is avaialbale and is applied along with the concerned fix.

• IPL - This means that the z/OS system should be IPLed to apply this maintenance.

SMP/e MCS statementsEach SYSMOD processed by SMP/E is composed of two distinct types of data: instructions to SMP/E identifying the elements in the SYSMOD and how to install them, and the actual element replacements or updates. The instructions to SMP/E consist of a series of control statements, called modification control statements (or MCSs).• Header

++FUNCTION++PTF++APAR++USERMOD

• ++VERSREL – System Release Identifier – Z038FMIDPRE, SUP and REQ

• ++HOLD – action required• ++JCLIN – how target libraries are built• ++MAC / ++MACUPD• ++MOD / ++ZAP• ++SRC / ++SRCUPD• ++HFS• ++JAR / ++JARUPD• ++PROGRAM

MiscellaneousSMP/e can be invoked through batch or an interactive ISPF panel

DDDEFThe DDDEF entry contains the information SMP/E needs to dynamically allocate a specific data set. With DDDEF entries, you do not have to provide a DD statement for every data set SMP/E may need to process a particular command. When SMP/E determines that it needs a specific data set, it looks for a DD statement that it can use to allocate that data set. If there is no DD statement, SMP/E checks whether the current zone contains a DDDEF entry for that data set. If so, it uses the information in the DDDEF entry to dynamically allocate the data set. To list the DDDEF entries use the command:-SET BDY(TZN) /* Set to requested target. */.LIST DDDEF /* List all DDDEF entries. */.

Utility usedThe utility used to invoke SMP/e in a batch job is GIMSMP (e.g. PGM=GIMSMP)

Defining zonesTo define which zone a specific modification statement has to work with we enter the following UCLIN command :– SET BOUNDRY (GLOBAL) . /* for global zone; a period “.” is used as continuation statement */

Other common UCLIN statements:BYPASS (HOLDSYS) /* to bypass all the holds ; excpet ERRHOLD */SELECT (sysmod-name) /* Select specific sysmod from the list */EXCLUDE (sysmod-name) /* EXCLUDE specific hold */GROUPEXTEND /* includes requisites and supersedes */

SMP/e in AVIVA