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.
>>-crtmqm--+----------+--+------------------------------+-------> '- -c Text-' '- -d DefaultTransmissionQueue-' .- -lc -. >--+------------------------+--+-------+--+--------------+------> '- -h MaximumHandleLimit-' '- -ll -' '- -ld LogPath-' >--+-------------------+--+----------------------+--------------> '- -lf LogFilePages-' '- -lp LogPrimaryFiles-' >--+------------------------+--+------+-------------------------> '- -ls LogSecondaryFiles-' '- -q -' >--+----------------------+--+-------------------+--------------> '- -g ApplicationGroup-' '- -t IntervalValue-' >--+---------------------+--------------------------------------> '- -u DeadLetterQueue-' >--+--------------------------------+--+------+--QMgrName------>< '- -x MaximumUncommittedMessages-' '- -z -'
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.
In WebSphere MQ for Windows, the default is C:\Program Files\IBM\WebSphere MQ\log (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 UNIX systems, the default number of log file pages is 1024, giving a log file size of 4 MB. The minimum number of log file pages is 64 and the maximum is 65 535.
In WebSphere MQ for Windows, the default number of log file pages is 256, giving a log file size of 1 MB. The minimum number of log file pages is 32 and the maximum is 65 535.
The minimum number of primary log files you can have is 2 and the maximum is 254 on Windows, or 510 on UNIX systems. The default is 3.
The total number of primary and secondary log files must not exceed 255 on Windows, or 511 on UNIX systems, and must not be less than 3.
Operating system limits can reduce the maximum possible log size.
The value is examined when the queue manager is created or started. You can change it after the queue manager has been created. However, a change in the value is not effective until the queue manager is restarted, and the effect might not be immediate.
For more information on primary log files, see What logs look like.
To calculate the size of the primary log files, see Calculating the size of the log.
The minimum number of secondary log files is 1 and the maximum is 253 on Windows, or 509 on UNIX systems. The default number is 2.
The total number of primary and secondary log files must not exceed 255 on Windows, or 511 on UNIX systems, and must not be less than 3.
Operating system limits can reduce the maximum possible log size.
The value is examined when the queue manager is started. You can change this value, but changes do not become effective until the queue manager is restarted, and even then the effect might not be immediate.
For more information on the use of secondary log files, see What logs look like.
To calculate the size of the secondary log files, see Calculating the size of the log.
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
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
zcrtqm |