Re: Betr.: Re: Printing PDF on iseries outq

On 06-Mar-2015 02:40 -0600, Erwin Donker wrote:

<<SNIP>> When tested separately as you suggested, it looks to me like
the problem is in the cat command. When looking in the file as it is
stored on the IFS, the first couple of lines look like this:

%PDF-1.4
<<SNIP>>

When I issue the cat command (cat -c file.pdf) the result looks like
this:

&àã
<<SNIP>>

And this goes on for a very long time (170 pages?). When I change the
CCSID of my PDF document and then look in the file again, the content
looks like the result of the cat command. So it looks like cat is
changing the data. <<SNIP>>

Actually, the output from the "cat -c" request appears correct; the binary data in the beginning of the file will appear much like shown, when presented as though EBCDIC data, so seemingly the cat utility is properly leaving the data unconverted just as requested. Presumably what was used when "looking in the file as it is stored on the IFS" was either the Display File (DSPF) command or the Edit File (EDTF) command, each of which implicitly translates the data from the ASCII file CCSID to the [default] EBCDIC job CCSID.

<<SNIP>> When I change the CCSID of my PDF document and then look in
the file again, the content looks like the result of the cat command.
So it looks like cat is changing the data.

If the CCSID of the STMF is changed to match the CCSID of the job, thus an EBCDIC CCSID instead of an ASCII CCSID, the DSPF of that STMF should appear nearly the same as the results of the "cat -c" request; that effect would essentially confirm the validity of the "cat -c" results described [but snipped to just the first line] above.