Troubleshooting
Problem
BRMS creates files in /tmp/brms that can be used by service personnel when diagnosing problems with BRMS. In the current design, when these files reach a size of 10 MB, they are renamed to *.bku and a new file is created. When the new file reaches 10 MB, the *.BKU file is deleted, and the original file is renamed to *.bku. It is not possible to prevent these files from being created.
Resolving The Problem
BRMS creates files in /tmp/brms that can be used by service personnel when diagnosing problems with BRMS.
In the current design, when these files reach a size of 10 MB, they are renamed to *.bku and a new file is created. When the new file reaches 10 MB, the *.BKU file is deleted, and the original file is renamed to *.bku. It is not possible to prevent these files from being created.
To delete these files, consider the following:
A list of the files that may be in /tmp/brms are:
Notes:
In the current design, when these files reach a size of 10 MB, they are renamed to *.bku and a new file is created. When the new file reaches 10 MB, the *.BKU file is deleted, and the original file is renamed to *.bku. It is not possible to prevent these files from being created.
To delete these files, consider the following:
| o | They will be created when required by BRMS. |
| o | If a problem occurs in BRMS, it may be difficult for service personnel to diagnose the problem without these files. |
| /tmp/brms/flightrec | Current BRMS flight recorders of the most current BRMS activity on the system. |
| /tmp/brms/flightrec.bku | Backup of the last /tmp/brms/flightrec. |
| /tmp/brms/brms | Current BRMS flight recorder of all BRMS activity done with the user profile QBRMS (media synchronization, networking, and so on). |
| /tmp/brms/brms.bku | Backup of the last /tmp/brms/brms.bku. |
| /tmp/brms/performance | Current BRMS flight recorder data used to help determine how long different options of BRMS took (saves, outfile processing, and maintenance). |
| /tmp/brms/performance.bku | Backup of the last /tmp/brms/performance. |
| /tmp/brms/install | Current BRMS flight recorders about the last installation of BRMS, upgrade, or PTF installation. |
| /tmp/brms/install.bku | Backup of the last /tmp/brms/install. |
| /tmp/brms/dmpbrm | A listing of all the DMPBRM commands run. It can be used to determine the save file used by the command to save the BRMS flight recorders. |
| /tmp/brms/assert | A snapshot of the BRMS flight recorders taken by BRMS when a serious BRMS save fails. |
| /tmp/brms/assert.bku | Backup of the last /tmp/brms/assert. |
| tmp/brms/diary | Current BRMS flight recorder that records only key events so that we can get a view of what happened on the system over an extended period of time. |
| /tmp/brms/diary.bku | Backup of last /tmp/brms/diary file. |
| /tmp/brms/tapetms | Current BRMS flight recorder containing only media management information. |
| /tmp/brms/tapetms.bku /tmp/brms/enterpriseFr |
Backup of last /tmp/brms/tapetms file. If customer is using BRMS Enterprise this file gets created and is used for troubleshooting. |
Notes:
- QBRMS user profile should not be used for backups or normal BRMS operations.
- BRMS functions that run using profile QBRMS, in other words, QBRMSYNC, backups, STRMNTBRM, and so on, will not be in the normal flightrec, but in the qbrms one.
- For customers that have the March 2020 BRMS PTF installed you will find the data listed above in folder /QIBM/UserData/BRMS/logs/ instead of /tmp/brms/.
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]
Historical Number
324767376
Was this topic helpful?
Document Information
Modified date:
18 March 2020
UID
nas8N1016297