The size of the Gun? I was illustrating Dirmaint's place/role in the CSE *requirements*; I explictly wanted to say all CSE functions don't need.PVM and Dirmaint. I know from experience that many people see CSE as 1 thing, and that isn't the case: 3 distinct functions, all with different requirements.
We do have Dirmaint, but, our VM systems are that different that having a single source directory would be unmanageable. We do however have an exec that performs a nightly verification of all source directories. Basically all MDISK statements found to reside on packs that happen to be used in more than one source directory must be identical (this way we even don't have to maintain lists volsers that are shared) 2008/1/11, Rob van der Heij <[EMAIL PROTECTED]>: > On Jan 11, 2008 11:03 AM, Kris Buelens <[EMAIL PROTECTED]> wrote: > > > DIRMAINT (or similar) is only required if you want to have a single > > source directory that defines all users of all VM systems in the CSE > > group. DIRMAINt's CSE support doesn't need PVM, it needs an RSCS > > link. > > I believe you underestimate the size of the gun that you point at your feet. > > If you share disks between systems (even in R/O fashion) you need some > process to keep directory entries up-to-date. An approach to keep > directory entries between systems synchronized by only good will and > promise will fail. Many of us have learned that the lifetime of things > on the mainframe is often much longer than anticipated. When there's > the a chance that something can break, we have enough time that it > will break eventually. Murphy refines this as to when it will break. > > When you maintain the directory by hand, you can probably wrap some > tooling around that to check / update the shared disks. Instead of > using a shared disk to hold those entries (which gives a chicken & egg > problem) you could use ISFC links to have two (home grown) service > machines talk to each other. With the CMS Pipelines IUCV stages, you > can issue Q MDISK U commands on the remote system and get the output > of that back into your tooling. Unlike RSCS, the ISFC link does not > require extra software (only CTC links between the LPARs). > > Rob > > > -- > Rob van der Heij > Velocity Software, Inc > http://velocitysoftware.com/ > -- Kris Buelens, IBM Belgium, VM customer support
