• Subject: Re: Routing Batch IBM Queries to Separate JOBQ
  • From: email@xxxxxxxxxxxxxxxxxxx (James W Kilgore)
  • Date: Thu, 18 Mar 1999 20:44:06 -0800
  • Organization: Progressive Data Systems, Inc.


Let's see if I have this straight.

For in-house queries you would write a wrapper to perform routing, but
for the canned product you need some form of control not currently

If that's a fair assessment, how about writing your own RUNQRY command
that the canned product gets run through?

Now having said that, to introduce a library above QSYS to do a run
around the OS supplied commands does require a bit of attention to
security measures.

Personally and professionally, I'm going to have to give a two thumbs
down.  The first for an application provider using query as a processing
solution (instead of a -real- program) and the second for not allowing a
user controllable method of management for their selected choice of
solution.  Had they tied each query to a job description, you would at
least be able to tweak the job description to suit your needs.  Better
than nothing IMHO.


"William N. Harrell, Jr." wrote:
> We are trying to find a way to route user's queries to a
> special JOBQ.
> <<snip>>
> Our problem is that our primary AS400 Business Application
> submits various jobs for our users with the same Job Name,
> so we are unable to differentiate the queries, unless we do a
> display job on the job log on the job waiting to run.
> Any suggestions ?
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].