What is the best strategy to apply the required maintenance to Common Services for z/OS r14.1 for compatibility with z/OS 2.3?

Products

• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• 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
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu

Issue/Introduction

When upgrading to z/OS 2.3, it may be necessary to apply upwards of 15 - 20 fixes in order to bring Common Services r14.1 into compliance. What is the recommended procedure to follow to accomplish this upgrade as easily as possible?

• An upgrade to z/OS 2.3 involves applying maintenance to multiple components of Common Services for z/OS r14.1. 
  • Earlier z/OS releases only involved one component, SERVCS FMID CEI0E10
  •  z/OS 2.3 requires maintenance to SERVCS and CAIRIM FMID CAS9E10
• Maintenance can possibly require up to 19 fixes across different components if currently running z/OS release 2.1 or below
• Intent of this article is to provide instructions to accomplish the upgrade most easily

What is the easiest path to follow to upgrade Common Services r14.1 for compatibility with z/OS 2.3 if currently executing in a z/OS 2.1 or earlier environment?

Environment

Common Services r14.1 executing in a z/OS 2.3 environment

Resolution

• Support.broadcom.com provides Compatibility and Lifecycle information for CA Mainframe products
  
  • Includes necessary maintenance for compatibility with different software and selected hardware
• z/OS releases prior to z/OS 2.3 required maintenance to one component/FMID
  
  • SERVCS FMID CEI0E10
• For z/OS 2.3, Common Services r14.1 requires the following maintenance be applied to two components/FMIDs
  
  • CAIRIM FMID CAS9E10
    
    • Necessary maintenance for this component includes
      
      • RO93293
      • RO94935
      • RO95015
  • SERVCS FMID CEI0E10
    
    • Necessary maintenance for this component includes
      
      • RO94936
• Each of these fixes requires one or more prerequisites and/or corequisites
  
  • RO93293
    
    • RO85313 is a prerequisite
  • RO94935
    
    • RO78799 is a prerequisite
    • RO93293 is a prerequisite
    • RO94936 is a corequisite
  • RO94936
    
    • RO73190 is a prerequisite
    • RO94935 is a corequisite
  • RO95015
    
    • RO93293 is a prerequisite
  • Due to corequisite dependencies, RO94935 and RO94936 must be applied together
    
    
• Key to entire set of maintenance above is RO85313 as a prerequisite to RO93293
  
  • Due to corequisite dependencies, RO85313, RO85314, and RO85315 must be applied together
    
    • Each has one or more prerequisites
    • Corequisites of each other
  • CAIRIM FMID CAS9E10
    
    • RO85313
      
      • RO67918 is a prerequisite
      • R085314 is a corequisite
      • RO85315 is a corequisite
  • ENF FMID CAW1E10
    
    • RO85314
      
      • RO75087 is a prerequisite
      • RO85313 is a corequisite
      • RO85315 is a corequisite
  • CCIMVS FMID CAW4E10
    
    • RO85315
    • combination of 9 prerequisites
      
      • various prerequisites themselves have prerequsites
    • best to apply them individually
    • apply in this order
      
      • RO60196
      • RO65568 - RO60196 is a prerequisite
      • RO65223 - RO65568 is a prerequisite
      • RO71715 - RO65568 is a prerequisite
      • RO74389 - RO65568 is a prerequisite
      • RO77749
      • RO79932 - RO77749 is a prerequisite
      • RO80854 - RO74389 is a prerequisite
      • RO82883 - RO74389 is a prerequisite
  • Once completed, apply necessary maintenance for z/OS 2.3 as instructed above

 

Additional Information

Reference the mainframe compatibility matrix available on support.ca.com