Backup Recovery and Media Services (5770-BR1)

Start of change

Prior to upgrading BRMS

It is important to ensure no user-created dependencies exist on BRMS files in QUSRBRM before upgrading BRMS. Use Display Database Relations (DSPDBR) on all physical and logical files in QUSRBRM to ensure only IBM® BRMS files are listed. If any other non-IBM dependencies exits, they need to be removed before starting an upgrade.

SQL can be used to potentially find user created files in QUSRBRM:
select * from table(qsys2.object_statistics('QUSRBRM', 'FILE')) x where OBJOWNER <> 'QBRMS';

If using OUTPUT(*OUTFILE) on any BRMS commands, it is recommended that the current outfiles be deleted prior to upgrading or after upgrading to a new release. Changes to files may have occurred and new fields added or changed.

Prior to upgrade, check parameters in BRMS (e.g. target release in control group attributes) if they contain values which may become invalid in the higher release.

If a data area is still used and supported, check 'Data Areas Used in BRMS' at

It is important to ensure that no temporary PTF objects exist in library QBRM before upgrading BRMS. All BRMS PTFs must be permanently applied before the upgrade using the following command:
End of change

WRKMEDBRM Select volumes (TYPE)

The Work with Media using BRM (WRKMEDBRM) parameter Select volumes(TYPE) special value *BOTH has been removed and is replaced by special value *ALL.

BRMS database

The default for the BRMS shipped database is changing from *PUBLIC *USE authority to *PUBLIC *EXCLUDE.

BRMS functional usage model

The default authority for BRMS shipped functional usage is changing from default authority *ALLOWED to *DENIED. Use the Set User Usage for BRM (SETUSRBRM) command as a starting point to grant system operators and administrators access to BRMS functions and components. Then use the functional usage model to customize access by user.

BRMS flight recording

The data authority for BRMS shipped flight recording is changing from data authority *RWX to *WX.

SAVBRM command default change

The default for the Save Object using BRM (SAVBRM) command parameter Asynchronous bring (ASYNCBRING) is changing from *NO to *YES to match the Save Object (SAV) command default.

Backup Policy change

The Work with Policies using BRM (WRKPCYBRM) TYPE(*BKU) default value for Asynchronous bring is changing from *NO to *YES to match the Save Object (SAV) command.

Navigating to the BRMS graphical interface

The BRMS component of IBM Navigator for i is used to help you implement a disciplined approach to managing your backups, and provides you with an orderly way to recover lost or damaged data. A new implementation of IBM Navigator for i is included with IBM i 7.5. However, the BRMS component is not available in this Navigator at this time. Keep looking at this space for additional information.

Start of change

Initialize BRMS graphical interface

The Initialize BRMS (INZBRM) command parameter OPTION(*SECUREDDM) with ACTION(*SET) has been disabled and will fail with message BRM412B. BRMS encourages using the alternate method of implementing the Add Server Authentication Entry (ADDSVRAUTE) command parameter SERVER(QDDMDRDASERVER).

End of change
Start of change


The Work with Media Policies (WRKPCYBRM *MED) command interface to create or change a media policy with a Media Class special value of *ADSM has been disabled and will fail with message BRM1174.

End of change