CA Remote Console using more CPU than expected?

Products

• Remote Console

Issue/Introduction

In today's high-powered operating systems and fully utilized processors, some product settings should be reviewed within CA Remote Console to affect more efficient CPU utilization.

How can we adjust CA Remote Console to reduce CPU usage?

Environment

z/OS

Resolution

If CPU utilization starts to rise and you notice the cause might be CA Remote Console, the most often cause is buffering. Since processor activity is much faster and more heavily utilized on today's systems the old recommended defaults for CA Remote Console may not be sufficient.

A simple recommendation for your initialization parameters can be similar to this:

MBUFFS=3010                                   ---> default is 1010 
AREABUFFER=500                              ---> Max is 5000 and default is 150
BUFFSIZE=300                                  --> default is 200                              

The AREABUFFER value should be higher to handle the MBUFFS value you have specified. 
When you update the MBUFFS value you must update / increase the AREABUFFER and BUFFSIZE values.

The RCS subsystem will use storage allocated to buffer the messages and begin routing the messages to the consoles. When a lot of messages are produced, as in the new environments, the buffers can use more storage but if you limit the buffers you could see the following error messages:

RCS5180 WARNBUFF LIMIT EXCEEDED, UTILIZATION IS AT nnn PERCENT

 

 

 

 

 

Additional Information

Please review these options in the CA Remote Console Reference Guide and User Guide.