Troubleshooting
Problem
This document provides debugging tips on common issues that can occur when systems are networked using BRMS.
Resolving The Problem
If you have missing BRMS information or differences in media, move policies, media classes, and so on between SYSA and SYSB, you should review the following information:
Step 1: Is the update showing correctly on SYSA?
Step 1: Is the update showing correctly on SYSA?
| NO: | It is a local problem rather than a network problem. Examine the joblog, BRMS log (using the DSPLOGBRM command), and the QSYSOPR message queue. |
| YES: | Continue with Step 2. |
Step 2: Did you wait for the information to be transferred between the systems?
Type WRKPCYBRM *SYS and select Option 1. Look at the Shared inventory delay parameter to determine how much time elapses between updates.
Type WRKPCYBRM *SYS and select Option 1. Look at the Shared inventory delay parameter to determine how much time elapses between updates.
| NO: | Be patient. This can sometimes take a while to complete. |
| YES: | Continue with Step 3. |
Step 3: Is the QA1ANET2 file empty?
Use the command DSPPFM QUSRBRM/QA1ANET2 to verify.
| YES: | Your update should have been sent already from SYSA to SYSB. |
| NO: | Your update has not been sent. If the file has records in it, are they decreasing? If they are decreasing, then the information is being sent across to the other systems. If it is getting larger, then continue with Step 4. Also, determine if the records are for a particular system or if they are for multiple or all systems. If it is just for one system, then there might be communication issues between those two systems. |
Step 4: Is anyone locking a BRMS file?
For example, is there a file in use error when trying to network the systems?
For example, is there a file in use error when trying to network the systems?
| YES: | Users should exit BRMS menus and displays. |
| NO: | Continue with Step 5. |
Step 5: Examine the joblog, DSPLOGBRM and QSYSOPR message queue on both systems for any error messages.
Continue with Step 6.
Step 6: What communication method are you using for the BRMS network?
Continue with Step 6.
Step 6: What communication method are you using for the BRMS network?
To determine the communication method, type WRKPCYBRM *SYS and select Option 4, Change network group. The V6R1 and later options and their meanings:
*AVAIL - BRMS will attempt to use TCP/IP first, but if that is unsuccessful, BRMS will then attempt to use SNA for its network operations.*RDB - BRMS is enabled to use the remote location information from the relational database entry for its network operations.
*IP - BRMS is enabled to use TCP/IP for its network operations.
*IP - BRMS is enabled to use TCP/IP for its network operations.
*SNA - BRMS is enabled to use SNA for its network operations.
*NONE - BRMS is not enabled for network operations.
SNA
Are you able to use APING with a mode of QBRM? Type the following command:
APING RMTLOCNAME('remote-sys-name') MODE(QBRM)
| YES: | Continue with Step 7. |
| NO: | a. Is the remote system running? YES: Can you pass through? Type the command STRPASTHR RMTLOCNAME(remote-sys-name). NO: Bring up the remote system. b. Verify your configuration (the system name, address, netid, and so on). Review the joblog for communication errors. c. Verify that the controllers used for the APPC communications are varied on for each system. Is the controller referring to SYSB on SYSA and vice versa? If the controllers are not varied on, vary them on. Use the following commands to verify the status: WRKCFGSTS CFGTYPE(*LIN) WRKCFGSTS CFGTYPE(*CTL) WRKCFGSTS CFGTYPE(*DEV) |
TCP
Are you able to PING? Type the command PING RMTSYS(remote-system-name).
| YES: | Continue with Step 7. |
| NO: | a. Use the WRKTCPSTS OPTION(*IFC) command to determine the status of the TCP/IP interfaces. b. Are you able to PING the TCP/IP address of the remote system? Type the command PING RMTSYS(IP address). YES: There might not be a host table entry for the system for that TCP/IP address. Type CFGTCP and select Option 10. If the TCP/IP address is listed without the name of the system or if the TCP/IP address is not listed at all, then contact the TCP queue. |
RDB (In releases IBM i 6.1 and later)
Type WRKRDBDIRE.
Does both *local entry with the system name (or BRMS user defined name if using any) and remote entry to the other systems in the BRMS network exist?
| YES: | Continue with Step 7. |
| NO: |
a. If *LOCAL RDB name has to be changed, review Using Relational Database Entries for All BRMS Communications - IBM Partnership - Confluence Additional information can be found in Example: Setting up a relational database directory - IBM Documentation |
Step 7: Is Q1ABRMNET SBS started? Is the Q1ABRMNET job queue released?
| NO: |
Start the QBRM/Q1ABRMNET subsystem (STRSBS QBRM/Q1ABRMNET) or release the QBRM/Q1ABRMNET job queue. It is advisable to end and restart the Q1ABRMNET subsystem after finding any network problems. Use the command ENDSBS QBRM/Q1ABRMNET on both (or all) systems, and then use the command STRSBS QBRM/Q1ABRMNET.
|
| YES: | Is the QBRMSYNC job running in the subsystem periodically? NO: Try ending and restarting the QBRM/Q1ABRMNET subsystem. If both the QBRMNET and the QNMAPINGD jobs are running in the subsystem, try making a change to a volume. For example, type WRKMEDBRM and select Option 2 next to a volume but do not actually change anything about the volume. This "non-change" causes an update in the journal, which causes the QBRMSYNC job to run. YES: Review the QBRMSYNC joblog for errors. You might need to change the message logging for the QBRMSYNC job to LOG(4 00 *SECLVL). Type WRKJOBD QBRM/QBRMSYNC, select Option 2 to change, and then press F10 for additional parameters. Review for error messages. Note: Do not forget to change this back to *NOLIST. Continue with Step 8. |
Step 8: Is SYSB showing up as active on SYSA?
| YES: | Continue with Step 9. |
| NO: | Refer to the following document: BRMS Systems Appear Inactive in a BRMS Network: |
Step 9: Can you use DDM?
Verify that the QSYS/CRTDDMF command has the correct authority by typing the following command:
DSPOBJAUT OBJ(QSYS/CRTDDMF) OBJTYPE(*CMD)
If it does not have the correct authority, change the authority.
Note: If Public is *EXCLUDE the user would require private authority to the command
unless they have *ALLOBJ authority.
Type the following to verify DDM:
CRTDDMF FILE(AnyName) RMTFILE(QUSRBRM/QA1AMM) RMTLOCNAME(RmtSysNameThatIsHavingIssues *IP)
Note: 'AnyName' is the name of the DDM file that will be created. You can choose any remote file; it does not have to be the QA1AMM file.
DSPPFM LIBRARY/AnyName
where LIBRARY is the name of the library that the DDM file you created resides in. This should display the same records as the remote file.
Note: You can use any file for the RMTFILE parameter.
| NO: | a. Verify that the QBRMS user profile exists on all systems in the network and that it is enabled. b. It is recommended that QBRMS does not have a password associated with it on any of the systems in the network. Type the following command: CHGUSRPRF USRPRF(QBRMS) PASSWORD(*NONE) c. - Is secured or unsecured DDM used? To determine, type CHGDDMTCPA and press F4 and review the Lowest authentication method (*USRID, *USRIDPWD)
1) Use the following commands to change the TCP/IP DDM attributes for non-secured operations: CHGDDMTCPA PWDRQD(*USRID)
2) If you are going from a secured DDM connection to a non-secured DDM connection, make sure to remove the server authentication entries. Use the commands to remove server Authentication entries for each user:
-RMVSVRAUTE USRPRF(user-profile) SERVER(QDDMSERVER) -RMVSVRAUTE USRPRF(user-profile) SERVER(QDDMDRDASERVER) NOTE: "QDDMSERVER" and "QDDMDRDASERVER" must be uppercase.
1) Use the following command to change the TCP/IP DDM attributes for secured operations:
CHGDDMTCPA PWDRQD(*USRIDPWD) 2) Automated secure TCP/IP DDM operations are not possible if authentication passwords cannot be stored. Type the following command to change the QRETSVRSEC system value so that passwords used for authentication can be stored on the system: CHGSYSVAL QRETSVRSEC VALUE('1)
3) Type the following command to add server authentication entries for each user who will be authorized to perform secured TCP/IP operations to the remote systems:
ADDSVRAUTE USRPRF(user-profile) SERVER(QDDMDRDASERVER) USRID(remote-system-userid) + PASSWORD(remote-system-password) 4) Type the following command to add server authentication entries for user QBRMS. This user profile is used for network synchronization:
ADDSVRAUTE USRPRF(QBRMS) SERVER(QDDMDRDASERVER) USRID(remote-system-userid) PASSWORD(remote-system-password) Notes:
d- Is the DDM server started? NO: Type the command STRTCPSVR SERVER(*DDM). |
Step 10: Is DRDA functionality working?
BRMS requires DRDA functionality for certain query operations. To test if DRDA is setup correctly to connect to the remote system do the following:
STRSQL
Then execute the following statement:
CONNECT TO remote_system USER user_id USING 'password'
Note: User ID and password must exist and be enabled on target remote system.
If connection fails, the error message will indicate why.
If connection is successful ensure you set connection back to the local system with one of the following options:
Option 1
SET CONNECTION local_system
Option 2
Exit Interactive SQL
Step 11: Is the system in Flash Copy Mode
Starting at V6R1M0 there is a Flash Copy Mode.
Type WRKPCYBRM *SYS and select Opt 4.
FlashCopy state should show *ENDPRC
If it doesn't, no data will be transferring from the network and QA1ANET2 will have records in it,
the QBRMSYNC job may end immediately after posting CPF0001 to PGM Q1ACSYN
BRMS requires DRDA functionality for certain query operations. To test if DRDA is setup correctly to connect to the remote system do the following:
STRSQL
Then execute the following statement:
CONNECT TO remote_system USER user_id USING 'password'
Note: User ID and password must exist and be enabled on target remote system.
If connection fails, the error message will indicate why.
If connection is successful ensure you set connection back to the local system with one of the following options:
Option 1
SET CONNECTION local_system
Option 2
Exit Interactive SQL
Step 11: Is the system in Flash Copy Mode
Starting at V6R1M0 there is a Flash Copy Mode.
Type WRKPCYBRM *SYS and select Opt 4.
FlashCopy state should show *ENDPRC
If it doesn't, no data will be transferring from the network and QA1ANET2 will have records in it,
the QBRMSYNC job may end immediately after posting CPF0001 to PGM Q1ACSYN
[{"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":"a8m0z0000000CKTAA2","label":"Backup Recovery Install Migration-\u003EBRMS"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
427939498
Was this topic helpful?
Document Information
Modified date:
29 November 2024
UID
nas8N1018963