Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

BRMS 7.2 and later versions will no longer write the flight recorder data to the /tmp/brms directory. The flight recorder data is written to the /QIBM/UserData/BRMS/logs directory. This is to comply with IBM i data guidelines.

Because of this change it will be necessary to migrate BRMS-managed virtual tape and optical images from /tmp/brms/userData/cloud to the directory /QIBM/UserData/BRMS/cloud. Some considerations for this move include:

  • This migration process will occur during a BRMS maintenance operation. After applying the March 2020 BRMS PTF, maintenance should be run to perform this migration. 

  • The migration process may increase the time for the maintenance dependent upon the number and the sizes of BRMS-managed image catalogs and virtual volumes that exist. 
    Note: due to the nature of migrating the image files, users that want to implement CLRTMP processing to clear the /tmp directory at system startup should wait to do so until the March 2020 BRMS PTF has been applied *PERM.

  • Also, in the event that BRMS images are stored in the /tmp/brms/userData/cloud directory for an existing image catalog and the BRMS settings have been changed to write new virtual volumes to an IASP that is varied off, the migration process will fail and BRMS maintenance will end with the error message BRM3D1C. This issue can be resolved by varying on the independent ASP and running maintenance again.

  • No labels