June, >>>I was thinking more along the lines of functionality, additional >>>coding requirements, DPL, etc. For our proof of concept project >>>we want to replace an application that currently accesses CICS via >>>an EXCI from a DB2 stored procedure. Currently this request goes >>>directly into an AOR. However, with our future apps, we may want >>>them to be 3270 initiated via the TOR. I guess what I am asking >>>under what will one give you that the other doesn't? Basically >>>we want to get tinto CICS and just run the existing programs.
With the MQ Bridge, the bridge itself, running as a CICS task, will get messages from a queue and invoke a DPL-complient program, just as your existing mechanism today invokes a DPL-complient program via the EXCI from a DB2 stored procedure. With the CICS/MQ Adapter, you would have to write a program to get messages from the queue, and either process those messages directly or pass the data to another program. So, with the CICS/MQ Bridge you can expose existing DPL/ECI/EXCI-invoked programs to the MQ world without change. But that's ALL you can do. With the CICS/MQ Adapter, you can do anything you want, because you get and put messages to MQ queues directly. But you have to write the code. Hope this helps. Regards, Christopher Frank Sr. I/T Specialist - IBM Software Group IBM Certified Solutions Expert - Websphere MQ & MQ Integrator -------------------------------------------- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
