Small but important update :

I've did more tests about and i've noticed another thing :

The "split" seems it not depends from the size.
This is the scenario i've got :
1) spool file of 928 pages get splitted at page 560
the last chars (ASCII) of the output file(PCL) i get are
"1B26612D3030303132482D0DFF &a-00012H-ÿ"

2) spool file of 89 pages get splitted at page 35.
the last chars (ASCII)of the output file(PCL) i get are
"1B26612D3030303132482D0DFF &a-00012H-ÿ"
Same as above.

The chars ".ÿ" are present only on the files that get splitted.

A standard spool file that get printed correctly has "0D0C1B45 ...E"
at the end of file.
Same i get if i "print" the spool file 1 with page limit (like up to page
559) i get the same end of file.

This is how i launch the lp5250d :


Why this happens?
Thanks !

Happens with some spool files and this is what i have at the end of the
"Alberto" <a.ernestini@xxxxxx> ha scritto nel messaggio
Hi to all , i am using lp5250d under linux and i am getting a strange
The printer has env.IBMMFRTYPMDL=*LEXOPTRAC, because i want to get a PCL
output and the outputcommand contains "myscript" that is a bash script.
This is what i'm doing inside :

scs2ascii /home/alberto/outfile$$

This works like a charm, except if i send "big" spool files to the AS/400
printer handled by lp5250d.
(Big means that the output file will be big more than 1Mb.)
I will get two outfileXXXX for a single spool file. Means that the print
job will get "splitted" in two threads.
If i don't use the HPT and i use the SCS2ASCII i will get a single file.
There could be a reason for that? Some kind of a limit on the emulator?
(even a fix?) :-)

Thanks a lot.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].