That would work, but it would route the traffic during any period that MV1N was down. I suppose, we could start a timer in a service machine and have is issue the commands to switch to the group if the link was down and more than x jobs were queued or any job was queued for longer than some threshold value on the link. It would also have to be the one to detect that the link was back up and reroute the traffic back.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark > Sent: Monday, April 27, 2009 9:16 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: RSCS Connections > > On Monday, 04/27/2009 at 12:12 EDT, "Schuh, Richard" <rsc...@visa.com> > wrote: > > It doesn't quite fit what the network designers want. > > You *could* play the automation game. When MVSN goes down, RSCS will > issue a message and try to restart the link. Capture the message and > ROUTE the traffic to a backup node. When the MVSN link comes > back up, > reroute the traffic back to MVSN. > > Alan Altmark > z/VM Development > IBM Endicott >
