If you choose to create the queue manager separately, set up a dead-letter queue (DLQ); the DLQ is referenced by WebSphere Message 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 would prefer the message to be backed out onto the input queue, effectively halting the message flow until the problem is resolved, disable the DLQ.
The mqsideleteconfigmgr command does not delete this queue (unless the queue manager is deleted).
If you run the mqsicreateconfigmgr command again in this situation, and specify the -n parameter, the parameter is ignored because the new database still exists.
This command changes security privileges for the ServiceUserID; the user ID used to invoke this command must be a member of the Windows Administrators group on this 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 access to WebSphere MQ.
Access authority is granted for the WebSphere Message Broker group mqbrkrs to all these queues. If the DLQ is enabled, it also has the same authority.