Re: AFP PagSeg/Overlay error

On 26-Oct-2015 13:21 -0500, mlazarus wrote:

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:
<<SNIPed as only RC2 is pertinent>>

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.

<<SNIPed as only RC02 is pertinent>>

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??

SWAG: When FTP PUT action was done to send the BINARY data to a Physical File (PF), that should have been directed to a PF that was pre-created with the desired attributes, rather than allowing the FTP to create the file; i.e. such that "the record length of the physical file is correct", according to the requirements of the Create Page Segment (CRTPAGSEG) command, rather than according to the vagaries of the FTP server. IIRC the requirement for AFP resources is 80-byte record length [92 if PF-SRC vs PF-DTA], and the FTP server is likely to implicitly create a PF-DTA as the target with CRTPF RCDLEN(512).