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 » Mainframe, CICS, TXSeries » Variation in Using MA12 Example MQ Batch Trigger

Post new topic  Reply to topic Goto page Previous  1, 2
 Variation in Using MA12 Example MQ Batch Trigger « View previous topic :: View next topic » 
Author Message
zpat
PostPosted: Fri Jul 31, 2009 7:16 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

There a new trigger monitor support pac (MA10) using REXX on z/OS, which if I had a mainframe I would be looking at..

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24022461&loc=en_US&cs=utf-8&lang=en
Back to top
View user's profile Send private message
rtsujimoto
PostPosted: Fri Jul 31, 2009 9:56 am    Post subject: Reply with quote

Centurion

Joined: 16 Jun 2004
Posts: 119
Location: Lake Success, NY

I've developed my own batch trigger monitor, using MA12 as a reference. It's been running for over 10 years without any problems, so I don't understand the criticism that it's more trouble than it's worth. Aside from that, I have one suggestion. Undoubtedly, whoeve imposed this requirement on you to use MA12 as a mechanism for submitting batch jobs (via Control-M, or whatever), there's a fair chance that you might be asked to support some other task via MA12 in the future. So, my suggestion is to design your batch trigger monitor so that it can "launch" any arbitrary job. I used the Application ID ins a process definition as a key into a table, which then allowed me to submit the job associated with that key. It's pretty straightforward. Beyond that, you can get as fancy as you want, e.g. develop an interface to the batch trigger monitor to do things such as dynamically loading a new table, disable the submission of a particular job, display statistic, and so forth. Good luck.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Jul 31, 2009 12:08 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.

Compared to UNIX and Windows, triggering on z/OS is a bit more tricky. There are a variety of ways to launch work on MVS: started task, batch JCL submitted to JES, CICS, IMS. Much simpler on UNIX and Windows where there is really only one way.

Automation software can watch for events such as a message to the op console, or a dataset being created. My favorite is a message to op console.

The triggered app sends a message (WTO macro or equivalent). The content of the message varies by the application queue attributes or process attributes or trigger monitor app.

I suspect that there already exceptions to the rule that Control-M is the only way jobs get launched...
_________________
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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » Variation in Using MA12 Example MQ Batch Trigger
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.