IV54386: CANNOT DEFINE/OVERRIDE KMS LOG FILE SIZE AND NUMBER.
A fix is available
Closed as program error.
Instructions in the itmc_kms.properties contain the following: # # Users may change the following to set the maximum log # file size and the number of rolling logs # fh.maxFileSize=1000000 fh.maxFiles=3 Changing the value of either or both of the above has no effect. RECREATE INSTRUCTIONS: Try what's described in the problem description and the reported problem will be reproducable.
A workaround provided to the customer was to change the following two configuration values for the KOL (operations log) component from: fh.maxFileSize=1000000 fh.maxFiles=3 to: fh.MaxFileSize=nnnnnnnn fh.MaxFiles=nn The following manifest constants in the KOL component specify an incorrect literal value: #define CCG_PROP_MAX_FILES "MaxFiles" #define CCC_PROP_MAX_FILE_SIZE "MaxFileSize"
Changing the fh.maxFileSize and/or fh.maxFiles parameters in the properties file does not affect the behavior of the operations log (KOL) component of the monitoring server or the portal server.
The MaxFileSize and MaxFiles manifest constants have been changed to maxFileSize and maxFiles respectively to match the documentation. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.3.0-TIV-ITM-FP0003
Change the fh.maxFileSize and fh.maxFiles parameters in the properties file to fh.MaxFileSize and fh.MaxFiles respectively.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels