|
Hi Jim, There is no OVRPRTF at the moment. The current status is a PRTF created with DEVTYPE(*AFPDS) and FRONTOVL(MyOverlay). Displaying the File Description shows the Overlay, but I have to admit that I haven't checked the spool file with option 8. We could safely assume that this will show the right settings, but I will double-check it tomorrow when I get back to work (based in the UK, I am already in the warm at home). What I found strange was that I was able to display the spool file. I actually expected a message saying that the spool file couldn't be displayed, sent, etc. but in fact, option 5 displays the content rather nicely (data only). So, this tends to prove that I might be wrong somewhere... On the other hand, I got the same results with the IBM samples, which led me to think that the overlay would get lost somewhere (ie, the printer would not be able to print it). To make things more confusing, this printer was used in the past to print reports with logos... I am indeed going in circles!!! Any input to resolve this rather annoying issue will be more than welcome... Fabrice -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jim Franz Sent: 27 January 2004 18:49 To: Midrange Systems Technical Discussion Subject: Re: AFP - *OVL issue Is there an OVRPRTF when the pgm runs, and what does it say? DSPFD of the printer file should show the overlay you specified. Once spool generated, Opt 8 of wrksplf should show that it has Printer Dev Type = *AFPDS and Overlay = your overlay. jim ----- Original Message ----- From: "Fabrice Calmelat" <f.calmelat@xxxxxxxxxxxxxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, January 27, 2004 12:48 PM Subject: RE: AFP - *OVL issue > Hi Rich, > > The printer is a LEXMARK Optra S2455 which is attached to the LAN and I > can't see the device description from the 400. > > Concerning the PRTF, I tried using the FRONTOVL parameter and > DEVTYPE(*AFPDS) but also specifying the overlay details within the DDS. None > of them worked... > > I downloaded some samples from the IBM website (PRTF, OVL and RPG), ran them > off and printed the reports on this printer, but I couldn't get the logos > and frames to print (although the barcodes printed ok). I tried them on an > IBM printer too, and again, it didn't work. > > I'm really puzzled as it seems to be a very simple operation and I followed > the step-by-step procedure to the letter. > > > One funny thing is that I can display the spool file before printing it, > which I believe shouldn't be possible because of the overlay. Strange... > > Any ideas and clues are most welcome... > > > Fabrice. > > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Rich Duzenbury > Sent: 27 January 2004 17:10 > To: Midrange Systems Technical Discussion > Subject: Re: AFP - *OVL issue > > On Tue, 2004-01-27 at 10:01, Fabrice Calmelat wrote: > > Hi, > > > > I have created an overlay using the IBM AFP driver and the CRTOVL command. > > This went smoothly and I can compile a PRTF referencing this overlay. > > However, when I print my report, the overlay does not get printed and I > only > > get the data. > > > > Any ideas? > Make sure to specify devtype(*afpds) frontovl(myovl) on the CRTPRTF > comnmand. You're sending it to an IPDS printer, or a printer running > host print transform, too, right? > > > > > > > Fabrice > > > > > > > > _______________________________________________ > > 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. > > _______________________________________________ > 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 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.