The Automation product will start the CICSLOGR task when CICS is restarted.
The command is: START CICSLOGR.taskID
If there is no reply to the command within a set time period whilst the region is starting then the Automation routine should repeat the command a 2nd time, then again wait for the reply.
If there’s still no reply then a warning message will be issued.
Is there any problem to issue the start command of CICSLOGR task several times?
Reissuing the command while the logger task is already active would not cause any problems.
It's possible to see the below message in the log:
GSVX586E (MAIN) START CICSLOGR.taskID invalid, task is already active
Information about the process to start the CICSLOGR may be found at: