× 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.


  • Subject: Revisit Output Queue when using Query.
  • From: "Roger Vicker" <rvicker@xxxxxxxx>
  • Date: Mon, 03 Aug 1998 08:59:52 -0500
  • Organization: Vicker Programming

Some time ago there was a thread here about the OUTQ used by Query when the job
was submitted that I forgot to save.

It seems that Query uses a OUTQ(*USRPRF) or OUTQ(*JOBD) instead of the default
OUTQ(*CURRENT).
One of my customers uses several OUTQ for any given user. They do a CHGJOB
OUTQ(_____) to set the destination before submitting jobs. However when they
submit a Query from WRKQRY it usually ends up in the wrong place. This customer
is at V3R2 with the latest (maybe last?) CUM PTF. Was there a resolution to this
problem or another _mis-feature_ that they are stuck with?

TIA

Roger Vicker, CCP

--
*** Vicker Programming and Service *** Have bits will byte ***
http://www.vicker.com/vicker/vps.html ***
Most bugs are real sons of glitches.

+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.