Before merging BRMS data, you need to consider the following items:
BRMS data can use a fair amount of DASD when object level detail is saved as part of your backup strategy. Ensure that the target system has sufficient free storage space. The more systems merged, the greater the DASD utilization.
BRMS related job scheduler entries are not transferred during a merge or migration of BRMS data. You need to create new job scheduler entries on the target system if required.
Having a single system with data from multiple systems can increase the time to do backups. Users should be aware that their backup routines may contain additional processes after merging BRMS data.
Running BRMS maintenance take longer to run after the merge is completed if more data is involved.
If a donor system is in an earlier time zone than the target system, do not merge BRMS data onto the target system until the time the data was saved on the donor system has been reached. This prevents the possibility of overwriting current data on the target system.
BRMS data is not affected by different language codes; however, it is possible that menus and reports generated within BRMS are of another language on the target system.
If your donor system has more basic user auxiliary storage pools (ASPs) than the target system, be aware that BRMS has created a library for save file backups for each ASP. The libraries are named Q1ABRMSFnn, where nn is the auxiliary storage pool identifier. Make sure the Q1ABRMSFnn library that resides in an ASP that does not exist on the target system, is empty before the merge.
If spooled files are required from a donor system, save the spooled files on the donor system and then restore the saved spooled files to the target system. This can be done using a spool list. Create and run a backup control group containing the QALLSPLF spooled file list to back up all spooled files on the donor system or use the Work with Lists using BRM (WRKLBRM) command to create a spooled file list specifying the spooled files you want to back up.
If the donor system is a server, point the clients to the target system if it is to be the new server.
Merging from a higher release of BRMS to a lower release is not supported by BRMS.
Do not attempt to merge multiple donor systems to a system at the same time. If multiple systems are to be merged into one or more systems, merge one system at a time.