What is it? MQSeries is a middleware product from IBM that runs on multiple platforms and enables applications to send messages to other applications. Basically, the sending application PUTs a message on a Queue, and the receiving application GETs the message from the Queue. The sending and receiving applications do not have to be on the same platform, and do not have to be executing at the same time. MQSeries takes care of all the storage, logging and communications details required to guarantee delivery of the message to the destination queue. In most cases, it will take care of translating the data when the source and destination use different character sets (EBCDIC on MVS vs. ASCII on NT or Unix). All the applications have to do is know the name of the Queue and agree on the meaning of the message.
Transferring data from mainframe systems to PC/Unix systems
Transferring data from PC/Unix systems to mainframe systems
Problem…Solution… An event in an IMS system requires action by a midrange system. Modify the IMS program to PUT a message to the midrange system. The midrange system can be configured to start the application whenever a message arrives.
An event in an midrange system requires action by a
Modify the midrange program to PUT a message to
the mainframe system. The mainframe system can
process the message :
At set intervals
On a schedule
CAD - MQ Architecture MQSEND ECS Database CAD to ECS ECS to CAD *existing ECS MPPs modified to: 1 – add XML formatting to some data 2 – MQPUT to UP incoming queue MQ MQ
New BMP, cycles every x minutes
Reads all messages from queue into buffer
Sorts on sequence number
Processes each in proper order
UP Database OG_Main_Download OF_Main_Upload MQRECV
Problem…Solution… A PC user needs to request an overnight report that needs data from IMS, DB2 and other files. A VB program puts the report requirements on a queue which is read by a batch job
Problem…Solution… Web server needs data from legacy IMS/CICS transaction. Web server puts a message to the MQ-IMS/CICS Bridge, which runs the transaction and returns the results on a queue (screen-scraping without the 3270).
Problem…Solution… VB app needs data from DB2, SQL Server and IMS VB client app puts messages on queues on NT and mainframe systems, triggering programs which populate reply queues on an NT system, which the VB app will read to present to the user. The VB client need not wait for the report to be completed. It could spawn a separate thread that would monitor the reply queues and notify the user when the report was complete.