Richard,
Following David Boyes' example, set up something like: LINKDEF MVS1A NODE MVS1 TYPE SNANJE LUNAME MVS1ALU ASTART RETRY PARM MVS1A BUFF=3840 LINKDEF MVS1B NODE MVS1 TYPE SNANJE LUNAME MVS1BLU ASTART RETRY PARM MVS1B BUFF=3840 ROUTE GROUP MVS1 TO MVS1A MVS1B Mark Wheeler http://www.linkedin.com/in/marklwheeler Date: Thu, 23 Apr 2009 13:00:45 -0700 From: [email protected] Subject: RSCS Connections To: [email protected] 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 _________________________________________________________________ Rediscover Hotmail®: Now available on your iPhone or BlackBerry http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Mobile2_042009
