Use the mqsicreateconfigmgr command to create a Configuration Manager and its associated resources.
If it does not exist:
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 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 you run the mqsicreateconfigmgr command again in this situation, and specify the -n parameter, the parameter is ignored because the new database still exists.
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 the mqbrkrs group.
On z/OS systems, the user ID used to run 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.