Re: FW: Re: 5250 Data Stream Operation Codes -- LINUX5250

Hello,  Deleted most of message....
On 09-Dec-99 Jason M. Felice wrote:
> I should probably start following it.  (The TN3270E list..)
>
That list is also the sounding off place for TN5250 enhancments, so, I
would recommend subscribing.  It really isn't a high volume group.  This
list actually gets more messages normally.  Not like the debian-user list 
that I just subscribed to (and have to unsubscribe to) which is getting ~300
per day.  The TN3270E list has also provided good examples/explanations for
questions about implementing some of the newer features like the encrypt option.

<Forwarded message deleted..> 

> 
> Actually, there are opcodes, commands, and orders.  We were having a problem
> with orders (which are part of the Write To Display command, which are done
> with the Put opcode).  The distinction has thrown me a few times as well - I
> personally see no reason to have both opcodes and commands; using one or the
> other would have been perfectly adequate.  I think the real reason behind
> opcodes was that the SNA transport is more complex than TCP/IP, and contains
> more information which is used for scheduling packets and other such
> nonsense.
> But don't quote me on that, I just blew up a Twinax installation :)
> 
I had forgotten where the problems had occured, I just noticed the 0x0D and 
thought it was worth forwarding, I should have looked closer and seen that they
were talking about Opcodes.  I haven't looked at tn5250 recently, so I don't
know if you are processing the 0x0D opcode or not.  It is newer than the spec
that I used for doing my tn5250 emulator which doesn't process it currently.

Just to make sure we are on the same page....

  Opcodes:  These are the things that they added to the 5250 datastream for
            the telnet processing,  Basically something that is really part
            of the SNA protocol level. 

  Commands: These are the 5250 Datastream High Level what to do..
            Like Write, Read, Clear, Save, and Restore
            Screen...  Save/Restore is kind of weird as it's an Opcode and
            a command.  I've seen the Save with a Put/Get Opcode, and I've
            also seen it with a Save Opcode,  Same goes for the Restore Command.

  Orders:   These are really only used in WriteToDisplay type Commands AFAIK.

Speaking of Saving and restoring the screen, did you or Mike Madore ever
redesign tn5250 to not use local buffers, and instead send the necessary info
to the host to redraw the screen?

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