Re: FW: Re: 5250 Data Stream Operation Codes

[wsuetholz@xxxxxxxxxxxxxx]

On 10-Dec-99 Jason M. Felice wrote:
> On Sat, Dec 11, 1999 at 11:00:26AM +1300, Carey Evans wrote:
>> > Out of curiosity, why would we do that?
>> 
>> Because if tn5250 crashes, and you reconnect and resume the session,
>> the local buffers won't be there any more.  And if you signoff a
>> session when it's got some screens saved, you get a memory leak since
>> the saved screen is never used.

The memory leak is there, and there really isn't a good way to determine when
a saved screen buffer could be freed.

> 
> Waitaminute... what happens if you reconnect the session with a different
> emulator?  That could be disasterous.
> 

Yes,  And since the restore can possibly use the restore opcode, you can't
just reverse engineer the screen and send the WTD type commands and expect
another emulator to handle it properly.  However, that was the solution that
I did.  Basically I determined the WTD orders necessary to repaint the screen
and get my fields back to the same state they were in.  Modified flags and
all.  Then I treated a restore opcode like a put/get opcode which left the
session in the invited state.

As far as other emulators go...  Shouldn't everyone be using the better tn5250
emulator for linux?  ;-) 

Bill Suetholz
+---
| 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
+---