Prior to upgrading BRMS

Some customer interventions may be required for a successful upgrade.

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(5770BR1) 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.
If upgrading to 5770-BR2 from 5770-BR1:

Product 5770-BR2 cannot be installed with product 5770-BR1 already installed. You must delete product 5770-BR1 using option 12 on the GO LICPGM menu or using the DLTLICPGM command.

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

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.