Re: runqry and remote outq (printing question) -- MIDRANGE-L

× 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: Re: runqry and remote outq (printing question)
From: Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>
Date: Wed, 16 Sep 2009 17:34:17 +0200
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Wed, Sep 16, 2009 at 17:10, Jack Kingsley <iseriesflorida@xxxxxxxxx> wrote:

Since you can't hardcode a remote outq in a query defintion, is the only way
to get around this using cl and ovrprtf??

You can create a *DEVD that doesn't get used with a name matching the
OUTQ. Works fine ;)

As an Amazon Associate we earn from qualifying purchases.

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