Running crtmqm

You run the command crtmqm to create a queue manager.

Note: As IBM® MQ for HPE NonStop V8.1 uses TMF-enabled files for queue data storage, logger related crtmqm options are not supported. These are the following options:
  • -lc
  • -ld
  • -lf
  • -ll
  • -lp
  • -ls

You specify the Guardian sub-volume by using the -ng option of the crtmqm command.

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 command-line.

The Guardian sub-volume provided by -ng can be written in various forms:
vol.subvol 
vol/subvol 
\$vol.subvol (Note: the $ must be escaped) 
/G/vol/subvol
Additionally, the -ng option 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 example, be $DATA09.MYQMGR0 if that sub-volume was empty at the time the crtmqm command was run.

Note: The crtmqm option -x specifies 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 -x for 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 -x with a lower number than your current TMF configuration. Please consult your system administration, HPE, or IBM if in doubt.