On Friday, 01/11/2008 at 08:38 EST, Rob van der Heij <[EMAIL PROTECTED] > The primary requirement is that the CP directory of all involved > systems is managed in some way by a single organization. > Use of distributed IUCV requires that you control at least the > userids. And like you describe, when you share mini disks you must > control allocation of those shared mini disks. Whether with DIRMAINT > or with home grown tools.
Yes. The OP asked for the "best" way, and that involves using system management products that were designed to operate in a clustered environment. "A man with two watches does not know the time." Keeping two (or four!) source directories in sync is a must in a *cluster*. If you're just sharing DASD between two separate VM systems (i.e. not a cluster), then you have extra work to do to ensure that directory updates that affect the shared volume are properly reflected on all systems. If you've got RACF, you can share the database among all systems in the cluster. I would guess that CA's products have a clustering capability as well. By the way, PVM is also the mechanism that limits a user to logon only once in the cluster. Sure, you can write some scripts of your own, but they are "advisory" in the sense that the system cannot enforce the policy. If someone bypasses the script you may find yourself in trouble. And that may not have anything to do with virtual machine corruption, but, for example, something as simple as bringing up two hosts with the same IP address. Alan Altmark z/VM Development IBM Endicott
