| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| program mentioned in program id of the trigger data is not |
« View previous topic :: View next topic » |
| Author |
Message
|
| cicsprog |
 Posted: Fri May 25, 2012 7:08 am Post subject: |
 |
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
We took the SupportPac mentioned and added it to the xxxMSTR, xxxxCHIN, and now xxxTRIG to make it an MQ trilogy. When the trigger fires we write a message to the MVS SYSTEM log and have ESP react upon the console message to start a batch job. EasyPIZy.
Many variations are possible. I'm sure many vendor scheduling packages have an API that could be used I'd guess. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri May 25, 2012 7:21 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| cicsprog wrote: |
We took the SupportPac mentioned and added it to the xxxMSTR, xxxxCHIN, and now xxxTRIG to make it an MQ trilogy. When the trigger fires we write a message to the MVS SYSTEM log and have ESP react upon the console message to start a batch job. EasyPIZy.
Many variations are possible. I'm sure many vendor scheduling packages have an API that could be used I'd guess. |
Your solution (WTO message trapped by automated operations software) is one of the many ways to launch work on z/OS.
Things are always more complicated on 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 |
|
|
|
|
|
|
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
|
|
|
|
