I am wondering how many, if any, other companies set up MQ applications as started tasks on OS/390? We have several very high volume (up to 3-4 million messages a day) applications. For these applications it does not make sense to use CICS. A batch job is long running and takes up an initiator.
Doing this presents some small hurdles. Instead of writing a command interface we will be putting a high priority message in the queue to shut it down. We will have our automation tool start the task up.
Has anyone else implemented a solution like this? How do other companies handle large volume real time messaging on OS/390? _________________ Jason Adams
IBM Certified Specialist MQSeries
Posted: Mon Aug 05, 2002 1:51 pm Post subject: os 390 support
Newbie
Joined: 05 Aug 2002 Posts: 9 Location: US
Hi Adams
I have implemented similar kind of architecture with very high volumn messages. There is absolutely no problem in using CICS for real time system handling for these many messages.
I am just listing down varoius approch which you can adopt for OS/390 using CICS.
1. Can have more then one CICS region to handle the volumn.
2.have a listner process running on your CICS which just takes the messages from MQ and writes it to some file or database. Don't let this process hlod message for very long time. Then define another process which takes this message from database or file. This arch has procved to be great sucess for our project.
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