Single CSI

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

We are planning to have Single SMPE CSI for all below products. Which means we will have single global ,Target & Dlib zone. in other words all FMIDS will be in one zone for all products.
 

We are planning to have Single SMPE CSI for all below products. Which means we will have single global ,Target & Dlib zone. in other words all FMIDS will be in one zone for all products. CA Common services CA7 CA OPS MVS CA 1 CA Dispatch CA Eastrieve CA JCl Check CA Spool Compress/MVS2 Will this be an issue.

Environment

z/OS

Resolution

We always recommend CA COMMON SERVICES be installed into separate SMP/E libraries. We recommended to keep CCS390 separate and allow easier fallback to a previous release if necessary. CA COMMON SERVICES has a huge impact on a system processing, because every CA Solution depends on it
In addition, what if something goes wrong with a product, and compromises the entire CSI.
CA COMMON SERVICES must always be kept intact.