|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Application Triggering a BATCH JCL job |
« View previous topic :: View next topic » |
Author |
Message
|
SATYAIBMMQ |
Posted: Mon Aug 25, 2025 10:33 pm Post subject: Application Triggering a BATCH JCL job |
|
|
Newbie
Joined: 25 Aug 2025 Posts: 1
|
Greetings,
I am new to this forum and new to IBM MQ need a little guidance.
Being a ZOS developer, i am doing self learn on MQ , renting a USERID for practice.
I want to execute a batch JCL job thru application trigger.
Following are the steps i followed but failed to execute the Batch JCL
DEFINE QL(SBI.APPTRIG) <= successful
*
ALTER QL(SBI.APPTRIG) TRIGGER TRIGTYPE(FIRST) +
INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE) +
PROCESS(SBI.PROCESS) <= successful
*
DIS QL(SBI.APPTRIG) <= tried to see the Queue, <= successful
*
DEFINE PROCESS(SBI.PROCESS) APPLICID('XXXXXXX.TEST.JCL(IEBGEN)')
APPLTYPE(MVS) <= successful
*
My trigger JCL is not executing when i put message on SBI.APPTRIG.
I am putting message thru JCL.
Regards All. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Aug 26, 2025 3:11 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9481 Location: US: west coast, almost. Otherwise, enroute.
|
What trigger monitor application (see midrange runmqtrm) are you using to submit the JCL to JES? There was a support pac MA12 that provided that service on MQ 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 |
|
 |
hughson |
Posted: Wed Aug 27, 2025 2:49 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1966 Location: Bay of Plenty, New Zealand
|
If those are literally all the steps you did, then you are missing a trigger monitor.
A trigger monitor is an application that reads the initiation queue - I can see that you have defined the queue, but I am guessing you have nothing reading from it.
As noted, the only batch trigger monitor is the withdrawn MA12 support pac. However, you can grab a copy from here: https://community.ibm.com/community/user/discussion/zos-batch-trigger-monitor
Your process definition will probably need a change to match the format expected by the batch trigger monitor if you decide to use it. RUNDEFS job in the zip file has examples.
Cheers,
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Aug 27, 2025 7:40 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9481 Location: US: west coast, almost. Otherwise, enroute.
|
Or, you can write your own trigger monitor that MQGETs the trigger event message, and then submits the named jobstream off to JES.
Midrange runmqtrm source is provided in samples directory. _________________ 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 |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|