We had a configuration that looks like this:
VM/RSCS ---------------------------- MVS1
The JES2 and MVS network folks got together and came up with a slight
alteration:
VM/RSCS ----------------------------- MVS1
|
................................................. Etc.
| |
MVS1(a) MVS1(b)
Where VM knows absolutely nothing about the MVS1(x) subordinate machines. The
node MVS1 has suddenly become a link to a group of systems collectively known
as MVS1. Naturally, this means that if the Front End is down, the machines in
the collection are unable to participate in the network.
The question of keeping the MVS1 node alive when the F/E machine is down has
been posed. The only way that I have been able to come up with so far is to
define a link to MVS1A, for example, specify it as an alternate route for MVS1
traffic using something like "route node mvs1 to link mvs1alternate mvs1a". If
this will work, it will at least give access to one member of the collection.
Will this work?
If so, will the traffic revert to the normal path when the F/E is brought back
up and signs in?
Is there a better way?
Regards,
Richard Schuh
