Jay,
It's not unusual for non-displayable characters to be sent to a
terminal as display data. This would happen, for example, when
displaying raw physical file data, if the data contains packed decimal
fields. 5250 terminals usually replace this data with a solid
rectangle, to visually indicate non-printable characters. If memory
serves, these are all characters less than 0x40, and 0xFF.
HTH
____
Paul
______________________________ Reply Separator _________________________________
Subject: Re: assertion 0 failed, 0.14.0
Author: "Jason M. Felice" <[EMAIL PROTECTED]> at InterNet
Date: 12/4/99 1:33 AM
Fixed. Apparently the AS/400 is sending 0x0D (which, in ASCII is a CR) to the
terminal as though it were a valid data character. It currently has no special
meaning, but according to this:
http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/CO2E2001/15.6.2
It's not a valid data character either. It is now being treated as a valid data
character, although we don't know how to display it.
The fact that this is a CR in ASCII and that it seems to appear at the end of
every line in the file makes me suspicious that some sort of conversion didn't
take place properly. This of course doesn't excuse the AS/400 for sending it to
the terminal as though it were valid data.
If you find more characters like this, let me know.
Updates to 0.14 and 0.15 in CVS will be available soon, but I'm going to try to
knock a few more bugs out :)
-Jay 'Eraserhead' Felice
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to [EMAIL PROTECTED]
| To subscribe to this list send email to [EMAIL PROTECTED]
| To unsubscribe from this list send email to [EMAIL PROTECTED]
| Questions should be directed to the list owner/operator: [EMAIL PROTECTED]
+---
