How to start CCILGR STC?


Article ID: 38334


Updated On:


CA ACF2 CA ACF2 - DB2 Option CA ACF2 for zVM CA ACF2 - z/OS CA ACF2 - MISC 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 Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component 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 CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA PanApt CA PanAudit



How is the CCILGR STC started?



The CCILGR procedure gets started by CA-ENF with the presence of the LOGGER control statement defined in the CCI parameter file (eg. CCIPARMS).

When ENF starts and encounters the LOGGER statement, an internal CCI spawn service is invoked to start the CCILGR task.

Subsequently, when CA-ENF terminates it will shutdown (cancel) the CCILGR task. If the CCILGR task is stopped (eg. P CCILGR), it will automatically get restarted by CA-ENF. If for some reason the CCILGR task is not restarted automatically, it is recommended that it be restarted using ENF command: F ENF,LOGGER

If you don't want the CCILGR procedure to start, comment or remove the LOGGER statement from the CCI parameter file.

If the CCILGR task is already running and you want to shut it down and not restart, CANCEL the task. 


Additional Information:

You can check the CA Common Services r14.1 Administration Guide for information about CCILGR.


Documentation Wiki:


Release: ACF2..001AO-15-ACF2