Merging BRMS data to target system with no BRMS
This section describes how to move BRMS data from a donor system to a target system that does not have BRMS installed.
The merge operation basically consists of moving the BRMS data
from the donor system to the target system and then installing the
BRMS licensed program. The merge steps are:
- Ensure all prerequisites for merging BRMS data are met.
- On the donor system:
- Verify you are signed on with a user profile with *SECOFR authority.
- If donor system is part of a BRMS network group, use the following
command to display the active records for this system:
Verify the QUSRBRM/QA1ANET2 file is empty as shown in the Display Physical File Member panel below.DSPPFM FILE(QUSRBRM/QA1ANET2)
This indicates that donor has no data to send across the current network. Should the QA1ANET2 file not be empty, refer to Checking BRMS network synchronization.Display Physical File Member File . . . . . . : QA1ANET2 Library . . . . : QUSRBRM Member . . . . . : QA1ANET2 *...+....1....+....2....+....3....+....4....+....5....+....6....+....7 (Selected member contains no records)
- Save the QUSRBRM and Q1ABRMSF* libraries on donor system using
the command:
SAVLIB LIB(QUSRBRM Q1ABRMSF*) DEV(tape_device)
- On the target system:
- Verify you are signed on with a user profile with *SECOFR authority.
- Restore the QUSRBRM and Q1ABRMSF* libraries on the target system
using the command:
RSTLIB LIB(QUSRBRM Q1ABRMSF*) DEV(tape_device) ALWOBJDIF(*ALL) MBROPT(*ALL)
- Hold the users batch job queue.
- Install BRMS as outlined in Installing BRMS.
- Load and apply all relevant PTFs.
- Release the users batch job queue to allow the post-installation product initialization to complete.
- If the target system has a different local location name, network
ID, or system name than donor, transfer ownership of all BRMS data
to the target system using the command:
INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(netword-id.donor-system-name) NEWSYSNAM(*LCL)