Leroy,
Since MQ is designed to be send and forget technology, and because you can have multiple listeners, there is nothing to stop you, and is, in fact, the purpose of the technology. However, remember that if you are using MQ as a means of users communicating with the database in the scenario you describe, you are using MQ as a de facto connection pool and violating your U2 license agreement if you don't have the equivalent number of U2 licenses that match the interactive users.
Thats OK, we don't do it; but thankyou for clarifying that using MQ Series in this way would violate the licence.
Can you suggest how you would ask an enterprise customer to audit licence usage in an environment where MQ series is used to connect multiple systems (only one of which is running U2) and allowing them to be queried from any system -- including systems running user interactive sessions on an AS/400 and an S/390. If they were a bank and an ATM could request or update an account balance from U2 via MQ Series do we need to include these users too?
If they has N non U2 systems each supporting M users all of which could potentially send a simultaneous MQ request to U2 as part of their application session do they need M*N licences?
Craig ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
