Controlling the WebSphere MQ extension on i5/OS platforms
- Before starting an extension, enter WRKACTJOB to check that the agent is running. Look for QPEA in the list of running jobs. If it is not running, enter the following command:
SBMJOB CMD(CALL PGM(QPASA/QPEA) PARM('--start')) - Use the commands:
SBMJOB CMD(CALL PGM(QPASA/QPMON) PARM('command parameter'))SBMJOB CMD(CALL PGM(QPASA/QPCFG) PARM('command parameter'))
The table below lists the command parameters.
For example, to start the WebSphere MQ monitoring extension, enter:SBMJOB CMD(CALL PGM(QPASA/QPMON) PARM('–start'))
Likewise, to stops the WebSphere MQ configuration extension, enter:SBMJOB CMD(CALL PGM(QPASA/QPCFG) PARM('--stop'))
Command parameter | Use to... |
|---|---|
| Run the extension program in the foreground, displaying log messages as they are generated. It is useful when trying to locate or troubleshoot problems. |
| List the available command prompt options (this list) and short descriptions. |
| Start the extension. If an extension does not start while the TMTM Extensible Agent is running, ensure that MAXJOB is set to *NOMAX. The command is:
TrueSight Middleware and Transaction Monitor starts a separate QPMONSUB job for each queue manager that is monitored on i5/OS. For example, when monitoring three queue managers, there is one instance of QPMON and three instances of QPMONSUB. Note Permission to alter WebSphere MQ objects is set by the user who starts the configuration extension. After the extension is started a user is allowed to alter any of the objects from any client connected to the TMTM Extensible Agent unless the agents or objects are secured. |
| Stop the extension. |
| List the version of the extension. |
Note
Permission to alter WebSphere MQ objects is set by the user who starts the configuration extension. After the extension is started a user is allowed to alter any of the objects from any client connected to the TMTM Extensible Agent unless the agents or objects are secured.
For information about how to secure individual agents, see Managing WebSphere MQ object security.
Comments