CCILGR task does not restart automatically after it is stopped.

Document ID : KB000031790
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

Task CCILGR does not restart automatically after it is stopped. 

The CCILGR/Assured Delivery component monitors conversations between CA Solutions that exist on local and remote host(s) defined to a CAICCI network.  CCILGR stores sent and received data in a VSAM database (LOGGER file) that can be used to verify that data sent from a CA Solution to a specific recipient was successfully received. Some CA Solutions, such as ACF2/CPF, require that CCILGR/Assured Delivery be activated.

There are two methods that can be used to start CCILGR

  • Automatically via ENF by including the LOGGER control option in the CCI Parms (recommended) 
    • The format of the Control Option is  LOGGER(strings,buffer1,buffer2,reorg (either "Y" or "N") with the defaults set to:  LOGGER(20,12,12,N). 
  • Manually by including the LOGGER parms on a z/OS Console Command 
    • The Console Command includes the parms on the command itself, for example: CCI LOGGER(20,12,12,N). 

Despite the fact that the default to the reorg parm is "N", it is recommended to specify "Y" so that the logger database file is reorganized whenever CCILGR is started using either of the above methods.

Sites requiring CCILGR choose to start it automatically through ENF and subsequently stop it on a scheduled basis to recover fragmentation in the LOGGER file that will occur through normal frequent usage. Once the scheduled shutdown is completed, ENF will restart CCILGR automatically.  However, sites that use the ENF automatic startup have experienced problems if CCILGR is shutdown unexpectedly restarted manually with an MVS START command (eg. S CCILGR).

Environment:

CA Common Services for z/OS r14.1 using the CAIENF Component to start CAICCI and CCILGR.

Sites requiring CCILGR choose to start it automatically through ENF and subsequently stop it on a scheduled basis to recover fragmentation in the LOGGER file that will occur through normal frequent usage. Once the scheduled shutdown is completed, ENF will restart CCILGR automatically.  However, sites that use the ENF automatic startup have experienced problems if CCILGR is shutdown unexpectedly restarted manually with an MVS START command (eg. S CCILGR).

Cause:

Although it is a legitimate method of starting the Logger, using an MVS START command to start CCILGR will cause an out of synch condition between the two components and thereby prevent ENF from maintaining control over the CCILGR address space.  This will prevent ENF from automatically starting CCILGR following subsequent scheduled shutdowns.  

Resolution:

To avoid/correct this problem you need to resynch the components.  Rather than use an MVS START command, restart the ENF STC using commands such as:  
                                F ENF,LOGGER(20,12,12,Y)    or    CCI LOGGER(20,12,12,Y) 

Additional Information:

More details of CCILGR/Assured Delivery can be found in: