I'll check to see if there are any lingering OVRPRTFs, but I doubt it. I
checked one program (RPG II and OCL) that I know exhibited the problem in
the past; the // PRINTER statement is there and is correct.

Jerry C. Adams
IBM i Programmer/Analyst
A verbal contract isn't worth the paper it's written on. - Samuel Goldwyn
--
A&K Wholesale
Murfreesboro, TN
615-867-5070

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Tuesday, March 13, 2012 7:16 PM
To: Midrange Systems Technical Discussion
Subject: Re: Weird Printer Issue

An override printer file (ovrprtf) in the job stack could do this.

Also, because the // printer statement is optional, is it possible the
printer statement is not functional if the printer output file in pgm not
same as ocl printer name ?

Jim Franz

----- Original Message -----
From: "Jerry C. Adams" <midrange@xxxxxxxx>
To: "Midrange-L" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, March 13, 2012 3:16 PM
Subject: RE: Weird Printer Issue


Also, meant to say that I did check the job log after the incident today
(when the invoice wanted to print at BB even though it should have been
directed to P7). There were no messages in the job log, and it shows the
//
PRINTER OCL statement explicitly referencing P7, but nothing later except
the normal stuff.

Jerry C. Adams
IBM i Programmer/Analyst
[I support efforts] to limit the terms of members of Congress, especially
members of the House and members of the Senate. - Dan Quayle
--



This thread ...

Replies:

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

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