Re: Leftover SNA functions -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

It seems like you ought to be able to discontinue running the qsnads subsystem. It's on my list of things to do when I can monitor to be sure there are no adverse effects. Perhaps someone here could comment.

ChadB@xxxxxxxxxxxxxxxxxxxx wrote:

Now that we've finally migrated our Mimix setup to TCP/IP communications,
we're getting close to the point of 'turning off' our remaining SNA
connectivity. I know it can't really be 'turned off', but we're definitely
interested in finding out any remnants of our operations that may rely on
SNA and finding an alternate way of getting them done. We know that
Enterprise Extender is an option, but would rather just find a TCP/IP based
way of doing anything that remains.

The obvious items are passthroughs, SAVRST* type commands, SNDNET*
commands, etc., but has anyone else gone through the process of weeding out
any remaining SNA based operations they are/were using? At some point in
the near future we'll be varying off the comm line that is configured for
our SNA communications and looking for fallout (along with a list of
specific items to test). I'm looking for any other gotchas or advice if
someone else has gone through this process...

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.