You run the command crtmqm to create a queue manager.
You specify the Guardian sub-volume by using the
-ng option of the
As with the previous WebSphere MQ for HP NonStop Server V5.3, crtmqm chooses a
new (empty) Guardian sub-volume if the
-ng option is not specified on the
-ngcan be written in various forms:
vol.subvol vol/subvol \$vol.subvol (Note: the $ must be escaped) /G/vol/subvol
-ngoption accepts a trailing "+" wildcard in the sub-volume specification. When the Guardian sub-volume contains this wildcard, it is treated as a sub-volume prefix. Specified this way, the crtmqm command chooses an empty Guardian sub-volume with a name that begins with the specified value. For example:
crtmqm -ng data09.myqmgr+ MYQMGR
This command causes the crtmqm command to choose an empty Guardian sub-volume
with a name starting with
$DATA09.MYQMGR. The chosen sub-volume might be, for
$DATA09.MYQMGR0 if that sub-volume was empty at the time the
crtmqm command was run.
-xspecifies the maximum number of uncommitted messages the queue manager supports. This corresponds to the TMF locklimit per transaction. So make sure that the TMF limit (which can be configured per disk) is at least as large as the limit used by IBM MQ. The default value for
-xfor IBM MQ is 10000, while the default lock limit for TMF is 5000. So either increase the TMF limit (this can be done online, no system interruption is required) or specify
-xwith a lower number than your current TMF configuration. Please consult your system administration, HPE, or IBM if in doubt.