You can shortcut a few of those steps by using the "AFP Manager "- "Import
a page segement" functions in the System i Navigator. That helps you avoid
issues with the FTP and create functions. Now, on the printing side, make
sure you edit the properties of what you're printing. The document type
must be a page segment, not the default. I also set the page size, because
its not usually what you expect by default. The printer file you get is
what you import in Navigator.
By the way, I'll miss this AFP manager in the new version. I don't think
its part of the planned migration to whatever the new Java and web based
tools are. Correct me if I'm wrong.
From: mlazarus <mlazarus@xxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/26/2015 02:22 PM
Subject: AFP PagSeg/Overlay error
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
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.
The message I receive is:
Additional Message Information
Message ID . . . . . . : CPD88C0 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
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
--
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.
midrange.com
