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



Alan,

You need to produce the overlay in landscape then rotate it back to
portrait before you save it to the i.

Your print file specs below will invoke COPRR (computer output print
reduction rotation). The i print drivers rotate the printed image and
THEN apply the overlay. So your overlay needs to be in portrait with the
text running up and down the length of the page sideways on 8.5 x 11 (or
A2) paper. If you find the job log for the print job, I think you'll
find that the overlay doesn't match the page dimensions.

Dan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Thursday, December 04, 2008 9:20 AM
To: Midrange Systems Technical Discussion
Subject: Re: Lets Talk about Overlays

Hi James
here is my CL
PGM PARM(&PBNUMX)
DCL VAR(&PBNUMX) TYPE(*CHAR) LEN(7)
DCL VAR(&PBNUM) TYPE(*DEC) LEN(7 0)
CHGVAR VAR(&PBNUM) VALUE(&PBNUMX)
OVRPRTF FILE(PCKLIST) DEVTYPE(*AFPDS) PAGESIZE(60 +
132) LPI(8) CPI(15) PAGRTT(90) +
OUTQ(WPVLSR1) COPIES(1) SAVE(*YES) +
OVRSCOPE(*JOB) +
FRONTOVL(AXSLIB/OVERLAY3)
CALL PGM(ORD220EE) PARM(&PBNUM)
ENDPGM

The report from the above CL prints as the FRONTOVL overlay is portrait

Here is the CL that doesnt print
PGM PARM(&PBNUMX)
DCL VAR(&PBNUMX) TYPE(*CHAR) LEN(7)
DCL VAR(&PBNUM) TYPE(*DEC) LEN(7 0)
CHGVAR VAR(&PBNUM) VALUE(&PBNUMX)
OVRPRTF FILE(PCKLIST) DEVTYPE(*AFPDS) PAGESIZE(60 +
132) LPI(8) CPI(15) PAGRTT(90) +
OUTQ(WPVLSR1) COPIES(1) SAVE(*YES) +
OVRSCOPE(*JOB) +
FRONTOVL(AXSLIB/OVERLAY4)
CALL PGM(ORD220EE) PARM(&PBNUM)
ENDPGM

The OVERLAY4 is the same as OVERLAY3 except 4 is in landscape format and
3 is in portrait format



Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
midrange-l-bounces@xxxxxxxxxxxx wrote on 12/04/2008 10:06:37 AM:

Please include the OVRPRTF command as well as the device description
that you are printing to, this will help in figuring this out.

Also include the "regular" atrributes of the printfile like the length

& width, CPI & LPI if they aren't specified in the OVRPRTF.

Thanks.
James Salter
Systems Programmer
American Cast Iron Pipe Company
phone (205) 325-3033
fax (205) 307-3833



------------------------------

message: 7
date: Thu, 4 Dec 2008 09:48:12 -0500
from: Alan Shore <AlanShore@xxxxxxxx>
subject: Re: Lets Talk about Overlays

Hi James
thanks for your reply
It looks like I didn't explain my predicament clearly My program
produces a report in landscape format, which I can print.
I have created an overlay (via Microsoft Excel 2002), unfortunately in

portrait format.
This was uploaded to the AS/400 via a certain procedure.
The same program was run with the same data, this time applying my
overlay in the OVRPRTF command This report was then printed to the
same printer.
This is where I realized the mistake I made where the overlay was in
the wrong format.
I recreated the overlay (again using Microsoft 2002) this time in
landscape format.
I uploaded the new version (as a different name) to the AS/400, re-ran

the same program with the same data applying the new overlay in the
OVRPRTF.
I cannot get the new spool file to print to the same printer, no
matter what I try. The status goes to PND.
If anyone can point out what I am doing wrong, it would be much
appreciated

Thanks in advance



Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

midrange-l-bounces@xxxxxxxxxxxx wrote on 12/03/2008 05:56:14 PM:

_________Confidentiality Notice_______________________ This e-mail and

any files transmitted with it is confidential and is intended solely
for the use of the individual(s) or entity(ies) to whom this e-mail is

addressed. If you are not the intended recipient or the person
responsible for delivering the e-mail to the intended recipient, be
advised that you have received this e-mail in error, and that any use,

disclosure, dissemination, forwarding, printing, retention or copying
of this e-mail is strictly prohibited. If you have received this
e-mail in error, please immediately return this e-mail to the sender
and delete the e-mail from your system.
Thank you.

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