Explanation of SMP/E HOLDDATA processing via CA Mainframe Software Manager.

Products

• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu
• Datacom
• DATACOM - AD
• RC Compare for DB2 for z/OS
• Bind Analyzer for DB2 for z/OS
• SQL-Ease for DB2 for z/OS
• SYSVIEW Performance Management Option for DB2 for z/OS
• Plan Analyzer for DB2 for z/OS
• Subsystem Analyzer for DB2 for z/OS
• Database Analyzer for DB2 for z/OS
• Fast Unload for DB2 for z/OS
• Fast Check for DB2 for z/OS
• Fast Index for DB2 for z/OS
• Rapid Reorg for DB2 for z/OS
• Endevor
• Endevor Natural Integration
• Endevor - ECLIPSE Plugin
• Endevor - Enterprise Workbench
• Mainframe Software Manager (Chorus Software Manager)
• MICS Resource Management
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Description:

What process does CA Mainframe Software Manager use to acquire and process SMP/E HOLDDATA?

Solution:

The 2 types of HOLDDATA used in CA SMP/E processing are SYSTEM and ERROR.

HOLDDATA (SYSTEM) is generated, at PTF creation, when special processing is required before or after the SYSMOD is applied. For example, this type of HOLDDATA will tell when to rebind the DB2 packages or bounce a started task. CA Mainframe Software Manager will display this HOLDDATA during the maintenance process.

HOLDDATA (ERROR) is generated when a problem is found with an existing PTF that is no longer suitable for installation (apply). This HOLDDATA cannot appear within a PTF and is placed into an external file. For example, we would place a PTF in error if it causes data corruption or DB2 to abend. When a PTF is placed in error, the original PTF is modified to include an external ".TXT" file that contains the HOLDDATA information. You can acquire this HOLDDATA when downloading a Published Solution or PTF Bucket from Support.ca.com.

Currently, CA Mainframe Software Manager 2.0 is unable to acquire and receive HOLDDATA (ERROR) and you will need to go outside of MSM to download the product's HOLDDATA from the Detailed Service Pack Information Page for the given set of tools found on Support.ca.com. An example for DB2 Tools is found here:
https://support.ca.com/irj/portal/anonymous/phpdocs?filePath=7/1201/1201_dspi_mainframe.html.

Sample holddata may look like this:

++HOLD (UPAF199) ERROR  FMID(APPA115)
  REASON(HPAF001) DATE(06334)  CLASS(PE)
  COMMENT(Problem PBA-47:  STATUS OF PTF UBAF037 IN ERROR.
      PE PTF is resolved by UPAF224).

You will then need to perform the SMP/E RECEIVE of the HOLDDATA outside the scope of the CA Mainframe Software Manager product via native SMP/E JCL. Once the HOLDDATA has been received into the product's SMP/E GLOBAL zone, CA Mainframe Software Manager can then be used to perform the SMP/E APPLY of the PTF maintenance. MSM will not provide special handling to EXCLUDE or BYPASS "Hold Errors", thus any unresolved error holds will not be applied. The SMP/E output displayed by MSM will indicate each PTF that did not apply due to unresolved error holds.

Environment

Release:
Component: MSM