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



I disagree...

IMHO, using QPRINT is just lazy...and unacceptable in a production application.

Is it really that hard to do CRTPRTF (MYLIB/MYPRTF) so that you don't
have to worry about what might have been done to QPRINT?

Charles

On Tue, Aug 24, 2010 at 2:13 PM, Morgan, Paul <Paul.Morgan@xxxxxxxxxxx> wrote:
James,

As long as nothing else is running between the OVRPRTF and when you delete the override & created spool file you're safe.  Creating your own print file would be overkill.  If your process is mixed in with other things (called from somewhere, calling something else or maybe using the attention key) then a different print file with a hold override on that print file might be appropriate.  There is no reason for an output queue.

Paul

Principal Programmer Analyst
IS Supply Chain/Replenishment


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Tuesday, August 24, 2010 1:49 PM
To: Midrange Systems Technical Discussion
Subject: Re: Problems with spool files

Actually, the user profile must NOT be changed, and if there is even a
remote possibility that an override would interfere with other things to
be printed, then THAT must not happen, either.

The program, on the other hand, can be changed at will, which is why I
suggested creating my own private print file and output queue, under a
different name.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.