CA CIS, CA Common Services for z/OS, CA 90s Services, CA Database Management Solutions for DB2 for z/OS, CA Common Product Services Component, CA Common Services, CA ecoMeter Server Component FOC, CA Easytrieve Report Generator for Common Services, CA Infocai Maintenance, CA IPC, Unicenter CA-JCLCheck Common Component, CA LDAP Server for z/OS, CA Mainframe VM Product Manager, CA Chorus Software Manager, CA On Demand Portal, CA Service Desk Manager - Unified Self Service, CA PAM Client for Linux for zSeries, CA Mainframe Connector for Linux on System z, CA Graphical Management Interface, CA Web Administrator for Top Secret, CA CA- Xpertware, MF - MISC OLD CODES, SERVICE ASSURE, Generic Uniservice for CICS, Generic Uniservice II, CA Output Management Web Viewer
In a position to get CCS 14.1 PTF SO08282 or CCS 15.0 PTF SO08287 installed for a z/OS 2.4 roll out. What are implications if PTF is not installed?
Release : 14.1 Release : 15.0
Component : CAICCI-MVS
These PTFs address a problem that was identified during internal z/OS 2.4 validation and are specific to CAICCI and CCI Component Tracing.
The potential for a problem would only exist with the CCICT statement in the CCI parameter file. CCICT controls the Component Trace environment.
With CCICT specified, an attempt is made to create a dataspace as part of CCI initialization. It's the creation of the dataspace that fails and results in the hang.
Note: By default this statement is delivered as a comment.
With CCICT defined and without PTF SO08282 or SO08287, CCI initialization within the CA-ENF address space basically stalls.
The last message seen in ENF joblog would be "CAS9603I - WAITING FOR SRB TO COMPLETE".
The message "CAS9626I - CAICCI Subsystem is operational", which indicates that CCI initialization has completed successfully would not be generated.
As a result, the CCI address spaces (eg. CCILGR,CCITCP,CCITCPGW,etc...) may not be automatically started (if configured to do so).
Finally, any CCI calls from CA-products would result in a RC=4