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.