David, Our original idea was to have all jobs submitted to MVS1 and let the front end distribute the work. The users are unaware of the fact that their jobs run on different systems, the MVS1-plex is a single entity as far as they know.
To make the GROUP work, it looks like I need to define the links for MVS1, MVS1A and MVS1B, then define the MVS1 Group with all three links. If the MVS1 link is chosen preferentially (order tested determined by position in the list?), then everything would be sent to MVS1, as desired. If it failed, then everything would be sent to either A or B, whichever responded first, but not both. Is this correct? Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of David Boyes Sent: Thursday, April 23, 2009 1:05 PM To: [email protected] Subject: Re: RSCS Connections I think you could use link groups here. You'd have to define MVS1A and MVS1B to VM, then create a group MVS1 that contains the MVS1A and MVS1B links. You could then route files passing through RSCS to GROUP MVS1 and it would pick the first available link to queue it on. If MVS1A went away, then traffic would flow via MVS1B until MVS1A came back, and would then go back to transmit on first-available.
