On 11/1/05, Berry van Sleeuwen <[EMAIL PROTECTED]> wrote: <SNIP>
> Any other ideas I did not consider yet? Here's an idea that touches on a couple of others. Combine the use of TSAF and ISFC. We've been running SFS servers on our z/VM host and sharing them with a large number of z/VM guests for years. Based on this experience, I've found that when you do not have the real CTCs available on your host to go with a pure CS Collection solution, that a combination of TSAF and ISFC works really well. It's all based on the notion of using ISFC via CTC, but uses TSAF to bridge the gap between host and guest, where you do not have a real CTC available and cannot use a virtual CTC. 1) Designate a z/VM guest to be "always available". You said VM4 hosts your SFS server now, perhaps that might be a good choice. Setup a TSAF collection between host and VM4 via Virtual CTC (vCTC). This allows you to access SFS on VM4. 2) Configure VM1, VM2, and VM3, to have vCTC connections to VM4. Use ISLINK to create an CS Collection that VM1, VM2, VM3, and VM4 use. Now, as long as TSAF is running on VM4, users on VM1,2,3 will all be able to use SFS. (You can also use vCTC between your guests on VM3 and VM3 itself) This approach gives you a different set of trade offs from a pure CS or TSAF collection: Pros: No requirement for a real CTC, no TSAF limitation on collection size, minimize TSAF server resources used (I believe it is cheaper to run a CS collection vs. TSAF collection) Cons: Must have z/VM guest with TSAF available at all times We've used pure CS collections here for about 4 years, so the TSAF/CS solution is getting a bit hazy. I think this was the gist of it. I know that it's been discussed from time to time in the archives and I believe that Bill Scully might have once given a session on it as well. Good luck, John -- John Hall (+1) 727-397-6373 Safe Software, Inc. JohnHall (at) SafeSoftware.Com http://www.SafeSoftware.Com JohnBeachFL (at) gmail.com
