On Fri, 9 Dec 2005, elmars.ositis@xxxxxx wrote:
Hmm.. I must have been a bit unclear. We have not made any changed to the lp5250d. We are taking the text output as generated by outputcommand and doing additional processing on the file. If the report is broken in two bits, we cannot determine whether the file has been fully spooled, as we check for the last line in the report for completion. I am trying to understand what would cause lp5250d to split the file on a page break. There are other times, when lp5250d concatenates two very short reports into one file/page. This only seems to happen if there are two reports, one after the other which have only a 1/4 page of data and are wider than 130 columns.
It would be very helpful if you have a case that is reproducible. Does a certain report always result in the described behaviour? If yes, then another test would be useful. Try the following outputcommand:
outputcommand = cat > output$$.scsIf multiple output files are created by one print job then that would help me figure out where the problem lies. If only one output file is created, then run it through the rest of your normal outputcommand like this:
cat output<pid>.scs | scs2ascii > /var/spool/lp5250d/prlit03/prlit03-`date +%y%m%d.%H`-$$.txt
A factor to consider may be that lp5250d and the as400 are on opposite ends of a 256k wan link. Could there be a timeout issue between pages? I this something we can adjust?
I don't think this is an issue. James Rich It's not the software that's free; it's you. - billyskank on Groklaw