db2mqlsn - MQListener command

Authorization

• All options except db2mqlsn admin access the MQListener configuration in the configDB database. The connection is made as configUser or, if no user is specified, an implicit connection is attempted. The user in whose name the connection is made must have EXECUTE privilege on package mqlConfi.
• To access MQ objects with the db2mqlsn run and db2mqlsn admin options, the user who executes the program must be able to open the appropriate MQ objects.
• To execute the db2mqlsn run option successfully, the dbUser specified in the db2mqlsn add option that created the task must have EXECUTE privilege on the specified stored procedure, and must have EXECUTE privilege on the package mqlRun in the dbName database.

Command syntax

configuration

run parameters

add parameters

remove parameters

admin parameters

Command parameters

help command

Supplies detailed information about a particular command. If you do not give a command name, then a general help message is displayed.

-configDB configuration database

Name of the database that contains the configuration information.

-configUser user ID -configPwd password

Authorization information with which to access the configuration database.

-config configuration name

You can group individual tasks into a configuration. By doing this you can run a group of tasks together. If you do not specify a configuration name, then the utility runs the default configuration.

run

-adminQueue admin queue name -adminQMgr admin queue manager

This is the queue on which the MQListener listens for administration commands. If you do not specify a queue manager, then the utility uses the configured default queue manager. If you do not specify an adminQueue, then the application does not receive any administration commands (such as shutdown or restart) through the message queue.

add

-inputQueue input queue name -queueManager queue manager name

This is the queue on which the MQListener listens for messages for this task. If you do not specify a queue manager, the utility uses the default queue manager configured in WebSphere MQ.

-procSchema stored procedure schema -procName stored procedure name

The stored procedure to which MQListener passes the message when it arrives.

-dbName stored procedure database

MQListener passes the message to a stored procedure. This is the database in which the stored procedure is defined.

-dbUser user ID -dbPwd password

The user on whose behalf the stored procedure is invoked.

-mqCoordinated

This indicates that reading and writing to the WebSphere MQ message queue should be integrated into a transaction together with the Db2 stored procedure call. The entire transaction is coordinated by the WebSphere MQ coordinator. (The queue manager must also be configured to coordinate a transaction in this way. See the WebSphere MQ documentation for more information.) By default, the message queue operations are not part of the transaction in which the stored procedure is invoked.

-numInstances number of instances to run

The number of duplicate instances of this task to run in this configuration. If you do not specify a value, then only one instance is run.

remove

-inputQueue input queue name -queueManager queue manager name

This is the queue and queue manager that define the task that will be removed from the configuration. The combination of input queue and queue manager is unique within a configuration.

admin

-adminQueue admin queue name -adminQueueList namelist of admin queue names -adminQMgr admin queue manager

The queue or namelist of queue names on which to send the admin command. If you do not specify a queue manager, the utility uses the default queue manager that is configured in WebSphere MQ.

-adminCommand admin command

Submits a command. The command can be either shutdown or restart. shutdown causes a running MQListener to exit when the listener finishes processing the current message. restart performs a shutdown, and then reads the configuration again and restarts.