Merging BRMS data to target system with existing BRMS

This section describes how to move BRMS data from a donor system to a target system when the target system has BRMS installed.

BRMS is running backup policies on the target system so there exists on this system history and media information owned by the target system. The merge operation basically consists of combining the BRMS data from the donor system with the BRMS data on the target system. Since BRMS is already installed on the target system, no installation of BRMS is required. The merge steps are:

Ensure all prerequisites for merging BRMS data are met.
Review the printed outputs of the data you intend to merge to assure there are no duplicates. Only unique BRMS objects and information will be merged.
If using Software Encryption, you might need to translate all the necessary keystore files in QUSRBRM. Refer to the Merge consolidation planning section for more information.
On the donor system:
1. Verify you are signed on with a user profile with *SECOFR authority.
2. If donor system is part of a BRMS network group, use the following command to display the active records for this system:
```
   DSPPFM FILE(QUSRBRM/QA1ANET2)
```
  Verify the QUSRBRM/QA1ANET2 file is empty as shown in the Display Physical File Member panel below.
```
                          Display Physical File Member                 
 File . . . . . . :   QA1ANET2             Library  . . . . :   QUSRBRM 
 Member . . . . . :   QA1ANET2                                          
                                                                       
                                                                       
 *...+....1....+....2....+....3....+....4....+....5....+....6....+....7
                                                                       
   (Selected member contains no records)                                       
```
  This indicates that donor has no data to send across the current network. If the QA1ANET2 file is not empty, refer to Checking BRMS network synchronization.
3. If you want to differentiate the save history of the donor system from that of the target system, you can update the history records with a unique control group using the following SQL command:
```
   UPDATE QUSRBRM/QA1AHS 
      SET BKHGRP='new-control-group-name'
    WHERE BKHGRP='old-control-group-name'
```
  This step is optional and may not even be necessary if the saves on the donor system were performed using control groups which do not exist on the target system. Once you have completed the rename and merge the data to the target system, you will be able to view these older saves using the following command:
```
   WRKMEDIBRM CTLGRP(new-control-group-name)
```
4. Save the QUSRBRM and Q1ABRMSF* libraries on donor system using the command:
```
   SAVLIB LIB(QUSRBRM Q1ABRMSF*) DEV(tape_device)
```
  Note: You do not need to save the Q1ABRMSF* libraries if you do not intend to merge the save history of the donor system to the target system.
On the target system:
1. Verify you are signed on with a user profile with *SECOFR authority.
2. Save the QUSRBRM and Q1ABRMSF* libraries on target system using the command:
```
   SAVLIB LIB(QUSRBRM Q1ABRMSF*) DEV(tape_device)
```
  The save of these libraries will protect you in the event you need to back off the merge.
3. If you intend to merge the save history of the donor system to the target system, then use the following command to restore the save files in the Q1ABRMSF* libraries to the target system.
```
   RSTOBJ OBJ(*ALL) LIB(Q1ABRMSF*) DEV(tape_device) 
              ALWOBJDIF(*ALL) MBROPT(*ALL)
```
4. Restore the QUSRBRM library from the donor system to a temporary library on the target system using the following command.
```
   RSTLIB LIB(QUSRBRM) DEV(tape_device) RSTLIB(temp-library-name) 
                 ALWOBJDIF(*ALL) MBROPT(*ALL)
```
  Note: Do not restore the QUSRBRM library from the donor system to the QUSRBRM library on the target system.
5. Merge the BRMS data from the temporary library to QUSRBRM on the target system using the following:
  - If using Software Encryption and your keystore files had to be translated, then issue this command:
```
   INZBRM OPTION(*MERGE) FROMLIB(temp-library-name) 
           TOLIB(QUSRBRM) MERGE(merge-options) 
           KEYSTORE((source-keystore-file translated-keystore-file))
```
    You can specify more then one keystore file on the Keystore parameter.
  - Otherwise, issue this command:
```
   INZBRM OPTION(*MERGE) FROMLIB(temp-library-name) 
           TOLIB(QUSRBRM) MERGE(merge-options)
```
  where merge options specifies the types of BRMS data to be merged.
  Note: Because of the extensive file processing involved in the merge operation, this could be a long running process depending on the merge options you select and the size of the merged files.
6. Review the job log or the BRMS log for messages related to the merge processing. Verify the merge completed successfully. Assure that objects not merged are not required. Messages generated by the merge process include the following:
  BRM13B0 C
  
  Merge started for file &2 in library &3.
  
  BRM13B1 C
  
  Merge ended for file &2 in library &3.
  
  BRM13C1 I
  
  Archive control group &2 added.
  
  BRM13C2 I
  
  Archive list &2 of type &3 added.
  
  BRM13C3 I
  
  Backup control group &2 added.
  
  BRM13C4 I
  
  Backup list &2 of type &3 added.
  
  BRM13C5 I
  
  Migration control group &2 added.
  
  BRM13C6 I
  
  Device &2 added.
  
  BRM13C7 I
  
  Connection name &2 added.
  
  BRM13C8 I
  
  Storage location &2 added.
  
  BRM13C9 I
  
  Media class &2 added.
  
  BRM13CA I
  
  Move policy &2 added.
  
  BRM13CB I
  
  Media policy &2 added.
  
  BRM13CC I
  
  Container class &2 added.
  
  BRM13CD I
  
  Container &2 added.
  
  BRM13CE I
  
  ASP class &2 added.
  
  BRM13CF I
  
  Volume &2 added.
  
  BRM13D1 I
  
  Archive control group &2 not added. Reason &5.
  
  BRM13D2 I
  
  Archive list &2 of type &3 not added. Reason &5.
  
  BRM13D3 I
  
  Backup control group &2 not added. Reason &5.
  
  BRM13D4 I
  
  Backup list &2 of type &3 not added. Reason &5.
  
  BRM13D5 I
  
  Migration control group &2 not added. Reason &5.
  
  BRM13D6 I
  
  Device &2 not added. Reason &5.
  
  BRM13D7 I
  
  Connection name &2 not added. Reason &5.
  
  BRM13D8 I
  
  Storage location &2 not added. Reason &5.
  
  BRM13D9 I
  
  Media class &2 not added. Reason &5.
  
  BRM13DA I
  
  Move policy &2 not added. Reason &5.
  
  BRM13DB I
  
  Media policy &2 not added. Reason &5.
  
  BRM13DC I
  
  Container class &2 not added. Reason &5.
  
  BRM13DD I
  
  Container &2 not added. Reason &5.
  
  BRM13DE I
  
  ASP class &2 not added. Reason &5.
  
  BRM13DF I
  
  Volume &2 not added. Reason &5.
  
  BRM13F0 D
  
  Volume &2 not updated. Reason &5.
  
  BRM13FE D
  
  File &2 not merged. Reason &5
  
  BRM13FF E
  
  Merge operation not successful. Reason &5.
7. Verify the merged policies by editing or changing the policy using the standard BRMS interfaces. Resolve any errors that may occur during the validation processing.
8. If the target system has a different local location name, network ID, or system name than the donor system and you want to consider the saved history and media as now owned by the current system, transfer ownership of the merged BRMS data to the target system using the command:
```
   INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(netword-id.donor-system-name) 
                             NEWSYSNAM(*LCL)  
```
  Note: Merging BRMS data to a target system with existing BRMS will not merge save file history because of possible naming collisions on the target system. When consolidating systems and removing the source system from the BRMS network, if the target system is not changed to own the media and history from the source system by running the INZBRM *CHGSYSNAM function, then history will be removed during a run of maintenance. BRMS does not allow history from another system on the local system if the systems are not networked.