Mainframes continue to be relevant due to their stability and ability to handle large data. They can interact with other technologies like Java and .NET through message queuing (MQ) as a mediator for data transfer. The process flow involves three layers - a frontend built on technologies like SharePoint, a backend on mainframes interacting with databases, and a web services layer transmitting requests between the frontend and backend via MQ. Requests are placed in MQ queues to trigger transactions that access databases, with responses returned in the same manner. While mainframes are an older technology, they remain necessary due to their dependability.

1. Emerging trends in Mainframes - Interaction with MQ
By Sriramachandra Murthy K, Supply Chain Management
Someone askedme once “how do these banks and financial institutions maintain the data from so
manyyears?” We knowthe answer,don’twe?Mainframes beingone of the oldest systems of time,
givesthe edge over other systems to do so, and DB2 adds spice to it. Even though there are a lot of
new technologies, versions evolving in this competitive world, mainframes sustained because of
theirstabilityand the capability to handle large data. Not only that, but it has many other features
whichmakesthe “blackscreenthing”still interesting.One such feature is to interact with the other
technologies around like JAVA, .NET, Share point etc. Mainframes use the MQ as the mediator to
interact with them and even transfer data. This article focuses on how the transfer happens at
different phases.
Process Flow:
Let usdivide thisintothree layers.Firstthe frontend,whichwill be builton Share point/.NET/JAVA.
The back endwhich takes the responsibility to interact with the database (can be DB2/IMS) will be
on mainframes. Last but not the least, the third layer will be built on web services (someone to
interact with the middle ware and MQ at the same time). Web Services part is to act like a
transmitter.Itreceivesthe request(to access data) from front end through MQ, passes the request
to back end (through MQ).
Once the Web services places the request in the MQ, it will trigger a transaction. This transaction
calls a common driver module (A program written in COBOL language to interact with MQ alone).
Thisin turncallsthe applicationspecificdrivers(whichrunthe application),Service Managers(which
decides on the type of request), Service Modules (which interacts with the DB2 database to fetch
data).
The return flowhappensinthe same way. Once the back end driver receives all the information, it
will be keptinthe MQ output(upload) queue. Then the web services pass the same on to the front
end. In this way, the process flow gets completed.

2. Conclusion:
People starteddoubtingthe relevance of mainframesintoday’sworld,withothertechnologies
supposedlygaininganedge overthem.Mainframeswill continue tobe inthe reckoninginthe
foreseeable future,eventhoughitisthe oldesttechnologytobe usedtill date.Itistime forus to
buckle upand start believinginsomethingwhichwe greatlydependon.Itisnota trendto follow,
but a necessitytolive with.Thisisjustthe beginning!
***