That's a challenge, but there are some thoughts.

a) Are you sure the CICS transaction is releasing any buffers etc returned
from the
DB calls after it's passed then info back to the batch program?
Or are they just piling up in storage.

b) Are you firing hundreds (or thousands) EXCI at the CICS region without
some
form of throttling?
Why use EXCI at all - just invoke the DL/I code to read the DB directly from
the
batch application.

c) Why use MQCONN/MQPUT1/MQDISC.   Why not MQCONN and MQOPEN the output
queue
as the application, MQPUT each message as you go (with occasional commits
if you feel the need), and MQCLOSE and MQDISC when you're done.   If nothing
else
your application will perform a whole lot better this way.   I am assuming
it is the batch
program that is doing the MQI calls - is that right?

David

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

Reply via email to