Re: assertion failed upon system connect - updated

Fortunately (or unfortunately :) someone else here in Rochester ran into
the same problem and just happened to have the proper contacts. He sent a
message to the 5250 guys in New York and some details are coming down the
pipe. Someone contacted me with the details and is currently working on
writing up a description of what is going on. Hopefully I can have some
answers in the next couple of days!

Steve Fox
http://w3.rchland.ibm.com/~sjfox (IBM Intranet)
http://k-lug.com (Rochester Linux Users Group)
http://pcxtreme.org (Personal)


"Jason M. Felice" <jasonf@shell.nacs.net> on 02/04/2000 04:49:57 PM

Please respond to LINUX5250@midrange.com

To:   LINUX5250@midrange.com
cc:
Subject:  Re: assertion failed upon system connect - updated



Well, if tn5250 horks at that line, some command is accepting either more
or less data than it used to.  That hork happens when we aren't on a
command
boundry (an EBCDIC 0x04 (ESC) character) after processing a command.  It
could conceivably happen if the command-chain wasn't proceeded by an ESC
as well, but that doesn't make much sense.

I can't really believe IBM would release it in that state, as pretty much
every third-party emulator would hork.  But... now we know that we're in
for some 5250 extensions (some are needed IMHO) next release ;)

P.S.  Why don't I just change the assertion failed message to 'Emulator
horked at line...'  ;-)


+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---