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.
Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Tuesday, February 10, 2009 7:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Short user description in sample CP directory On Tuesday, 02/10/2009 at 09:12 EST, Kris Buelens <kris.buel...@gmail.com> wrote: > Has it been suggested already that the sample CP directory would > contain, for each userid, a one sentence description? Yes. (It was suggested here previously so that RACF initialization can associate a name/purpose with a user ID.) I have some concerns about storing metadata in comments in the directory, but I guess I can get over it. I prefer to have such data stored in the object directory where it can be interrogated, updated, and supported by a wide variety of Interested Parties. However, in the case of Sooner v. Later, more complex solutions always side with Later. Though maybe, with apologies to Voltaire, I shouldn't allow the Perfect to become the enemy of Good Enough? Alan Altmark z/VM Development IBM Endicott
