CRTMQM command is for creating a local queue manager under
an MQ installation.
There are many additional parameters which can be possibly used while creating a queue manager.
The available parameters are
listed below
Required parameters :
QmgrName
The name of the queue manager to
create. The name can contain up to 48 characters.
Optional
parameters :
-d DefaultTransmissionQueue
The name of the local transmission queue where remote
messages are put if a transmission queue is not explicitly defined for their
destination. There is no default.
-lc :: Use circular logging. Circular logging is the
default logging method.
-ld LogPath :: The directory used to hold log files.
In WebSphere MQ for Windows, the default is C:\Program
Files\IBM\WebSphere MQ\log (assuming that C is your data drive) and In
WebSphere MQ for UNIX systems, the default is /var/mqm/log.
-lf LogFilePages :: The log data is held in a series
of files called log files. The log file size is specified in units of 4 KB
pages.
In WebSphere MQ for UNIX systems, the default number of log
file pages is 4096, giving a log file size of 16 MB. The minimum number of log
file pages is 64 and the maximum is 65535.
In WebSphere MQ for Windows systems, the default number of
log file pages is 4096, giving a log file size of 16 MB. The minimum number of
log file pages is 32 and the maximum is 65535.
-ll :: Use linear logging.
-lp LogPrimaryFiles :: The log files allocated when
the queue manager is created.
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.
-ls LogSecondaryFiles :: The log files allocated when
the primary files are exhausted.
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.
-md DataPath :: The directory used to hold the data
files for a queue manager.
In WebSphere MQ for Windows, the default is C:\Program
Files\IBM\WebSphere MQ\qmgrs (assuming that C is your data drive). If the
volume supports file security, the SYSTEM ID, Administrators, and mqm group
must be granted read/write access to the directory.
In WebSphere MQ for UNIX systems, the default is
/var/mqm/qmgrs.
-q :: Makes this queue manager the default queue
manager. The new queue manager replaces any existing default queue manager.
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.
-u DeadLetterQueue :: The name of the local queue
that is to be used as the dead-letter (undelivered-message) queue. Messages are
put on this queue if they cannot be routed to their correct destination.
Examples
This command creates a default queue manager called
Paint.queue.manager, with a description of Paint shop, and creates the system
and default objects. It also specifies that linear logging is to be used:
crtmqm -c "Paint shop" -ll -q
Paint.queue.manager
This command creates a default queue manager called
Paint.queue.manager, creates the system and default
objects, and requests two
primary and three secondary log files:
crtmqm -c "Paint shop" -ll -lp 2 -ls 3 -q
Paint.queue.manager
Start of change This command creates a queue manager called
QM1 on a UNIX or Linux system with its log and queue manager data folders in a
common parent directory. The parent directory is shared on highly available
networked storage to create a multi-instance queue manager. Prior to issuing
the command, create /MQHA, /MQHA/logs and /MQHA/qmgrs owned by user and group
mqm, and with permissions rwxrwxr-x.
crtmqm -ld /MQHA/logs -md
/MQHA/qmgrs QM1
strmqm
(start queue manager)
Purpose:
Use the strmqm command to start a local queue manager.
If the queue manager start up takes more than a few
seconds WebSphere® MQ will show intermittent messages detailing the start up
progress. For more information on these messages see WebSphere MQ Messages.
-c
Start of changeStarts the queue manager, redefines the
default and system objects, then stops the queue manager. Any existing system
and default objects belonging to the queue manager are replaced if you specify
this flag, and any non-default system object values will be reset (for example,
the value of MCAUSER is set to blank).
Use the crtmqm command to create the default and system
objects for a queue manager.
-r
Updates the backup queue manager. The backup queue manager
is not started.
WebSphere MQ updates the backup queue manager's objects by
reading the queue manager log and replaying updates to the object files.
-a
Activate the specified backup queue manager. The backup
queue manager is not started.
Once activated, a backup queue manager can be started using
the control command strmqm QMgrName. The requirement to activate a backup queue
manager prevents accidental startup.
Once activated, a backup queue manager can no longer be
updated.
QMgrName:
The name of a local queue manager. If omitted, the
default queue manager is used.
Examples:
The following command starts the queue manager account:
strmqm ACCOUNT
Comments
Best Hosting in Nepal