×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have been trying to create a *PAGSEG or *OVL object with no success
from an image file. I am opening the file in Windows and "printing" it
to a file via one of the above mentioned drivers.
I drag/drop that file to the IFS (Explorer -> Navigator) and FTP it as
a binary to a PF. When I attempt to create the PAGESEG I receive an
error message and the object is not created.
Message . . . . : File AFP in MLLIB not valid for creating a *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:
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 47. 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 '5A002ED3A8A5'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.
I have tried several AFP drivers including a couple of generic ones
and a few Inforprint ones, including the IBM Infoprint 20. I set the
port to :FILE and the output type to page segment (or overlay, with the
same results). I tried with both compressions on and off. Also several
resolution sizes.
Any ideas??
-mark
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.