The user ID and password pair is created in the DSN folder under the broker's registry folder.
This command does not run if the broker is running. You must stop the broker before you run this command.
The mqsisetdbparms command allows you to create, alter, or delete the user ID and password pairs.
For compatibility with existing systems, you can still specify <password>. However, if you do not specify a password with this parameter when you run the command you are prompted to enter a password during its invocation, and to enter the password a second time to verify that you have entered it correctly.
On Windows systems the user ID used to invoke this command must have Administrator authority on the local system.
On UNIX systems, the user ID used to invoke this command must be a member of the mqbrkrs group.
On z/OS, the user ID used to invoke this command must be a member of a group which has READ and WRITE access to the component directory.
mqsisetdbparms WBRK_BROKER -n MQBroker1 -u MQUserId -p password
mqsisetdbparms WBRK_BROKER -n MQBroker1 -d
The following examples show the use of the command when the URI for a JMS or JNDI resource name is substituted for the DataSourceName associated with the -n flag.
For a JMS resource the prefix is "jms::" and for JNDI the prefix is "jndi::".
On UNIX systems, if the parameter string includes a back slash "\" character, you must escape from this character by using a second back slash character "\\" when entering the mqsisetdbparms command.
mqsisetdbparms MyBroker1 -n jms::tcf1 -u myuserid -p secret
mqsisetdbparms MyBroker1 -n jndi::com.sun.jndi.fscontext.RefFSContextFactory
-u myuserid -p secret
The preceding examples describe how to configure security for JMS and JNDI resources for all JMS Nodes using those resources in a broker.
<Message Flow Name>_<Node label>
MyJMSFlow1_MyJMSInput1
<resource type><account name>@<resource name>
jms::MyJMSFlow1_MyJMSInput1@tcf1
mqsisetdbparms MyBroker1 -n jms::MyJMSFlow1_MyJMSInput1@tcf1
-u myuserid -p secret