Use the mqsicreatebroker command to create a broker and its associated resources.
The queues that are created include a dead letter queue (DLQ), SYSTEM.DEAD.LETTER.QUEUE. The security settings are the same as those of other broker-specific WebSphere MQ queues.
If a message received by a message flow cannot be processed, it is typically backed out onto the input queue. If it cannot be backed out, or the message flow is not configured to back out messages, or to perform alternative error processing, the broker puts the message to the DLQ.
The mqsideletebroker command does not delete the default DLQ (unless the queue manager is deleted).
If you use WebSphere MQ clusters in your domain, define the queue manager before you run this command, and configure the queue manager in the cluster to benefit from reduced administration and increased availability.
If the queue manager is created on Windows by this command, it is not started as a service. The queue manager stops if you log off. Therefore either remain logged on, or change the startup status of the queue manager service. If you lock your workstation, the WebSphere MQ queue manager does not stop.
If the parameters that you specify on this command result in this broker sharing tables within a database schema with other brokers, you must ensure that all these brokers are at the same version of the product.
On Windows systems, the user ID used to run this command must have Administrator authority on the local system.
On Linux and UNIX systems, the user ID used to run this command must be a member of both the mqbrkrs group and the mqm group.
On z/OS systems, the user ID used to run this command must be a member of a group that has both READ and WRITE access to the component directory. The user ID must also have access to WebSphere MQ resources, and DB2®.
Using LDAP: Ensure that the registry is appropriately secured to prevent unauthorized access. You do not have to set the LdapPrincipal and LdapCredentials options on mqsicreatebroker for correct operation of the broker. The password is not stored in clear text in the file system.
Access authority is granted for the WebSphere Event Broker group mqbrkrs to all these queues. If the DLQ is enabled, it also has the same authority.
(51002)[IBM][CLI Driver][DB2/NT]SQL0805N Package "NULLID.SQLLF000" was not found. SQLSTATE=51002.
This error occurs when the bind to the database is not successful.
db2 connect to MYDB user db2admin using db2admin db2 bind X:\sqllib\bnd\@db2cli.lst grant public db2 connect resetwhere X: is the drive on which DB2 is installed.
db2 connect to WBRKBKDB user db2admin using db2admin
db2 bind ~<user_name>/sqllib/bnd/@db2cli.lst grant public CLIPKG 5
db2 connect reset
If you do not use the default DB2 user ID and password (db2admin), you must replace the values in the db2 connect command with the correct values.