...
You need to determine whether you intend to use secured or non-secured DDM connections to the remote systems in the BRMS network. In order to use a non-secured DDM connection, the user id must exist on the remote system, although the user's password will not be validated. To use a secured DDM connection the user id and password must be the same on both the local and remote systems. You may want to review this setup with your site security administrator before taking specific actions.
For Non-secured DDM connections
Use one of the following commands to change the TCP/IP DDM attributes for non-secured operations:
CHGDDMTCPA PWDRQD(*NO)CHGDDMTCPA PWDRQD(*USRID)
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.
Go to step 3.
BRMS strongly encourages the use of Secured DDM connections and implementing passwords for the Relational Database Directory Entries used for DB2 for i call level interface (CLI) communications.
For Secured DDM connection
Use one of the following commands to change the TCP/IP DDM attributes for secured operations:
...
There can only be one server authorization entry for a user no matter what remote system is specified. This means that for a user to access multiple systems in the network, that user's id and password must be the same on all BRMS networked systems.
Do not use user profile QBRMS for the remote system userid. Create a new user profile and specify user profile QBRMS for the Group profile (GRPPRF) parameter of the remote system user profile. Use this new remote system userid for the User ID (USRID) parameter of the Add Server Authentication Entry (
ADDSVRAUTE) command.
Go to step 3.
For Non-secured DDM connections
Use one of the following commands to change the TCP/IP DDM attributes for non-secured operations:
CHGDDMTCPA PWDRQD(*NO)CHGDDMTCPA PWDRQD(*USRID)
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.
Step 3: Configure the TCP/IP DDM Server Automatic Restart
...