RE: Changing protocols

["Urbanek, Marty" <Marty_Urbanek@xxxxxxxxxxxx>]

Frank,

So much of TCP/IP application level protocol seems to be based on timers.
When things fail, you really don't get much indication why, as somebody else
mentioned about sense codes.

One thing I miss is the ability to have a user's interactive job time out
and go to a disconnected status for a certain amount of time, during which
they can sign back on and be exactly where they left off. If you can do this
with telnet, I don't know how.

I don't know what kind of applications you had, but one great thing about
SNA was the ability for one APPC application to invoke a partner program on
a remote system, and do whatever they needed to do for each other. To
achieve this with TCP/IP (unless you run SNA over IP, aka Anynet) you have
to rewrite your applications and one of them has to be a "server" or
"daemon" to listen for and accept the conversation requests and kick off
subtasks to service those requests. This was all built in to SNA.

There may be parts of TCP/IP configuration, such as PPP connections, that
can only be configured from the Operations Navigator GUI as opposed to CL
commands. I am not sure about this, but if so, it could reduce your ability
to automate things via CL.

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