Use the crtmqm command to create a local queue manager and define the default and system objects. The objects created by crtmqm are listed in Appendix A, System and default objects. When a queue manager has been created, use the strmqm command to start it.
Required parameters
Optional parameters
If you include special characters, enclose the description in double quotes. The maximum number of characters is reduced if the system is using a double-byte character set (DBCS).
Specify a value in the range 1 through 999 999 999. The default value is 256.
The next six parameter descriptions relate to logging, which is described in Using the log for recovery.
Note: | Choose the logging arrangements with care, because you cannot change them once they are committed. |
In WebSphere MQ for Windows, the default is C:\Program Files\IBM\WebSphere MQ\log\qmgr(assuming that C is your data drive).
In WebSphere MQ for UNIX systems, the default is /var/mqm/log.
User ID mqm and group mqm must have full authorities to the log files. If you change the locations of these files, you must give these authorities yourself. This occurs automatically if the log files are in their default locations.
In WebSphere MQ for Windows, the minimum value is 32, and the maximum is 4095. The default value is 256, giving a default log size of 1 MB.
In WebSphere MQ for UNIX systems, the minimum value is 64, and the maximum is 16384. The default value is 1024, giving a default log size of 4 MB.
Note: | The total number of log files is restricted to 63, regardless of the number requested. |
The limits given in the previous parameter descriptions are limits set by WebSphere MQ. Operating system limits might reduce the maximum possible log size.
If you accidentally use this flag and want to revert to an existing queue manager as the default queue manager, change the default queue manager as described in Making an existing queue manager the default.
This option applies only to WebSphere MQ for AIX, Solaris, HP-UX, and Linux.
The default value is -g all, which allows unrestricted access.
The -g ApplicationGroup value is recorded in the queue manager configuration file, qm.ini.
The mqm user ID must belong to the specified ApplicationGroup.
You can use the trigger time interval to ensure that your application is allowed sufficient time to deal with a trigger condition before it is alerted to deal with another on the same queue. You might choose to see all trigger events that happen; if so, set a low or zero value in this field.
Specify a value in the range 0 through 999 999 999. The default is 999 999 999 milliseconds, a time of more than 11 days. Allowing the default to be used effectively means that triggering is disabled after the first trigger message. However, an application can enable triggering again by servicing the queue using a command to alter the queue to reset the trigger attribute.
The default is no dead-letter queue.
This limit does not apply to messages that are retrieved or put outside a syncpoint.
Specify a value in the range 1 through 999 999 999. The default value is 10 000 uncommitted messages.
This flag is used within WebSphere MQ to suppress unwanted error messages. Because using this flag can result in loss of information, do not use it when entering commands on a command line.
0 | Queue manager created |
8 | Queue manager already exists |
49 | Queue manager stopping |
69 | Storage not available |
70 | Queue space not available |
71 | Unexpected error |
72 | Queue manager name error |
100 | Log location invalid |
111 | Queue manager created. However, there was a problem processing the default queue manager definition in the product configuration file. The default queue manager specification might be incorrect. |
115 | Invalid log size |
crtmqm -c "Paint shop" -ll -q Paint.queue.manager
crtmqm -c "Paint shop" -ll -lp 2 -ls 3 -q Paint.queue.manager
crtmqm -t 5000 -u SYSTEM.DEAD.LETTER.QUEUE travel
strmqm | Start queue manager |
endmqm | End queue manager |
dltmqm | Delete queue manager |