|
Make sure that the type that you output in overlay not document in the AFP driver. I have found in the past that occasionally the driver "looses" my settings. On Mon, 19 Jul 2004 15:35:39 -0500, Tim Randall <trandall@xxxxxxxxxxx> wrote: > Hello I have been using an overlay for a print job for a long time. I had to > make a change to the overlay and I have come across a problem. I use WordXP > to create the *.prn file and then save it to QDLS. I then use the CPYFRMPCD > command to covert it to a PF and then use the CRTOVL command to create the > overlay. I get the following error message: > Additional Message Information > Message ID . . . . > . . : CPD88C0 Date sent . . . > . . . : 07/19/04 Time sent . . . . . . : 11:01:11 > Message . . > . . : File OVERLAYS in TIMLIB not valid for creating a *OVL. > 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: > 1 - A length field contained in the incoming data for the printer > resource is not correct. > 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 is '5A0010D3A8C6'X. > 3 - The file or member specified > contains no data. 4 - The incoming data for the > printer resource is not correct. The resource must contain an END > structured field that is appropriate for the type of resource being > created. The END structured field identifier expected for this > resource is ''X. 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. > > Has anyone else run into this problem and/or know what is causing the > problem? Thanks,Tim Randall > Programmer/Analyst > City of Independence > -- > 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. > > -- Mike Wills iSeries Programmer/Lawson Administrator koldark@xxxxxxxxx http://www.koldark.net Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.
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.
midrange.com
