KBB_RAS1_LOG and Universal Agent

The Universal Agent log file keeps growing more and more because the agent does not switch
between multiple log files when maximum size is reached.
Furthermore, the file name does not have the usual suffix indicating the log file number.

It looks like :
<hostname>_um_1359739336.log

instead of the expected

<hostname>_um_kuma620_50e41a60-01.log

Universal Agent configuration file, um.ini, by default does not include the keyword
KBB_RAS1_LOG, that is instead present for all the other ITM Agents.

Sometime, for troubleshooting purpose, IBM support can ask you to add KBB_RAS_LOG into um.ini,
in example to increase the number of generated log files (COUNT option) or the maximum file size (LIMIT option):

KBB_RAS1_LOG=%(CTIRA_LOG_PATH)/$RUNNINGHOSTNAME$_$PRODUCTCODE$_%(systask
)_%(sysutcstart)-.log
INVENTORY=%(CTIRA_LOG_PATH)/$RUNNINGHOSTNAME$_$PRODUCTCODE$_%(systask).i
nv COUNT=15 LIMIT=50 PRESERVE=1 MAXFILES=20

In this line, KBB_RAS1_LOG is populated with the content of some variables, like RUNNINGHOSTNAME, systask or sysutcstart.
During startup, the agent must resolve these variables to build the string that is passed to the KBB_RAS1_LOG, but it must know the character that is used as "variable prefix".
When adding KBB_RAS1_LOG to um.ini you must also include another keyword that
is indeed already present by default in all the other ITM Agents configuration file:
KBB_VARPREFIX=%

Using this keyword into the um.ini file, the variables will be correctly resolved and Universal Agent will use the ITM RAS1 log files as expected, switching to the next file when the maximum size is reached and wrapping when the maximum number of log files is reached.

Add KBB_VARPREFIX=% keyword into um.ini file before the KBB_RAS1_LOG keyword and restart
the agent