| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Need Help in MQ Trigger !!!! |
« View previous topic :: View next topic » |
| Author |
Message
|
| muthukumaran |
 Posted: Mon Feb 16, 2009 3:32 am Post subject: Need Help in MQ Trigger !!!! |
 |
|
Novice
Joined: 12 Feb 2009
Posts: 22
|
Hi,
Am new to MQ. am trying out the triggering mechanism in z/OS. I have defined a application queue,initiation queue and a corresponding process. The parameters that are to be given are
Application queue,
Trigger Definition
Trigger type . . . . . . . E F=First, E=Every, D=Depth, N=None
Trigger set . . . . . . . Y Y=Yes, N=No
Trigger message priority 0 0 - 9
Trigger depth . . . . . . 1 1 - 999999999
Initiation queue . . . . . SAMPLE.INIT
Process name . . . . . . . PROCESS1
Trigger data . . . . . . .
Event Control
Queue full . . . . . . . . D E=Enabled, D=Disabled
Upper queue depth . . . . D E=Enabled, D=Disabled
Threshold . . . . . . . . 80 0 - 100 %
Lower queue depth . . . . D E=Enabled, D=Disabled
Threshold . . . . . . . . 40 0 - 100 %
Service interval . . . . . N H=High, O=OK, N=None
Interval . . . . . . . . . 999999999 0 - 999999999 milliseconds
Backout Reporting
Backout threshold . . . . 0 0 - 999999999
Harden backout counter . . N Y=Yes, N=No
Backout requeue name . . .
Retention interval . . . . . 999999999 0 - 999999999 hours
Monitoring . . . . . . . . . Q Q=Qmgr, L=Low, M=Medium, H=High, O=Off
Accounting . . . . . . . . . E E=Enabled, D=Disabled, Q=Qmgr
Initiation Queue definition
Trigger Definition
Trigger type . . . . . . . N F=First, E=Every, D=Depth, N=None
Trigger set . . . . . . . N Y=Yes, N=No
Trigger message priority 0 0 - 9
Trigger depth . . . . . . 1 1 - 999999999
Initiation queue . . . . .
Process name . . . . . . .
Trigger data . . . . . . .
Process definition
Process name . . . . . . . . PROCESS1
Disposition . . . . . . . . : QMGR M1R1
Description . . . . . . . . : SAMPLE PROCESS
Application type . . . . . : MVS
Application
ID . . . : TSO SUB 'MYSELF.BATCHMQ.JCL(COBGET)'
Do i need to change any parameter's or have i missed any parameter's while defining ?
Thanks !!!! |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Feb 16, 2009 3:39 am Post subject: Re: Need Help in MQ Trigger !!!! |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| muthukumaran wrote: |
| Do i need to change any parameter's or have i missed any parameter's while defining ? |
Why are you using TRIGGER(EVERY)? This is not good practice (but not the source of your problem).
Are you sure the batch trigger monitor is running? Or are you trying to trigger a batch job via CICS (not a good idea)?
Are all the conditions for a trigger message to be raised (as laid out in the manual) being met?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 16, 2009 3:40 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Moved to correct (or more correct) section.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| muthukumaran |
| Posted: Mon Feb 16, 2009 3:41 am Post subject: |
|
|
Novice
Joined: 12 Feb 2009
Posts: 22
|
Adding to the above statements,
I tried to put a message in my appln queue. i was successful in doing that and my queue depth is also increasing.
But nothing is getting initiated. Plzzz help me out !!!
Thanks... |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 16, 2009 3:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| muthukumaran wrote: |
Plzzz help me out !!!
|
Doing my best! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| muthukumaran |
| Posted: Mon Feb 16, 2009 3:50 am Post subject: |
|
|
Novice
Joined: 12 Feb 2009
Posts: 22
|
Are you sure the batch trigger monitor is running?
I dont know much abt the trigger monitor part.
Is it anything like separate address space which should run along with MSTR and CHIN address spaces ? or .... |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 16, 2009 4:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| muthukumaran wrote: |
I dont know much abt the trigger monitor part.
|
This is going to make it trickier to get triggering working! 
Look here, also review the conditions for triggering in the same document.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Feb 16, 2009 2:08 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
What you are trying to do can't be done. You can't execute a TSO command from a MQ address space like that.....which is what I suspect you are trying to do.
You will need a trigger monitor program (there is a support pack out there which I am told is pretty flexible), alternatively you will need to roll your own.
It (MQ) is not generating a trigger message because you do not have anything monitoring the queue. We know this because 'out of the box' on z/OS MQ doesn't have one. It (MQ) will trigger a channel out of the box, but nothing else.
If you are only wanting to submit a job then I think the support pack will do this for you, but we don't use it here so I may be wrong on that.
Hope this helps |
|
| Back to top |
|
|
| zhiliyang |
| Posted: Fri Feb 20, 2009 1:59 am Post subject: |
|
|
Newbie
Joined: 20 Feb 2009
Posts: 3
|
Dear all, good night.
I met the same question with muthukumaran: I want to trigger a batch job on mainframe.
And I have started the monitor from CICS like:CKQC STARTCKTI INITATION.QUEUE.NAME. But there was not any response from MF when I to check log after a message successfully received. I don't know where the problem is, reside in Application type and Application ID setting of processor or somewhere else.
Could you do me a favor, Thanks. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 20, 2009 2:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zhiliyang wrote: |
| I met the same question with muthukumaran: I want to trigger a batch job on mainframe. |
There's been a lot of discussion lately about if this is actually a good idea.
| zhiliyang wrote: |
| I don't know where the problem is, reside in Application type and Application ID setting of processor or somewhere else. |
Given you've told us nothing about how you've defined your application, your triggering set up or used the CICS monitor to trigger a batch task we're not going to know where the problem is either.
| zhiliyang wrote: |
| Could you do me a favor, Thanks. |
Sure. Try thinking about what you're doing, read the manuals sections on triggering and z/OS administration, verify you've got everything set up in accordance with the manuals and especially that the conditions for triggering are being met.
If your problem persists, post again but with a bit more information than "I tried this, it's not working, tell me what's wrong".
There's a good sticky in the "New to Websphere" section you could read.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Feb 20, 2009 2:59 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Mainframe designs need to be done by experienced mainframe people - at least in a supervisor capacity. Otherwise the prospects are scary!
My advice - if you want immediate processing - use a CICS application program started by the CICS trigger monitor.
If you want occasional processing - schedule a batch job to run at intervals (it won't really matter if the queue is empty).
Trying to make batch processing handle messages immediately on demand is just the wrong model.
Alternatively run the application all the time, keeping an MQGET with WAIT on the queue. |
|
| Back to top |
|
|
| zhiliyang |
| Posted: Sun Feb 22, 2009 6:29 pm Post subject: |
|
|
Newbie
Joined: 20 Feb 2009
Posts: 3
|
Dear Vitor and zpat, thanks for your help.
I created a QL named to be exam.disLocalQueue, its Initation queue is EXAM.TEST.TRIGER.INI and process is exam.triger.pro. I start the trigger monitor under CICS like CKQC STARTCKTI EXAM.TEST.TRIGER.INI.
The properties of queues and process are defined to be:
Display a Local Queue - 1
Press F8 to see further fields, or Enter to refresh details.
More: +
Queue name . . . . . . . . . exam.disLocalQueue
Disposition . . . . . . . . : QMGR WMQA
Description . . . . . . . . : receive queue for cobol
Put enabled . . . . . . . . : Y Y=Yes, N=No
Get enabled . . . . . . . . : Y Y=Yes, N=No
Usage . . . . . . . . . . . : N N=Normal, X=XmitQ
Storage class . . . . . . . : DEFAULT
CF structure name . . . . . :
Dynamic queue type . . . . : N N=Non-dynamic (Predefined), T=Temporary,
P=Permanent, S=Shared
Page set identifier . . . . : 4
Use counts - Output . . . . : 1 Input . . . . : 0
Current queue depth . . . . : 5
Cluster name . . . . . . . :
Cluster namelist name . . . :
Default bind . . . . . . . : O O=Open, N=Notfixed
Cluster workload rank . . . : 0 0 - 9
Cluster workload priority . : 0 0 - 9
Cluster workload queue use : Q A=Any, L=Local, Q=Qmgr
Tpipe names . . . . . . . . : CSQ0005C CSQ8005C
Default persistence . . . . : N Y=Yes, N=No
Default priority . . . . . : 0 0 - 9
Message delivery sequence . : P P=Priority, F=FIFO
Permit shared access . . . : N Y=Yes, N=No
Default share option . . . : E E=Exclusive, S=Shared
Index type . . . . . . . . : N N=None, M=MsgId, C=CorrelId, G=GroupId,
T=MsgToken
Maximum queue depth . . . . : 999999999 0 - 999999999
Maximum message length . . : 4194304 0 - 104857600
Trigger Definition
Trigger type . . . . . . : E F=First, E=Every, D=Depth, N=None
Trigger set . . . . . . : Y Y=Yes, N=No
Trigger message priority : 0 0 - 9
Trigger depth . . . . . : 1 1 - 999999999
Initiation queue . . . . : EXAM.TEST.TRIGER.INI
Process name . . . . . . : exam.triger.pro
Trigger data . . . . . . :
Event Control
Queue full . . . . . . . : E E=Enabled, D=Disabled
Upper queue depth . . . : D E=Enabled, D=Disabled
Threshold . . . . . . . : 80 0 - 100 %
Lower queue depth . . . : D E=Enabled, D=Disabled
Threshold . . . . . . . : 40 0 - 100 %
Service interval . . . . : N H=High, O=OK, N=None
Interval . . . . . . . . : 999999999 0 - 999999999 milliseconds
Backout Reporting
Backout threshold . . . : 0 0 - 999999999
Harden backout counter . : N Y=Yes, N=No
Backout requeue name . . :
Retention interval . . . . : 999999999 0 - 999999999 hours
Monitoring . . . . . . . . : Q Q=Qmgr, L=Low, M=Medium, H=High, O=Off
Accounting . . . . . . . . : Q E=Enabled, D=Disabled, Q=Qmgr
Creation time . . . . . . . : 2009-02-16 13.29.44
Last alteration time . . . : 2009-02-19 15.54.01
Display a Local Queue - 1
Press F8 to see further fields, or Enter to refresh details.
More: +
Queue name . . . . . . . . . EXAM.TEST.TRIGER.INI
Disposition . . . . . . . . : QMGR WMQA
Description . . . . . . . . : System channel initiation queue
Put enabled . . . . . . . . : Y Y=Yes, N=No
Get enabled . . . . . . . . : Y Y=Yes, N=No
Usage . . . . . . . . . . . : N N=Normal, X=XmitQ
Storage class . . . . . . . : SYSVOLAT
CF structure name . . . . . :
Dynamic queue type . . . . : N N=Non-dynamic (Predefined), T=Temporary,
P=Permanent, S=Shared
Page set identifier . . . . :
Use counts - Output . . . . : 0 Input . . . . : 1
Current queue depth . . . . : 0
Cluster name . . . . . . . :
Cluster namelist name . . . :
Default bind . . . . . . . : O O=Open, N=Notfixed
Cluster workload rank . . . : 0 0 - 9
Cluster workload priority . : 0 0 - 9
Cluster workload queue use : Q A=Any, L=Local, Q=Qmgr
Tpipe names . . . . . . . . : CSQ0005F CSQ8005F
Default persistence . . . . : Y Y=Yes, N=No
Default priority . . . . . : 5 0 - 9
Message delivery sequence . : F P=Priority, F=FIFO
Permit shared access . . . : Y Y=Yes, N=No
Default share option . . . : E E=Exclusive, S=Shared
Index type . . . . . . . . : N N=None, M=MsgId, C=CorrelId, G=GroupId,
T=MsgToken
Maximum queue depth . . . . : 999999999 0 - 999999999
Maximum message length . . : 4194304 0 - 104857600
Trigger Definition
Trigger type . . . . . . : N F=First, E=Every, D=Depth, N=None
Trigger set . . . . . . : N Y=Yes, N=No
Trigger message priority : 0 0 - 9
Trigger depth . . . . . : 1 1 - 999999999
Initiation queue . . . . :
Process name . . . . . . :
Trigger data . . . . . . :
Event Control
Queue full . . . . . . . : E E=Enabled, D=Disabled
Upper queue depth . . . : D E=Enabled, D=Disabled
Threshold . . . . . . . : 80 0 - 100 %
Lower queue depth . . . : D E=Enabled, D=Disabled
Threshold . . . . . . . : 40 0 - 100 %
Service interval . . . . : N H=High, O=OK, N=None
Interval . . . . . . . . : 999999999 0 - 999999999 milliseconds
Backout Reporting
Backout threshold . . . : 0 0 - 999999999
Harden backout counter . : N Y=Yes, N=No
Backout requeue name . . :
Retention interval . . . . : 999999999 0 - 999999999 hours
Monitoring . . . . . . . . : Q Q=Qmgr, L=Low, M=Medium, H=High, O=Off
Accounting . . . . . . . . : Q E=Enabled, D=Disabled, Q=Qmgr
Creation time . . . . . . . : 2009-02-19 15.53.11
Display a Process - 1
Press F8 to see further fields, or Enter to refresh details.
More: +
Process name . . . . . . . . exam.triger.pro
Disposition . . . . . . . . : QMGR WMQA
Description . . . . . . . . :
Application type . . . . . : MVS
Application
ID . . . : TSO SUB 'GDC272.COBOL.JCL(DYNMAN1R)'
User data . . . . . . . . . :
Environment data . . . . . :
Last alteration time . . . : 2009-02-23 09.28.25
Last alteration time . . . : 2009-02-19 15.53.11
And I have tried to fill in the Application ID like:
GDC272.COBOL.JCL(DYNMAN1R),
'GDC272.COBOL.JCL(DYNMAN1R)',
SUB 'GDC272.COBOL.JCL(DYNMAN1R)'
but there is still no response from the Mainframe.
Can you help me to check where the problem lies in. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Sun Feb 22, 2009 11:03 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
What Batch Trigger Monitor are you using? Are you sure, it can handle this command?
| Quote: |
Application
ID . . . : TSO SUB 'GDC272.COBOL.JCL(DYNMAN1R)' |
If you like to hear another recommendation, do not mix uper / lower case definitions. Most shops use only upper case, as all objekt definitions are case sensitive.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| zhiliyang |
| Posted: Sun Feb 22, 2009 11:10 pm Post subject: |
|
|
Newbie
Joined: 20 Feb 2009
Posts: 3
|
Thank you Mr Butcher, I will pay attention to this issue.
And can you help me to figure out the problem in this trigger case?  |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Sun Feb 22, 2009 11:14 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
?!? if your trigger monitor is not able to handle the "TSO SUB" command then this seems to be your case. except i do not like your trigger every your definitions seem to be fine, and the initiation queue is open for input, so a put to the application queue should create a trigger message, that should be handled by the trigger monitor.
did you try it? did you check the log of the trigger monitor? again: which trigger monitor are you using and is that trigger monitor able to handle a TSO SUB command?
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
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
|
|
|
|
