Posted: Thu Apr 24, 2003 8:35 am Post subject: Shrinking Batch window problem - using MQ
Novice
Joined: 09 Apr 2003 Posts: 12
Hi all,
We have a z/OS mainframe shop.
I would appreciate if somebody could tell me how good is an option MQ series is to reduce the nightly Batch cycle window. I understand there are certain scenarios where you can actually get two dependent jobs to run parallely if we use MQ instead of passing Files between programs.
I would like to know if you have achieved any significant results on this and also some other scenarios in Batch where MQ could come in handy.
I guess it depends on the nature of the application and what the dependencies are. If it is purely passing data between the two jobs (and I assume that this is the case) then the advantage would be that the reading application can start at the same time (or even before!) the writing application and can start to process messages (data) while the other application is still running. If it is that both jobs are trying to update the same database then you could also have several processes dropping messages onto a queue 'at the same time' and these would then be processed by an application either later or even running concurrently.
As usual with MQSeries it really depends upon what the application needs are. and these should be based around what the business needs are.
As for a benchmark....I can't help there. We have one application that uses MQ in this way but it only queues up message during an online session for processing in batch later that evening.
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