| Author |
Message
|
| sebastia |
 Posted: Wed Jun 28, 2006 2:34 pm Post subject: can CLIENT use TRIGGERING ? |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Until now, I understood the MQ Client as a method to access a Queue Manager without having a license, the installation and the maintenance.
But now it seems clear to me the MQ Client can not use TRIGERING to get control when the reply message comes back ..
Am I right ? |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Jun 28, 2006 2:39 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Why not? There's a client trigger monitor, and even a supportpac for triggering via the MQ client .
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 28, 2006 2:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Your first understanding is wrong. You don't need a license to use the MQ Client, but you do need to install it and you do need to maintain it (apply Fix Packs).
Your second understanding is also wrong. You can run a trigger monitor on the client machine, that will listen to the initiation queue and start your application. In fact, MQ comes with a client trigger monitor - called "runmqtmc" instead of "runmqtrm".
Welcome to MQ. Please read the manuals.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Jun 28, 2006 6:07 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Just for completeness.......the client has to connect to a licenced server version of a queue manager somewhere.
Also the MQ Client attach facility for z/OS isn't free....in fact it is rather expensive.  |
|
| Back to top |
|
|
| sebastia |
| Posted: Thu Jun 29, 2006 12:28 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
.
Thanks a lot to all the answers !
That is what I needed : some light, some names
to start reading again !
 ))) |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jul 05, 2006 1:19 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Jeff ... Wayne :
Supose this environment :
+++
.--------------------. .------------------------------
| | |
| pc "A" | | pc "B"
| MQ client | | MQ Server
| | |
| APP-1 ===>======>= | QMN = "QMB" ;
| | |
| APP-2.exe | | QN = "QMB_RQ" ;
| | |
.--------------------. .------------------------------
+++
This is, in machine "A", application APP1-exe sends a message,
writing it into some queue in queue manager QMB.
And expects the answer in the queue "QMB_RQ"
We want to start the application "APP-2.exe" in the machine "A".
How do we define the PROCESS associated to queue QMB_RQ ???
In the machine "A" we started the Trigger Monitor :
runmqtmc -m QMB -q SYSTEM.DEFAULT.INITIATION.QUEUE
*************************************************
What I dont understand is how do you specify c:\app-2.exe
and trigger monitor knows this "C:\" disk is on machine "A"
instead of machine "B" ! |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jul 05, 2006 1:23 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Sorry for the drawing ...
On left side there is machine "A" with MQ Client and APP-1.exe (sends) and APP-2.exe (receives).
On right side there is machine "B" with MQ Server, queue manager QMB, queue QMB_EQ, that has to start APP-2.exe when a message is written into it.
Thnx. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jul 05, 2006 2:32 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Because when you define the processes, the APPLICID must always be for the environment where you are running the trigger monitor, not where the queue manager is. Remember that its the trigger monitor that is using the process definition and issuing the SYSTEM() call to start your program. So the process definition ALWAYS applies to the environment where the trigger monitor is running.
_________________
-wayne |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jul 05, 2006 2:48 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Wayne : I dont understand this part you say ...
>> Remember that its the trigger monitor that is using the process definition
I did start the trigger monitor in the client, using
runmqtmc [-m QMgrName] [-q InitQ]
but I did not provide any process definition (to RUNMQTMC) !! |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 05, 2006 2:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sebastia wrote: |
but I did not provide any process definition (to RUNMQTMC) !! |
Process definition is a separate MQ object (item / definition / ... ) that's picked up from the triggered queue 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Jul 05, 2006 2:53 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jul 05, 2006 3:27 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Wayne : thanks for the link.
I am using the good-old "GC34-6058-01" ...
The chapter 12 is still there ...
Guess I am missing some testing !!!
() |
|
| Back to top |
|
|
|
|
