The files are limited in size: when DTstatus.out is full, Blueworx Voice Response copies it and identifies the copy as a history file by appending the date and time as a file extension. For example:
DTstatus.out.Jan01.8:15:34
Blueworx Voice Response then initializes the original file and continues to write data to it.
Only three versions of DTstatus.out history files are kept. When the fourth one is created, the earliest one is deleted.
You must never try to free space by removing the current DTstatus.out file. Blueworx Voice Response cannot operate correctly without it.
dtalarmd.out is primarily for use by the IBM support center. It can be deleted when Blueworx Voice Response is not running.
When oamtrace or errorlog is full, new entries wrap around, overwriting the entries that are already there. This is particularly important for oamtrace, and it ensures that you get the most recent trace entries. The maximum size of the errorlog before wraparound occurs is specified by the Errorlog Wrap Threshold system parameter in the Application Server Interface group.
To set this parameter, click Configuration —> System Configuration —> Change —> Application Server Interface —> Errorlog Wrap Threshold. (For more information, see the Configuring the System information, or the online help for the parameter.)
Daily at midnight and each time you restart Blueworx Voice Response, each oamtrace and errorlog is copied, the copy being identified as a history file by the date and time appended to the name. For example, if you restart Blueworx Voice Response on January 1, at 7 in the morning, the history files will be named:
errorlog.Jan01.7:00:00
oamtrace.Jan01.7:00:00
Blueworx Voice Response then initializes the original files and continues to write entries in them.
Managing the oamtrace and errorlog history files is important, because otherwise they can eventually fill up the hard disk.
You must never try to free space by removing the current errorlog or oamtrace files. Blueworx Voice Response cannot operate correctly without them.
To manage disk space, you can use the log management utility (dt.log_mgr) to rationalize the errorlog or oamtrace history files by merging, compressing, grouping, or deleting the files. The utility operates on history files closed before the current date, including any previously rationalized sets of files. You can choose to process either oamtrace or errorlog files, or both.
How often you need to run dt.log_mgr depends on how often you restart the system. You can run it at any time, for instance, at the end of the working day, or at weekly or monthly intervals. Typically the file space saving is around 80% if deletion and compression are selected.
Although you can run dt.log_mgr from the command line, you can also schedule it to run on a regular basis by including it in the $SYS_DIR/report_schedule file (see Scheduling tasks to happen regularly).
The dt.log_mgr utility is supplied in the $VAE/tools/ directory.
To process both oamtrace and errorlog files, type on the AIX command line:
dt.log_mgr
To process only oamtrace files, type:
dt.log_mgr -d oamtrace
To process only errorlog files, type:
dt.log_mgr -d errorlog
By default, with no flags, dt.log_mgr will delete all errorlog and oamlog files that are prior to the current and preceding month, before continuing with merge, compress, group, and delete, as follows:
Selects the last oamtrace file closed on each date, for retention.
To avoid the merge of errorlog files and selection of the last oamtrace file, use the -M flag:
dt.log_mgr -M
To avoid the compression, use the -z flag:
dt.log_mgr -z
To avoid grouping, use the -S flag:
dt.log_mgr -S
To keep all empty and oamtrace files, use the -k flag:
dt.log_mgr -k