I'm not sure if it explains your experience, but unlike batch, the CICS adapter simulates get w/wait. Remember, the adapter pools 8-or-so qmgr connections that it shares among all CICS programs. The adapter cannot afford to tie up any of those connections with a bona-fide get w/wait.
> -----Original Message----- > From: Dye, Janet E [SMTP:[EMAIL PROTECTED]] > Sent: Monday, June 24, 2002 2:24 PM > To: [EMAIL PROTECTED] > Subject: MQGET with wait in CICS > > We have noticed that when a CICS program does a MQGET with wait, that > during > the time interval that the task is waiting, that it is using a lot of CPU > resources. When I do a MQGET with wait > in a batch environment, it does not appear to be using any resources > during > the wait. Has anyone > else experienced this. For purposes of being efficient, we wait a few > seconds after a MQGET to > see if another messages arrives, in order to avoid the process being > triggered again and having to go thru the overhead of the MQOPEN/MQCLOSE. > Any suggestions? > > Janet Dye > > 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 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
