×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
It's about a horse apiece; no real discernable difference as far as the
system is concerned since there are so few instances of the message to
process. The biggest difference is the QMHRCVM loop will drive quite a bit
more I/O than the queues do. That's what would tip it in favor of the
Message Queue APIs in my view.
In the end the message queue API's would win out over the QMHRCVM loop but
I'm not sure it's a large enough difference to matter much.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
dlclark@xxxxxxxxxxxxxxxx
Sent: Monday, August 01, 2016 12:03 PM
To: Midrange Systems Technical Discussion
Subject: Re: Who killed me?
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 08/01/2016
12:06:58 PM:
Thanks, I implemented a QMHRCVM loop on QSYSOPR.
Is that more efficient that using a message queue list? I'm
currently using the message queue list API's for those two messages so I
was curious which method is more efficient?
Sincerely,
Dave Clark
midrange.com
