BRMS (5770-BR2) Installation

Information about the BRMS (5770-BR2) installation process.

IBM has withdrawn the marketing of the IBM Backup, Recovery and Media Services for i (5770-BR1) and is offering IBM Backup, Recovery and Media Services for i Subscription Term (5770-BR2) as the available replacement.

5770-BR2 is simplified to contain all functionality from 5770-BR1 under a single option. In addition, 5770-BR2 has several new enhancements that are not included in 5770-BR1, including the new BRMS web interface.

It is recommended to apply BRMS 5770-BR1 PTFs 7.5 SJ01879, 7.4 SJ01877 or the latest BRMS PTFs to improve the migration to 5770-BR2. It is recommended that BRMS PTFs should be applied immediate. The BRMS PTF exit program performs SQL operations which can cause unexpected delays and results if the BRMS PTF is applied delayed at the same time as DB related PTFs.

7.4 Warning: Prior to installing 5770-BR2, you must ensure that PTF SI82606 or the latest are applied on the system where 5770-BR2 is being installed. Related to What's new as of December 2022

Users can migrate from 5770-BR1 to 5770-BR2 by either choosing to apply the latest PTFs (see the information above), saving the QUSRBRM library, deleting 5770-BR1, and install 5770-BR2, or they can choose to skip the latest PTFs, save the QUSRBRM library, migrate the BRMS Functional Usage information, delete 5770-BR1, and install 5770-BR2.

The instructions for both methods are detailed below:

Install steps with recommended PTFs

Save the QUSRBRM library using the command:
- SAVLIB LIB(QUSRBRM) DEV(tape_device) - The save of this library will protect you in the event you need to back off the installation.
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.
Remove the BRMS SQL services to prevent file dependency issues in QUSRBRM using the following command: CALL QBRM/Q1AOLD PARM('INSTALL ' 'RMVSQLSERV' 'N' '00')

SQL can be used to potentially find user created files in QUSRBRM:

select * from table(qsys2.object_statistics('QUSRBRM', 'FILE')) x where OBJOWNER <> 'QBRMS'

Delete product 5770-BR1

Product 5770-BR2 cannot be installed with product 5770-BR1 already installed. You must delete product 5770-BR1 and all its options using option 12 on the GO LICPGM menu or using the DLTLICPGM LICPGM(5770BR1) OPTION(*ALL) command.

QUSRBRM is not removed when the product is deleted, do not delete library QUSRBRM.

Install product 5770-BR2
Apply the latest BRMS PTFs

Install steps without recommended PTFs

Save the QUSRBRM library using the command:
- SAVLIB LIB(QUSRBRM) DEV(tape_device) - The save of this library will protect you in the event you need to back off the installation.
Migrate BRMS Functional Usage Information. The usage information for an individual function is saved with the user profile's private authorities using the command:
- SAVSECDTA DEV(tape_device)
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.
Remove the BRMS SQL services to prevent file dependency issues in QUSRBRM using the following command: CALL QBRM/Q1AOLD PARM('INSTALL ' 'RMVSQLSERV' 'N' '00')