Alan, Would it at least be possible for the information contained in those 30 IBM manuals recording the various userids included by IBM in z/VM, be gathered into one manual? Say the Guide for Automated Installation and Service, which already has "Appendix E: Contents of the z/VM System" (or whereever you like). Would that result in warm fuzzies instead of cold pricklies? :-)
On my system, each new userid gets a file on his A disk when created, containing his name, location, department and title. Sure, it could be erased, but its more accessible than the directory for someone trying to figure out whose id this is. Ron On Tue, Feb 10, 2009 at 11:54 AM, Alan Altmark <[email protected]> wrote: > On Tuesday, 02/10/2009 at 11:38 EST, Marcy Cortes > <[email protected]> wrote: >> Would be nice if there was some consistent key like "IBM Supplied" or >> "z/VM Component" in the description. >> That way we can make a list from the new install and compare it to the >> list on the current system. That'd allow us to more easily identify >> ones that went away as well so we're not carrying them to infinity. > > Being able to easily pick the, fly-, uh, droppings out of the pepper, as > it were, is part of the justification for putting a owner/name/description > with a user ID. > - Who does this user ID belong to? > - Is it an animal, vegetable, or mineral? (person, SVM, data repository) > - What is it for? > - Why does it need class C? > - Is it required or optional? > - How can I associate it with a unique identifier in my own business > process? > > All with an eye to: > - Ease directory migration from release to release > - Avoid having to read 30 books to answer "What's this for?" > - Making auditors/security people happier > > A simple comment in the directory may be able to achieve those objectives, > but as a software designer it gives me the cold pricklies. > > Alan Altmark > z/VM Development > IBM Endicott >
