| Author |
Message
|
| opmind |
 Posted: Thu Sep 15, 2005 7:56 am Post subject: Starting STRMQMTRM from MQ V6 OS400 Service ? |
 |
|
Acolyte
Joined: 04 Dec 2001
Posts: 68
|
Hello there,
I tried to implement a start of trigger monitor from New MQ v6 fonction, such as :
Name : TriggerMonitor
Start Command : STRMQMTRM
Args : INITQNAME(SYSTEM.DEFAULT.INITIATION.QUEUE) MQMNAME(A0QMS)
Apply, ok ...
But when I try to start : AMQ4056
Did someone tried it ? and run it ?
Cyril |
|
| Back to top |
|
 |
| wschutz |
| Posted: Thu Sep 15, 2005 8:01 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
I've done it on unix, but not the /400. Is there anything useful in the /400 mq log?
_________________
-wayne |
|
| Back to top |
|
|
| opmind |
| Posted: Thu Sep 15, 2005 8:07 am Post subject: |
|
|
Acolyte
Joined: 04 Dec 2001
Posts: 68
|
Yep it says it can't find the command ... But it's like that we start trigger monitor under OS/400 through command  |
|
| Back to top |
|
|
| tanglp |
| Posted: Mon Jun 20, 2011 10:28 pm Post subject: |
|
|
Newbie
Joined: 02 Jun 2011
Posts: 5
|
Anyone can help me on this as I'm facing the same situation.
I'm able to start the Trigger Monitor program manually via STRMQMTRM but when I specify it to start thru STRMQMSVC, it says it could not find the STRMQMTRM. I even specified the lib QMQM but to no avail: -
AMQ5019: Unable to access program 'QMQM/STRMQMTRM'.
EXPLANATION:
Cause . . . . . : A request was made to execute the program QMQM/STRMQMTRM,
however the operation was unsuccessful because the program could not be found
in the specified location.
Recovery . . . : Check the definition of the service specifies the correct
and full path to the program to run. If the path is correct then verify that
the program exists in the specified location and that WebSphere MQ userid has
permission to access it. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Tue Jun 21, 2011 12:22 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
You could have posted the same as New Thread (where OLD Post/Link could be taken as reference).
Please check link Hope that would be helpful.
Please do check your 'Permissions' !!
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| tanglp |
| Posted: Tue Jun 21, 2011 7:08 pm Post subject: |
|
|
Newbie
Joined: 02 Jun 2011
Posts: 5
|
| Thanks Shashi. But can you clarify why so? |
|
| Back to top |
|
|
| tanglp |
| Posted: Tue Jun 21, 2011 7:27 pm Post subject: |
|
|
Newbie
Joined: 02 Jun 2011
Posts: 5
|
Thanks again Shashi. I've read the link you provided.
Looks like AS/400 is a different kettle of fish. So basically I have to configure the MQ service using CALL PGM(QMQM/RUNMQTRM) PARM(X'6098E2E8E2...) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 21, 2011 9:19 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Can somebody clear up this for me? I thought that on AS400 like on zOS you uses CKT? to run as trigger monitor? Am I completely mistaken here? Is this only a trigger monitor for use with CICS?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jun 22, 2011 3:40 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
CKTI is the CICS trigger monitor.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| colbype |
| Posted: Wed Jun 22, 2011 12:55 pm Post subject: |
|
|
Novice
Joined: 13 Jan 2009
Posts: 23
|
It looks to me like it wants a program and not a *CMD which is why it is telling you it can not find it. It is looking for type *PGM instead of CMD.
I worked with this once before and you can drop it into a CL and then call the CL program. The last time I tried this I had horrible results as certain parms of the MQ commands it did not like being variables and would give crazy results.
I finally gave up on it and just put it in the scheduler after MQ starts.
From the AMQZMGR0 joblog
Unable to start program 'QSYS/DSPMQMVER' |
|
| Back to top |
|
|
|
|
