My best friend Bill writes... > These maroons (designated thusly, so that we don't give morons > a bad name -- to steal Chris Craddock's lovely phrase)
Actually I stole it from Bugs Bunny because it always gets a laugh. The rest of this thread has (as usual) meandered off its original path and into the area of installation and thence to installation naming standards. Customers have always insisted on their right to name everything to their own tastes and of course the system has always catered to that. I will nail my colors to the wall and say that I have always thought that a monumentally stupid idea, even back in my long ago previous life as a sysprog. Frankly it just takes a lot of work and produces (as near as I have ever been able to tell) no tangible benefit. The discussion here demonstrates that no two shops are alike and that in itself is a barrier to the successful migration of people and skills around the industry. New guy comes in the door with decades of experience and he's literally clueless and helpless until some local authority shows him the ropes and gives names to all the rocks the necessary information is hiding under in this particular shop. There are lots of ways out of this dilemma. Other platforms have the same flexibility in naming, but without the long history of militancy about local choice they quickly wised up to the idea that its better to just leave the names alone. There is probably no going back for us, which is a pity. I like Ed's idea of using indirection. Catalog aliases might also serve this purpose quite elegantly but they are a pain in the butt to deal with too. The simplest practice is probably just not to rename them in the first place. CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
