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



Ken, that is exactly right. No LIBL stuff in path naming, as you suggest.

But I actually tried my idea, and I don't think it will ever work. I thought I'd heard of doing it, but now I believe I was thinking of an OVRPRTF of stdout or something like that.

So someone please relieve my confusion on a Saturday!

Vern

On 5/24/2013 8:02 PM, Ken Sims wrote:
On Fri, 24 May 2013 18:07:49 -0500, Dan Kimmel
<dkimmel@xxxxxxxxxxxxxxx> wrote:

I don't have a qprint in qsys. Mine is in qgpl, too. Using qsys.lib in qsh like this just means to use the qsys file system inside root. Use the Rfile pipe as I suggested in my earlier note in this thread.
I'm pretty sure that /qsys.lib/qprint.file means to specifically look
in QSYS and that with it being in QGPL it would need to be specified
as /qsys.lib/qgpl.lib/qprint.file.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.