Re: Problems with spool files

How is it better that a client can't control output for just _your_ application?

If your application is using QPRINT and internal printer files, then
all you'd really need is one application specific printer file anyway.
Not much of a headache to change.

Besides, why aren't you using external printer files in the first place?

Charles

On Tue, Aug 24, 2010 at 3:40 PM, Morgan, Paul <Paul.Morgan@xxxxxxxxxxx> wrote:

Charles,

If a client wants to control print output in some way all he has to do is modify the QPRINT print file.  If you're creating your own print files now he's got to futz with all your print files and it's a big headache for her.  Is that acceptable in a production application?

Paul

Principal Programmer Analyst
IS Supply Chain/Replenishment


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, August 24, 2010 3:16 PM
To: Midrange Systems Technical Discussion
Subject: Re: Problems with spool files

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