Previous Topic: Configure Windows and UNIX ServersNext Topic: Start a Server Manager through an WebSphere MQ Trigger Monitor


Start Server Manager as a Daemon Task

Daemon tasks take the following command line syntax to invoke the server manager executable:

xxxx[-t n ] [-m|M queue_manager_name ] [-q|Q queue_name ][-r|R number_of_requests ]

Where:

xxxx

Specifies the name of the server manager executable (case sensitive on UNIX).

-t n

Identifies the trace level that the executing server manager should use. This value ranges from 0 to 15 with 0 specifying no trace data and 15 specifying the greatest level of detail. The default trace level is 0.

The trace level data writes to a file named lg-<procname>-<procid>.log, where <procname> is the name of the program and <procid> is the process number of the program. For example, in the log file, lg-p126-163574.log, p126 is the name of the program, and 163574 is the name of the process.

On Windows, this file is created in the directory, %USERPROFILE%\AppData\Local\CA\Gen 8.5\logs\server. On UNIX, the file is created in the directory where the program was started.

-m|M

Identifies the name of the local queue manager to which the server manager attempts a connection. The default queue manager name is an empty string (“ “) meaning that the server manager attempts to connect to the default queue manager defined by WebSphere MQ.

-q|Q

Identifies the name of the local queue that the server manager opens. The default is the server manager load module name.

-r|R

Identifies the number of inbound message requests the server manager processes prior to terminating. The default is -1, indicating that the server manager remains active and servicing its inbound message queue.