RLU – Page Size of 250 column not setting during printing only
1. Dears, Please guide me, I am having the following problem in RLU writing in ILERPG on AS/400. RLU was already made with page size 80 column paper, then I amended in it upto 250 column with pitch 15, but when I run it, so spool is created and the data appears upto 250 columns on screen, but when we this spool file to print, so data prints upto 80 columns only and rest of the data goes down the line and overlapps. Kindly guide me the solution so that the data can print upto 250 columns also with picth 15 on 132 column paper. 2. Printer is Panasonic 3696, connected with windows XP setup. AS/400 PRINTER session is also made. Actually, other reports upto 200 column paper are printing well, only this report (changed from 80 column to 250 column) is printing upto 80 column. Would you please tell me the complete page setup in RLU during compilation for 250 column pagewidth setting ?
Software/Hardware used:
Software/Hardware used:
ASKED:
August 17, 2010 4:51 AM
UPDATED:
August 24, 2010 7:53 AM
Answer Wiki:
Last Wiki Answer Submitted:
Be the first to answer this question.
All Answer Wiki Contributors:
Be the first to answer this question.
To see all answers submitted to the Answer Wiki: View Answer History.
The print wrap makes me think the problem lies more with the printer than the iSeries. Have you looked at the spool file before printing?
…the problem lies more with the printer than the iSeries.
I would agree. It might be in the Windows printer definition rather than the physical printer, though.
…Except — “…other reports upto 200 column paper are printing well…”. That confuses the issue.
The minimum that we need to see are the spooled file attributes related to page sizes, fonts and form definitions.
Tom
In the past I have handled a lot of printing (problem) issues. According to me, based on what I have seen, at least 90% of the spoolfiles are not defined correct what concerns the paper size. But, due to the fact the iSeries printing engine is quite flexible (intelligent) most customers agree with the output. Or think they get what they have asked for (defined).
If YOU want to control the output specify the page size in relation wit the LPI , CPI and PAGRTT values. Regardless how many characters and lines you want to print!
Above will avoid position problem whenduplex printing is being used.
To avoid font substituion problems you can specify the FIDELITY parameter to *ABSOLUTE. But in cases the font isn’t available the file will not be printed.
When the PC printer can be addressed via TCP/IP you can create on outq on the iSeries in a manner that it will use the (Windows) printer driver.
See more at http://www-03.ibm.com/systems/i/software/netserver/print/index.html
I’d be curious to know the actual file description. And I’d still like to know if the spool file looks to be formatted correctly when viewed using DSPSPLF.
The printer file definition is important. However, the actual spooled file attributes show what was applied at creation-time regardless of the printer file. Because that can include overrides and possibly other elements (library list?), spooled file attributes tell about what will be sent to the writer.
Tom
Tom, what you said is obvious. What I meant to say is that the prtf attributes what concerns LPI, CPI and PAGESIZE needs to reflect the actual size of the physical page size. Assuming that the measurement method is set to *ROWCOL. And that rule does not change if an OVRPRTF is being used. The final output is dependent of many things, but I learned from an IBM developer that a correct pagesize is the most important one.
Anjo.