Re: QZHQSSRV jobs

["Michael Ryan" <michaelrtr@xxxxxxxxx>]

I do that sort of thing by having one receiving data queue that all the
clients send to, and multiple data queues that the server responds to the
client. I have the client create the data queue (if it doesn't already
exist), and pass the name of that queue to the server. The data queue name
is usually based on the client job number.

On 4/11/06, David Gibbs <david@xxxxxxxxxxxx> wrote:
>
> Justin Taylor wrote:
> > I see what you are saying.  One batch job communicating with the
> > interactive jobs using two data queues.  The interactive job writes to
> > the first data queue and reads from the second, while the batch job does
> > the reverse.
>
> Something like that ... yes ... you can use keyed data queues if you
> need to differentiate the responses based on the requester.
>
> david
> --
> Any decision, made in haste, is invariably flawed...
> regardless of the outcome.
> --
> This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
> mailing list
> To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
>
>