Prior to upgrading BRMS

Some customer interventions may be required for a successful upgrade.

Prior to upgrading BRMS from IBM i 7.4 or IBM i 7.5 with 5770-BR1

It is important to have the following 5770-BR1 PTFs applied to improve the upgrade to 5770-BR2:
- BRMS 5770-BR1 PTFs IBM i 7.5 - SJ01879 , IBM i 7.4 - SJ01877
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.
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.

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'
If using OUTPUT(*OUTFILE) on any BRMS commands, it is recommended that the current outfiles are 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, please check parameters in BRMS (e.g. target release in control group attributes) if they contain values which may become invalid in the higher release.
Also please check 'Data Areas Used in BRMS' if a data area is still used and supported.

Prior to upgrading BRMS with existing 5770-BR2

It is important to ensure 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:
- APYPTF LICPGM(5770BR2) SELECT(*ALL) APY(*PERM)
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'
If using OUTPUT(*OUTFILE) on any BRMS commands, it is recommended that the current outfiles are 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, please check parameters in BRMS (e.g. target release in control group attributes) if they contain values which may become invalid in the higher release.
Also please check 'Data Areas Used in BRMS' if a data area is still used and supported.