On 4/23/09 8:00 PM, "Mark Wheeler" <mwheele...@hotmail.com> wrote: > 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
Hmm. If it truly doesn't matter which node things run on, this might be worth trying: Define a link to MVS1 with 7 streams. Define links to each node of the plex with 1 stream each. Put all the links into a group called MVSPLEX. ROUTE (or REROUTE) MVS1 to GROUP MVSPLEX. What I think should happen is that the file will be queued onto the first link in the group that has an open stream, which will normally be MVS1, and you get the behavior you originally described. If all streams on MVS1 are busy, RSCS should select one of the other links and queue it directly to one of the execution nodes that has a open stream for transmission. This should get you the behavior you want most of the time, and also remove the MVS1 front-end system as both a bottleneck and a single point of failure in the configuration -- if link MVS1 fails, there are no streams available, and the jobs will (more slowly) get distributed to the execution systems directly. Admittedly, I haven't tried it, but it seems like it should work. Les, am I totally misunderstanding how link groups work? -- db
