|
I have done what you are trying to do many times, but I didn't use corel photopaint. I believe the record length to the physical file has to be RCDLEN(32766). Also on the CPYFRMPCD the following parameters must be filled as follows; TRNTBL(*NONE) and TRNFMT(*NOTEXT). One more thing on the CRTOVL DATATYPE(*AFPDS). Hope some of this helps. Wayne Achenbaum Slomin's Incorporated ----- Original Message ----- From: Richard Baird <rbbaird@premsys.com> To: <MIDRANGE-L@midrange.com> Sent: Thursday, July 22, 1999 8:12 PM Subject: AFP Problems. > Hey all, > > I'm trying to do a simple invoice form overlay. > > I found the directions to do this in the midrange-l archives (thanks > Buck). > > I created the form image using corel photopaint, printed it to an afp > print file (IBM AFP 240), and moved the file to a folder in QDLS, > created the file, (record length 8201, level check no), did the > CPYFRMPCD, which worked fine, but when I try to do a CRTPAGSEG or > CRTOLY, I get a message: > > Message . . . . : File INVOLY in QGPL not valid for creating a *OVL > (or *PAGSEG). > Cause . . . . . : The file or member cannot be used to create a > printer > resource. *N means that the incoming data was an internal system > space. No > source file or library is specified. The reason code is 02. The > reason > codes and their meanings are: > ... > 2 - The structured field identifier in the incoming data for the > printer > resource is not correct or is not supported. The error was detected > while > processing record 1, byte number 17. The structured field which is not > correct may be caused by a length that is not correct on the previous > structure field. The structured field which was being processed at the > time > ... > Recovery . . . : Verify that the names of the file, library, and > member are > specified correctly on the command. If the data originated on another > system, also make sure that the record length of the physical file is > correct. > > > Any Ideas? > > Thanks in advance, > > Rick Baird > Premium Systems > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.