ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How do I know if the CAICCI SPAWN facility is being used?

book

Article ID: 187002

calendar_today

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

How to verify if CCITCP spawn facility is actively used on our LPARS. The CCITCP task is started by CAIENF.

Not sure if this is still used everywhere. How to verify it on lpars? Any commands, parameters of some products what may utilize CCITCP spawn facility.

Environment

Release : 14.1
Release : 15.0

Component : CCIMVS - CA COMMON COMMUNICATIONS

Resolution

The CCITCP and CCI Spawn service are independent of each other.
 
There are no commands that can be used to determine usage.
 
"Internal" CCI Spawn
 
The CCI Subsystem that initializes within the ENF address space can invoke an internal spawn request to start related services such as CCITCP/CCISSL or CCITCPGW/CCISSLGW.

For example, if the PROTOCOL(TCPIP) statement is defined in CCIPARMS then a CCI Spawn request will be issued to start the CCITCP (or other) address space.
 
The start of any of these CCI* tasks will be shown in the ENF joblog.

It is recommended that the CCITCP (and other similar tasks) address space be managed by ENF. The presence of the mentioned PROTOCOL statement  will result in ENF starting CCITCP.

If ENF terminates, the CCITCP task will also terminate.

If CCITCP abends or is stopped (eg. P CCITCP) the ENF task will restart CCITCP in most all situations.

While not recommended, the CCITCP/CCISSL address space can be manually started. However, this same potential is not advised for the CCITCPGW/CCISSLGW address space.
 
"External" CCI Spawn
 
There is also the CAICCI Spawn service that is available and makes use of a CCISPAWN DD in the ENF proc.
 
The CCISPAWN DD points to a member in the CAW0OPTN (or equivalent) dataset containing spawn parms.
 
Spawn parms are provided by the CA Mainframe Product that is going to use this service.
 
If spawn parms are defined, active usage would be witnessed by seeing messages in the ENF joblog showing tasks being started. The tasks would correlate to the PROCNAME defined in spawn parms.

Additional Information

CA Common Services for z/OS - TCP/IP Configurations