ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Trigger question

Post new topic  Reply to topic
 Trigger question « View previous topic :: View next topic » 
Author Message
LouML
PostPosted: Tue Jul 31, 2007 11:05 am    Post subject: Trigger question Reply with quote

Partisan

Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY

I'm on a unix systems running mq 5.3.12

One of our developers is complaining that his program is not getting triggered. When the remote side sends a message I see that it is immediately off the queue. I assume that it's being processed but he says his program is not even starting. We've redirected the output to a log file in the APPLICID paramter on the process definition but the log file remains empty.

This is how I'm starting the trigger monitor.

bash-2.05$ nohup runmqtrm -m QM.JEDI1Q.01 -q QL.NAWORK.UPDATES.FROM.GT >/var/mqm/trig.out & [2] 7653
bash-2.05$ Sending output to nohup.out

This is the queue and process definition.

1 : dis ql(QL.NAWORK.UPDATES.FROM.GT) all
AMQ8409: Display Queue details.
DESCR(New Account Update Msgs from Goldtier)
PROCESS(PD.nuflow) BOQNAME( )
INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE)
TRIGDATA( ) CLUSTER( )
CLUSNL( ) QUEUE(QL.NAWORK.UPDATES.FROM.GT)
CRDATE(2007-06-21) CRTIME(12.33.41)
ALTDATE(2007-07-27) ALTTIME(21.45.42)
GET(ENABLED) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(NO)
MAXDEPTH(5000) MAXMSGL(4194304)
BOTHRESH(0) SHARE
DEFSOPT(SHARED) HARDENBO
MSGDLVSQ(PRIORITY) RETINTVL(999999999)
USAGE(NORMAL) TRIGGER
TRIGTYPE(FIRST) TRIGDPTH(1)
TRIGMPRI(0) QDEPTHHI(80)
QDEPTHLO(20) QDPMAXEV(ENABLED)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QSVCINT(999999999) QSVCIEV(NONE)
DISTL(NO) NPMCLASS(NORMAL)
DEFTYPE(PREDEFINED) TYPE(QLOCAL)
SCOPE(QMGR) DEFBIND(OPEN)
IPPROCS(0) OPPROCS(0)
CURDEPTH(0)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ echo "dis process('PD.nuflow') all" | runmqsc QM.JEDI1Q.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.JEDI1Q.01.


1 : dis process('PD.nuflow') all
AMQ8407: Display Process details.
DESCR( )
APPLICID(/apps/clearing/etc/nuflow/nuflowtranslator.sh > /var/mqm/pd.out)
USERDATA( ) ENVRDATA( )
PROCESS(PD.nuflow) ALTDATE(2007-07-31)
ALTTIME(14.09.31) APPLTYPE(UNIX)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$

At one point, i saw the following in the trigger monitor log file:

bash-2.05$ cat /var/mqm/trig.out
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.

__________________________________________________
Waiting for a trigger message
Trigger message with warning 2079

__________________________________________________
Waiting for a trigger message
Trigger message with warning 2079

__________________________________________________
Waiting for a trigger message
Trigger message with warning 2079

__________________________________________________
Waiting for a trigger message
bash-2.05$

Is the 2079 the reason code (MQRC_TRUNCATED_MSG_ACCEPTED)?

Any ideas?
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Jul 31, 2007 11:08 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You're telling your qmgr to write trigger messages for your ql to the INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE).

Then you're running your trigger monitor against QL.NAWORK.UPDATES.FROM.GT.

You probably want to set INITQ to something like QL.NAWORK.UPDATES.INITQ
and then run your trigger monitor against the same.

You don't want to use S.D.I.Q, for the same reason you don't want to enable SYSTEM.DEF.SVRCONN.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Nigelg
PostPosted: Tue Jul 31, 2007 10:08 pm    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

Quote:
APPLICID(/apps/clearing/etc/nuflow/nuflowtranslator.sh > /var/mqm/pd.out)

You should not redirect the output directly in APPLICID. The app is started with the trigger msg passed on the command line as an TMC2 structure, followed by the USERDATA & ENVRDATA. In this case the command line is
Quote:
nuflowtranslator.sh > /var/mqm/pd.out TMC2_structure

I doubt that will work. The proper place for the redirect is ENVRDATA.
_________________
MQSeries.net helps those who help themselves..
Back to top
View user's profile Send private message
LouML
PostPosted: Wed Aug 01, 2007 4:04 am    Post subject: Reply with quote

Partisan

Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY

How do the USERDATA and ENVRDATA on define process differ?

So I have the following now.

bash-2.05$ echo "dis ql(QL.NAWORK.UPDATES.INITQ) all" | runmqsc QM.JEDI1Q.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.JEDI1Q.01.


1 : dis ql(QL.NAWORK.UPDATES.INITQ) all
AMQ8409: Display Queue details.
DESCR(WebSphere MQ Default Initiation Queue)
PROCESS( ) BOQNAME( )
INITQ( ) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(QL.NAWORK.UPDATES.INITQ) CRDATE(2007-07-31)
CRTIME(15.36.09) ALTDATE(2007-07-31)
ALTTIME(15.36.09) GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(NO) MAXDEPTH(1000)
MAXMSGL(1000) BOTHRESH(0)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(PRIORITY)
RETINTVL(999999999) USAGE(NORMAL)
NOTRIGGER TRIGTYPE(NONE)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(80) QDEPTHLO(20)
QDPMAXEV(ENABLED) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(NO)
NPMCLASS(NORMAL) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(1)
OPPROCS(0) CURDEPTH(0)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ echo "dis ql(QL.NAWORK.UPDATES.FROM.GT) all" | runmqsc QM.JEDI1Q.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.JEDI1Q.01.


1 : dis ql(QL.NAWORK.UPDATES.FROM.GT) all
AMQ8409: Display Queue details.
DESCR(New Account Update Msgs from Goldtier)
PROCESS(PD.nuflow) BOQNAME( )
INITQ(QL.NAWORK.UPDATES.INITQ) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(QL.NAWORK.UPDATES.FROM.GT) CRDATE(2007-06-21)
CRTIME(12.33.41) ALTDATE(2007-07-31)
ALTTIME(15.34.3 GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(NO) MAXDEPTH(5000)
MAXMSGL(4194304) BOTHRESH(0)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(PRIORITY)
RETINTVL(999999999) USAGE(NORMAL)
TRIGGER TRIGTYPE(FIRST)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(80) QDEPTHLO(20)
QDPMAXEV(ENABLED) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(NO)
NPMCLASS(NORMAL) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(0)
OPPROCS(0) CURDEPTH(0)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ echo "dis ql(QL.NAWORK.UPDATES.INITQ) all" | runmqsc QM.JEDI1Q.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.JEDI1Q.01.


1 : dis ql(QL.NAWORK.UPDATES.INITQ) all
AMQ8409: Display Queue details.
DESCR(WebSphere MQ Default Initiation Queue)
PROCESS( ) BOQNAME( )
INITQ( ) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(QL.NAWORK.UPDATES.INITQ) CRDATE(2007-07-31)
CRTIME(15.36.09) ALTDATE(2007-07-31)
ALTTIME(15.36.09) GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(NO) MAXDEPTH(1000)
MAXMSGL(1000) BOTHRESH(0)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(PRIORITY)
RETINTVL(999999999) USAGE(NORMAL)
NOTRIGGER TRIGTYPE(NONE)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(80) QDEPTHLO(20)
QDPMAXEV(ENABLED) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(NO)
NPMCLASS(NORMAL) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(1)
OPPROCS(0) CURDEPTH(0)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$ echo "dis process('PD.nuflow') all" | runmqsc QM.JEDI1Q.01
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.JEDI1Q.01.


1 : dis process('PD.nuflow') all
AMQ8407: Display Process details.
DESCR( )
APPLICID(/apps/clearing/etc/nuflow/nuflowtranslator.sh)
USERDATA( ) ENVRDATA( > /var/mqm/pd.out &)
PROCESS(PD.nuflow) ALTDATE(2007-08-01)
ALTTIME(08.01.00) APPLTYPE(UNIX)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-2.05$
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 01, 2007 4:11 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

LouML wrote:
How do the USERDATA and ENVRDATA on define process differ?


They go in different places in the data supplied to the triggered application.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Aug 01, 2007 4:24 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Your setup looks beter now... Does it work? Or are you still getting the 2079 warning?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
LouML
PostPosted: Wed Aug 01, 2007 4:35 am    Post subject: Reply with quote

Partisan

Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY

jefflowrey wrote:
Your setup looks beter now... Does it work? Or are you still getting the 2079 warning?


Waiting for the developer to get in to send me a message. Will keep you posted.

Thanks again.
Back to top
View user's profile Send private message
LouML
PostPosted: Wed Aug 01, 2007 5:08 am    Post subject: Reply with quote

Partisan

Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY

Developer says it works now. Thanks for the help.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Trigger question
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.