If you choose to create the queue manager separately, you must set up a dead letter queue (DLQ). The DLQ is referenced by WebSphere Event Broker when errors occur processing messages in message flows.
If a message in either a user-defined message flow or in the publish/subscribe model cannot be processed, it is routed to this DLQ as a last resort. If you prefer to back out the message onto the input queue, effectively halting the message flow until the problem is resolved, disable the DLQ.
The mqsideletebroker command does not delete this queue (unless the queue manager is deleted).
If you are using a WebSphere MQ queue manager that has been created independently of the mqsicreatebroker command, you can define clusters if you choose. This simplifies your configuration in most cases.
If the queue manager is created by this command, it is not started as a Windows service; it therefore stops if you log off. To avoid this happening, you must 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.
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 systems, the user ID used to invoke this command must be a member of a group that has READ and WRITE access to the component directory and have access to WebSphere MQ resources and DB2.
Using LDAP: Ensure that the registry is appropriately secured to prevent unauthorized access. The setting of LdapPrincipal and LdapCredentials options on mqsicreatebroker is not required 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.
On Windows platforms, binding is not needed for broker databases, but is required for user databases. If you have created the database using the DB2 Control Center, the bind is completed for you. If you use the command interface, it is not. For the database MYDB, for example, you can create or recreate a bind by entering the following commands at the command prompt:
db2 connect to MYDB user db2admin using db2admin db2 bind X:\sqllib\bnd\@db2cli.lst grant public db2 connect reset
where X: is the drive on which DB2 is installed.
On UNIX platforms, binding is necessary for all databases. For example, to create binding for database WBRKBKDB, you can enter the following commands at the command prompt (where <user_name> is the user ID under which the database instance was created):
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 are not using the default DB2 user ID and password (db2admin), you must replace these values in the db2 connect command with the correct values.
If you run the mqsicreatebroker command and it fails, resolve the problem that caused the failure. When you run the same command again you might receive a series of messages indicating any items that cannot be created. Receiving these messages does not indicate a problem with the mqsicreatebroker command itself.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an07080_ |