|
We had a similar problem, a customer was sending us a spool file from their Iseries, using a RMTOUTQ. It would show up on our system, and it would print too many lines. The spool file attributes showed a RECORD LENGTH of 256. On his system, it was 198. Everything we printed from our system was fine. We finally came up with a hack. Put a CLP to process every spool file that showed in the outq, it basically did a CPYSPLF to a data base file, then back to QSYSPRT, with the record length set to 198. We get a warning message that the data was truncated, but it prints fine. Art Tostaine, Jr. CCA, Inc. Jackson, NJ 08527 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Berman Sent: Wednesday, July 07, 2004 8:00 PM To: Midrange Systems Technical Discussion Subject: Remote Outq problem of skipping lines I have created a remote outq description for an IBM 6400 printer. It is not *LAN or PRTLAN description, because the 6400 has its own network card. So the emulation is PROPRINTER ETHERNET. It prints the first page of the pick tickets, but then for the subsequent pages, it skips some lines, rendering the printout useless. The overflow line of the print file, is 60, yet the actual lines printed are 50. So the creating RPG program, has an OVRPRTF, that does some adjusting to the Overflow line. However, I am not sure if this is the problem or not. So before I tear into the spaghetti code, Do you think the problem is located w. the printer or not. Mike
As an Amazon Associate we earn from qualifying purchases.
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.