Protection against oversized SYSLOG file

If you are maintaining the SYSLOG as an FGG, you can control the amount of storage space occupied by the SYSLOG by permitting a maximum of n file generations for the FGG (number parameter of the KDCSLOG tool) and by activating automatic size monitoring. See also section “Automatic size monitoring”.

The file generations of the SYSLOG are cyclically overwritten so that the FGG contains a maximum of n file generations. With size monitoring, each generation has a maximum of size UTM pages.

The maximum space requirement of the SYSLOG-FGG is thus calculated by:

n * size * (size of a UTM page).