Re: Question about lp5250d and SCS2ASCII

To me, the problem seems to be in the way lp5250d reads the SCS stream. He says it's chopping the data into multiple files when it shouldn't -- and that would imply that it's happening when the SCS is generated, not when scs2ascii processes the output.

So I'm not sure dumping the raw SCS to disk would help much?


On 5/13/2010 4:25 PM, James Rich wrote:

On Thu, 13 May 2010, Alberto wrote:

I am still trying to find the right way for make you reproduce the problem,
so i'll let you know asap !! :-)

The easiest way to reproduce this problem is to create a printer
configuration that dumps the raw SCS stream to a file. Of course, make
absolutely certain that there is no sensitive or private data of any kind
in the spool file that you use to create this data.

To create a printer configuration that dumps the raw SCS output to a file
add an entry like this to your ~/.tn5250rc file:

print-raw {
host = your.as400.domain.com
env.DEVNAME = RAWDEVICE
outputcommand = cat> /tmp/output.scs
}

Then email me or Scott the resulting output.scs file directly since this
list strips attachments. Then we can pipe output.scs through scs2ascii or
whatever and see if the problem occurs.

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev