I found it, although 'it' is not as complete as I had remembered. What I am referring to is some nice 'how to' doc for DIRMAINT. Appendix 'F' was added to 5.3 admin guide this is a procedure for making mass changes to the directory and putting it back online. I wish there were more easy to find procedures like this one.
-----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]]on Behalf Of Le Grande Valerie Sent: Thursday, April 09, 2009 4:21 PM To: [email protected] Subject: Re: USER MDISK and DIRMAINT Question Thanks for all the great support so far from Tom, Mary Ann and Kris. You = are bolstering my confidence that I am on the right track here. I will = take your advice about not worrying about LOGON BY just yet if we are going to use RACF. I was thinking that it would give some consistency for= Admin users right now, but we will leave that alone as it might just be = more confusing. I will go right now and code the cylinders for my DASD and get rid of those default sizes that are causing the overlay messages in the director= y report. As for the user mdisks, the point about the possibility that the Linux = admins might want to be moving Linux guests around is a good one. I can = see that might happen at our shop,too. Might be better keep Linux "stuff"= all together for that reason. Thanks for the pointers on handling the user mdisks for the admins. I had= picked up on some reference to creating a group for user disks that Tom = mentioned which sounded like a good idea, and I have already dealt with = the EXTENT CONTROL file, so I can handle that. Grouping seems like a grea= t function. The less I have to keep track of in detail, the better! (My old= brain seems to have more memory dumps as the years go by.) Tom, I also have been looking for that "how to" piece in the documentation. Some products have a reference manual for commands and a = user guide for how to use those commands. Not so with DIRMAINT. The Tailoring and Admin Guide is not really a user guide for the commands. = Seems there is a piece missing here unless it is elsewhere in the documentation that I have missed.
