Re: getting SNADS to work again on a system that moved to my -- MIDRANGE-L

Subject: Re: getting SNADS to work again on a system that moved to my
From: "Lindstrom, Scott R." <slindstrom@xxxxxxxxxx>
Date: Fri, 23 Sep 2011 20:05:14 +0000
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Are there any ANYNET entries int he host table ? Something like
S6512345.APPN.SNA..IBM.COM. If so change the IP address on it.

If that's the issue having a VLAN between the partitions instead of
going out to the network would be better.

There was one entry on one of the systems that started with the system name, not the name made up with the serial number.
I tried adding entries on each side in the above format with no luck.

I am not sure of how the networking works (or how it has changed). I am told these new systems are on their own VLAN.
How does that affect SNADS?

Scott

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: getting SNADS to work again on a system that moved to my , Jack Kingsley

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.