|
midrange.com
I never realized those commands were specifically from ObjectConnect, so
that will give me a place to start...
If I can find a more comprehensive list (which I remember seeing at one
point), we can gauge the scope of what commands are 'SNA based' and decide
whether to steer clear of them, or whether to continue to use them under an
Enterprise Extender environment within TCP/IP.
I'll keep digging... i'll get to talk with some people at Common about this
next month also.
Has anyone else migratated those types of functions away from SNA and
phased out the hardware/communications?
"Ingvaldson,
Scott"
<SIngvaldson@guid To
eone.com> "Midrange Systems Technical
Sent by: Discussion"
midrange-l-bounce <midrange-l@xxxxxxxxxxxx>
s@xxxxxxxxxxxx cc
Subject
03/30/2007 11:17 RE: SNA based commands
AM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
You can remove all of the SAVRST commands by removing ObjectConnect -
5722SS1 Opt. 22 on V5R3. But you can also get rid of the hardware used
for native SNA support and continue to use these commands using AnyNet.
(SNA over TCPIP)
Regards,
Scott Ingvaldson
System i Administrator
GuideOne Mutual Insurance Company
-----Original Message-----
From: ChadB@xxxxxxxxxxxxxxxxxxxx [mailto:ChadB@xxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, March 29, 2007 9:44 AM
To: Midrange Systems Technical Discussion
Subject: Re: SNA based commands
We are mainly using SNA communications for 2 sets of functions:
- One is our connection between 2 servers that transports our Mimix
replication between the 2 servers. This can be reconfigured as TCP/IP
within the Mimix application.
- The second set of functions is the set of commands used by our
programmers to accomplish moving objects between systems... things like
SNDNETF, SAVRSTOBJ, and commands of that nature. I read a good document
at that point that described which commands used SNA functionality as
their mode of communication. Has anyone seen such a document?
We added a 2849 ethernet adapter to each of our last set of systems in
order to still maintain native SNA connectivity, but at this point we
would rather just try to use TCP/IP based communications for what we are
doing (we have no specific reason to keep things SNA).
Using Enterprise Extender is an option, of course, and we may find out
in the end that it's necessary to set this up for some portion of
functionality, but would be more interested in avoiding the SNA based
functions wherever possible. IBM's not necessarily removing it, but we
get the feeling that we should be moving away from it wherever possible.
Pat Barber
<mboceanside@worl
dnet.att.net>
To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
03/28/2007 04:46
Subject
PM Re: SNA based commands
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
SNA is not a "thing" on the system. It's a structure that the entire
commuications system is based on. There are many commands related to
communications and that will take you down a VERY long road.
Which SNA thing are you moving away from ? SDLC is probably the most
common thing, but we could be talking about a LOT of different protocols
supported by SNA. You are talking about a framework that is woven
through the entire OS. Pulling out SNA is not a minor issue.
I'm not really sure that IBM can do away with the SNA framework
entirely.
What are you moving away from ?
How much communications do you have ?
A little reading on the subject:
http://www.redbooks.ibm.com/abstracts/sg245291.html
ChadB@xxxxxxxxxxxxxxxxxxxx wrote:
We are starting to prepare for getting rid of the SNA oriented items we
are
currently using (we will move off them later this year). I seem to remember a good article or listing I saw somewhere (last year?) that gave
a
breakdown of the commands and features that were based on SNA communications. Does anyone have such a link or document?
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. ________________________________________________________________________ _____ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com ________________________________________________________________________ _____ ForwardSourceID:NT000684B6 ----------------------------------------- DISCLAIMER: This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________ ForwardSourceID:NT000687B6
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
