Checking BRMS network synchronization
The System status field on the Change Network Group display should provide you with an easy means of determining whether the current system is communicating with the other networked systems.
A status of Online indicates that synchronization is running
between the two systems. A status of Offline may be an indication
of a problem.
Note: Network Status only indicates whether
the system has or has not been activated into the network.
You can take the following steps to run a daily check of media synchronization:
- On one system in the BRMS network, create a dummy media class (for example, NETCHK, which stands for Network Checking). Because you will not use this media class for real backups, you can simply use the default values.
- On each system (SYSTEMxx, where xx = name of the system), type: ADDMEDBRM VOL(SYSxx) MEDCLS(NETCHK)
- Every morning, on each system in your BRMS network, use the job
scheduler to run the CL command:
RMVMEDBRM VOL(SYSxx) MEDCLS(NETCHK)
Delay Job (DLYJOB) DLY(300)
ADDMEDBRM VOL(SYSxx) MEDCLS(NETCHK).
- After you submit the CL command, your media should have a creation date equal to the current date. This should be true on the system that will run the command. If not, it means that you did not submit the CL command, and should check the job log for error information. The other systems in the BRMS network should also have the current date as the creation date for this media. If not, it means that system did not process the update correctly.
Assuming that the current date is July 6, 2005, the WRKMEDBRM command
for each system should display the following information:
Work with Media SYSTEM01
Position to . . . . . . Starting characters
Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 6=Work with serial set 7=Expire
8=Move 9=Remove volume error status 10=Reinitialize ...
Volume Creation Expiration Move Media Dup
Opt Serial Status Date Date Location Date Class Sts
__ ______
xxxxxx xx/xx/xx *NONE xxxxxxxx xx/xx/xx xxxxxxx
xxxxxx xx/xx/xx *NONE xxxxxxxx xx/xx/xx xxxxxxx
SYS01 *EXP 07/06/05 *NONE *HOME *NONE NETCHK
SYS02 *EXP 07/06/05 *NONE *HOME *NONE NETCHK
SYS03 *EXP 07/06/05 *NONE *HOME *NONE NETCHK
SYS04 *EXP 07/06/05 *NONE *HOME *NONE NETCHK
xxxxxx xx/xx/xx *NONE xxxxxxxx xx/xx/xx xxxxxxx
More...
Parameters or command:
===> _________________________________________________________________________
F3=Exit F4=Prompt F5=Refresh F11=Volume system F12=Cancel F17=Top
F18=Bottom F23=More options
Press F11 to view the owning system. Reviewing the following display,
you might conclude that SYSTEM01 did not receive the SYSTEM04 media
update.
Work with Media SYSTEM01
Position to . . . . . . ______ Starting characters
Type options, press Enter.
1=Add 2=Change 4=Remove 5=Display 6=Work with serial set 7=Expire
8=Move 9=Remove volume error status 10=Reinitialize ...
Volume Creation Expiration Move Media Dup
Opt Serial Status Date Date Location Date Class Sts
__ ______
SYS01 *EXP 07/06/05 *NONE *HOME *NONE NETCHK
SYS02 *EXP 07/06/05 *NONE *HOME *NONE NETCHK
SYS03 *EXP 07/06/05 *NONE *HOME *NONE NETCHK
SYS04 *EXP 07/04/05 *NONE *HOME *NONE NETCHK
More...
Parameters or command:
===> __________________________________________________________________________
F3=Exit F4=Prompt F5=Refresh F11=Volume system F12=Cancel F17=Top
F18=Bottom F23=More options
In this case, it could be that a communications problem occurred subsequent to July 4th.