[Info-vax] MQ series client support AST?

[GerMarsh]

On 11 Dec, 16:35, Hein RMS van den Heuvel <heinvandenheu... at gmail.com>
wrote:
> On Dec 11, 9:56 am, rockdale <rockdale.gr... at gmail.com> wrote:
>
> > In a while
> > loop, I do mqget, if returns data then process the data , if nothing
> > returns, sleep 1 sec do mqget again...
>
> And have yo considered adding that 1 second timeout to the MQget call
> as a param instead?
> You probaly should, but I admit to not reading the further description
> carefully enough to help decide.
> This will give more prompt response!
> And you may increase the timeout to reduce the overhead without losing
> promptness.
>
> > My application major task is to transmit messages between two systems
> > (let's call them MQ server and system B), MQ server have 2 queues,
> > one
> > for my application read from, another one is for my application write
> > to. My application read a message from MQ server, process the
> > message,
> > send this message to system B via tcp/ip socket connection. At the
> > same time, when my application receive a message from system B via
> > tcp/
> > ip socket(here we are using sys at qio and ast), my appl process the
> > message and then put(mqput) it into the MQ server.
>
> And this is from one process?
> What is the value / need to use a single process?
> Why not have a separate PRODUCER and a CONSUMER process and have them
> talk (mutex?) if need be?
>
> fwiw,
> Hein

We never had any problem GETting from a queue and waiting there on
most MQ programs.

However, a third party MQ interface, which does use AST's, had some
real hassle. It was sorted out with:

$ THREADCP/ENABLE=UPCALLS <image>

Here's the original thread:
http://groups.google.co.uk/group/comp.os.vms/browse_thread/thread/eda073e77f05d0fe/22d1ba14fd268f98?hl=en&lnk=gst&q=upcalls#