CA RCS uses excessive CPU, may appear to be in a loop
search cancel

CA RCS uses excessive CPU, may appear to be in a loop


Article ID: 40672


Updated On:


Remote Console



CA Remote Console (RCS) CPU usage increased substantially. In one case, it increased by a factor of 100. RCS may also appear to be in a loop.


The problems you have just experienced are usually indicative of RCS not being able to handle the volume of messages. Usually a message is issued regarding memory, but if the buffer fills rapidly enough it is possible to appear that RCS is in a loop when it is trying to handle a high volume of messages. Given enough time, the buffer should empty. However, if a high volume of messages continues to be forced into the buffers it may never catch up.


Set RCSOPT parms to AREABUFFER=5000 and BUFFSIZE=5000.

The storage is only used as needed.

The change in buffer options is not dynamic. It will take effect the next time that you stop and start the started task for RCS. If you share RCS across environments, you will need to restart each started task.

Also, the values recommended are a starting point and should be defined by the customer based on their environment and storage utilizations.

Additional Information:

This is one reason we advise customers that RCS was intended to catch specific messages to be sent to specific consoles. Not all consoles were meant to receive all the route codes.

Review the Remote Console System Reference Guide for detailed information on these parameters.


Release: PVLRMC00200-2.3-Remote Console