Details regarding PTF SO08282 or SO08287.
Article ID: 145093
Updated On:
Products
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
LDAP SERVER FOR Z/OS
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
MF - MISC OLD CODES
SERVICE ASSURE
GENERIC UNISERVICE FOR CICS
GENERIC UNISERVICE II
Output Management Web Viewer
Issue/Introduction
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?
Environment
Release : 14.1
Release : 15.0
Component : CAICCI-MVS
Resolution
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
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
Additional Information
Feedback
Yes
No
Powered by
