On Wednesday, 10/29/2008 at 08:51 EDT, RPN01 <[EMAIL PROTECTED]> wrote:
> Why couldn't vmsys: be localized by default, but allow the option of sharing > it among systems, where it makes sense in the customer's environment? Don't > be so headstrong in protecting me from myself; I may have thought of > something you missed. As has been said, you can rename VMSYS to anything you want. As long as the name doesn't start with "VMSYS" it will be a global filepool (but subject to the setting in the DMSPARMS file). Just be sure you do PPF overrides to change the filepool name. To elaborate a bit on my previous explanation of "why?" is is because SES does not recognize that there could be another system trying to manipulate or use the data in the VMSYS filepool. For example, there's no explicit file locking when SES is going to update more than one file. VMSYS really was designed to be accessed by a single system. Again, I recognize that this is not sufficient for a clustered environment that has a mixture of shared and private data needed by SES. We intend to fix that as we improve our clustering capabilities. > On a similar but disparate subject: Why do we have to use tape to move SDF > type files from one system to another? I just want to move CMS, GCS and the > various system files from one system within CSE to another... But to do it, > I have to have a tape drive. It's the only use I have for a tape drive now, > and it keeps us from getting rid of otherwise unneeded hardware in a data > center with no space or power to install new systems. Another "why?" question. :-) Because it was designed during a time when people were not so reluctant to provide their VM systems with a tape drive? z/OS needs a tape and no one complains. Harrumph. (Doesn't anyone share anymore?) There are virtual tapes, whether provided by h/w or s/w. The s/w version doesn't take up space on your RF! > A question comes to mind here... I can easily build CMS and somewhat easily > build GCS. What is, or where are, the procedures for rebuilding all the > other SDF files? There's likely documentation for the various shared > segments, but what about the IMG and NLS files? I haven't gone on a search > yet, but is there somewhere that these procedures are documented? z/VM Service Guide. Chapter 4. Alan Altmark z/VM Development IBM Endicott
