Troubleshooting
Problem
This document explains how to correct systems that appear as INACTIVE on some systems after they were added to a BRMS network.
Resolving The Problem
This document explains how to correct systems that appear as INACTIVE on some systems after they were added to a BRMS network.
Example
You add new systems to an existing BRMS network; at that point, all systems show the correct status. For example, you have three systems in an existing network group:
On SYSA, a user types WRKPCYBRM *SYS and adds SYSD.
On SYSD, a user types the following commands:
CPYMEDIBRM OPTION(*TOFILE)
INZBRM *NETSYS FROMSYS(SYSA)
where SYSA is the system designated as the master system.
CPYMEDIBRM OPTION(*FROMFILE)
If all systems are up and DDM is working correctly between all systems, then things will look good. However, if SYSB is down during this time and SYSD cannot communicate with SYSB after the INZBRM command has completed, when SYSB starts up it will show the information in the following table.
Note: The job log might list error messages for communications to SYSB but SYSD and SYSA will have the correct information.
Resolution
On SYSD, do the following:
This document can also be used to correct systems that are showing an inactive status after normal operations.
Note: Users must ensure that the steps in the BRMS manual (SC41-5345) to add a system to a BRMS network were correctly followed.
Example
You add new systems to an existing BRMS network; at that point, all systems show the correct status. For example, you have three systems in an existing network group:
| SYSA | SYSB | SYSC | New system SYSD |
| SYSB Active | SYSA Active | SYSA Active | |
| SYSC Active | SYSC Active | SYSB Active |
On SYSD, a user types the following commands:
CPYMEDIBRM OPTION(*TOFILE)
INZBRM *NETSYS FROMSYS(SYSA)
where SYSA is the system designated as the master system.
CPYMEDIBRM OPTION(*FROMFILE)
If all systems are up and DDM is working correctly between all systems, then things will look good. However, if SYSB is down during this time and SYSD cannot communicate with SYSB after the INZBRM command has completed, when SYSB starts up it will show the information in the following table.
Note: The job log might list error messages for communications to SYSB but SYSD and SYSA will have the correct information.
| SYSA | SYSB | SYSC | New system SYSD |
| SYSB Active | SYSA Active | SYSA Active | SYSA Active |
| SYSC Active | SYSC Active | SYSB Active | SYSB Active |
| SYSD Active | SYSD Inactive | SYSD Active | SYSC Active |
Resolution
On SYSD, do the following:
| 1. | On the operating system command line, type the following: CPYMEDIBRM OPTION(*TOFILE) Press the Enter key. |
| 2. | On the operating system command line, type the following: INZBRM *NETSYS FROMSYS(SYSB) Press the Enter key. Note: On any BRM1519 - Entries exist for &1. (R I C) message, select an I to ignore. |
| 3. | On the operating system command line, type the following: CPYMEDIBRM OPTION(*FROMFILE) Press the Enter key. This will make the status for SYSD correct on SYSB. |
| SYSA | SYSB | SYSC | New system SYSD |
| SYSB Active | SYSA Active | SYSA Active | SYSA Active |
| SYSC Active | SYSC Active | SYSB Active | SYSB Active |
| SYSD Active | SYSD Active | SYSD Active | SYSC Active |
This document can also be used to correct systems that are showing an inactive status after normal operations.
Note: Users must ensure that the steps in the BRMS manual (SC41-5345) to add a system to a BRMS network were correctly followed.
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z000000cwpBAAQ","label":"Save Restore-\u003EBRMS"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
373811696
Was this topic helpful?
Document Information
Modified date:
08 October 2024
UID
nas8N1015614