| Author |
Message
|
| imrakesh |
 Posted: Thu Apr 26, 2012 11:13 am Post subject: program mentioned in program id of the trigger data is not |
 |
|
Novice
Joined: 10 Apr 2012
Posts: 10
|
program mentioned in program id of the trigger data is not getting auto triggered.
Hi,
I created a LQ in mainframe and i did create a Initiation queue, process
. Provided the process name and trigger data but the app team says the program which is mentioned in the program id of trigger data is not getting auto triggered.
Any one can help ? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Apr 26, 2012 11:35 am Post subject: Re: program mentioned in program id of the trigger data is n |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| imrakesh wrote: |
| Any one can help ? |
Not from the little information you've posted no.
How do you know it's not being triggered? How do you know (by which I mean what steps have to taken to determine that) the program is not being triggered and immediately abending?
How do you know (same proviso) that the trigger's fireing? How do you know that the trigger condition's being met?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Apr 26, 2012 12:45 pm Post subject: Re: program mentioned in program id of the trigger data is n |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| imrakesh wrote: |
program mentioned in program id of the trigger data is not getting auto triggered.
Hi,
I created a LQ in mainframe and i did create a Initiation queue, process
. Provided the process name and trigger data but the app team says the program which is mentioned in the program id of trigger data is not getting auto triggered.
Any one can help ? |
When you refer to mainframe, do you mean WMQ on z/OS? Or z/Linux?
Are you a z/OS support person?
z/OS is different. WMQ on z/OS is different. There is no equivalent to the midrange runmqtrm supplied program. There are many types of work in z/OS: batch, CICS, IMS.
Exactly what is supposed to be triggered? Is this something new?
_________________
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 |
|
|
| imrakesh |
| Posted: Thu Apr 26, 2012 2:07 pm Post subject: |
|
|
Novice
Joined: 10 Apr 2012
Posts: 10
|
| I am talking about WMQ on z/OS |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Apr 26, 2012 4:24 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Please answer all questions you are asked.
Are you a z/OS support person? Or just the WMQ admin person?
z/OS is different. WMQ on z/OS is different. There is no equivalent to the midrange runmqtrm supplied program. There are many types of work in z/OS: batch, CICS, IMS.
Exactly what is supposed to be triggered? A batch job? A CICS transaction? Something else?
Is this a new app?
_________________
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 |
|
|
| imrakesh |
| Posted: Thu Apr 26, 2012 4:40 pm Post subject: |
|
|
Novice
Joined: 10 Apr 2012
Posts: 10
|
Sorry I tot i responded but my page crashed
Are you a z/OS support person? Or just the WMQ admin person?
I am a just MQ admin and new to Mainframe MQ
z/OS is different. WMQ on z/OS is different. There is no equivalent to the midrange runmqtrm supplied program. There are many types of work in z/OS: batch, CICS, IMS.
Exactly what is supposed to be triggered? A batch job? A CICS transaction? Something else?
This is what i have given
Trigger data . . . . . . : USER-ID=OAKAMS01 PGM-ID=EMCMMQ01
CV-DESIG=AM READY=U TRAN=USQA-Y
Based on the above they r not getting the program id of the trigger data |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 26, 2012 6:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you possibly trying to get a batch program triggered by a CICS trigger monitor? I thought CICS transactions were mostly identified by 4 alpha numeric chars...
Have fun and please, please talk to your friendly zOS admin.
They will help you get some understanding and struggle with you to fix the problem. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| elkinsc |
| Posted: Wed May 23, 2012 7:04 am Post subject: Please see the Batch Trigger Monitor SupportPac MA12 |
|
|
Centurion
Joined: 29 Dec 2004
Posts: 138
Location: Indy
|
| There is no batch trigger monitor built into WMQ for z/OS: the JCL needed to initiate the jobs is unique to the program being run. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 23, 2012 7:13 am Post subject: Re: Please see the Batch Trigger Monitor SupportPac MA12 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| elkinsc wrote: |
| There is no batch trigger monitor built into WMQ for z/OS |
Really? I thought there was a way to start a JCL proc rather than a CICS task when a message showed up on a queue in z/OS.
Obviously the JCL is (as you correctly say) unique for the batch program.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 23, 2012 8:38 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
No. There really is no equivalent to runmqtrm in WMQ for z/OS.
_________________
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 |
|
|
| Vitor |
| Posted: Wed May 23, 2012 8:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| No. There really is no equivalent to runmqtrm in WMQ for z/OS. |
Clearly the caffine has got to my memory.
You could (quite) easily write one. But to circle back to the OP, you certainly can't start a batch job from a CICS task without considerable dancing.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 23, 2012 9:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bruce2359 wrote: |
| No. There really is no equivalent to runmqtrm in WMQ for z/OS. |
well.... |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed May 23, 2012 9:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| bruce2359 wrote: |
| No. There really is no equivalent to runmqtrm in WMQ for z/OS. |
well.... |
Hah! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 23, 2012 9:31 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Vitor wrote: |
| mqjeff wrote: |
| bruce2359 wrote: |
| No. There really is no equivalent to runmqtrm in WMQ for z/OS. |
well.... |
Hah! |
Hah! if you like...
In UNIX and Windoze, there is really only one way to launch work - thus a single trigger monitor app (runmqtrm) suffices.
In z/OS, work can be started with JCL submitted to JES, operator start command (STC), IMS transaction or app, CICS transaction or app, UNIX System Services... How this work is started varies.
MA12 offers an example of a z/OS batch 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 |
|
|
| Vitor |
| Posted: Wed May 23, 2012 9:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Hah! if you like... |
I'm just pleased my recollection of triggering batch jobs when messages arrived is based in some sort of fact.
| bruce2359 wrote: |
In UNIX and Windoze, there is really only one way to launch work - thus a single trigger monitor app (runmqtrm) suffices.
In z/OS, work can be started with JCL submitted to JES, operator start command (STC), IMS transaction or app, CICS transaction or app, UNIX System Services... How this work is started varies. |
It's an architetural fact that z/OS offers multiple interfaces.
| bruce2359 wrote: |
| MA12 offers an example of a z/OS batch trigger monitor. |
Well runmqtrm is a example. It's a really good example & you're need significant justification to change it, but it's not immutable.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
