Start persistent local recording
The user can select the type of persistent local binary or nmon recording.
To start respective recording, select binary or nmon on the Type of Persistent Recording menu:
Type of Persistent Recording
Move cursor to desired item and press Enter.
binary
nmon
F1=Help F2=Refresh F3=Cancel
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
Type of Recording binary
Length of Recording persistent
Recording Interval in seconds [300]
* Number of Days to store per file [1]
* Number of Days to retain [7]
Output Path []
* Overwrite existing recording file no
* Enable WLE no
* Include Disk Basic Metrics [Yes/No]
* Include Service Time Metrics [Yes/No]
* Include Disk Adapter Basic Metrics [Yes/No]
* Include Disk Adapter Service Time Metrics [Yes/No]
* Enable Filesystem Threshold [Yes/No]
Minimum Percentage []
Maximum Percentage []
The recording interval (in seconds) should be a multiple of 60. If the recording type is local binary recording, then the user has an option to enable the IBM Workload Estimator (WLE) report generation in the SMIT screen. The WLE report is generated only on Sundays at 00:45 a.m. and requires local binary recording to always be enabled for consistent data in the report. The data in the weekly report is correct only if the local recordings are always enabled.
The generated WLE report is stored in the /etc/perf/<hostname>_aixwle_weekly.xml file. For example, if the hostname is ptoolsl1, the weekly report is written to the /etc/perf/ptoolsl1_aixwle_weekly.xml file.
If the filesystem threshold is enabled, the topasrec command pauses the recording when the file system used space crosses the maximum percentage of the specified filesystem threshold. It will then write an error log entry. The topasrec command resumes the recording when the file system used space goes back to less than the minimum percentage of the file system threshold.
For additional information, refer to: