Definitely agree. But I believe that the mistakes I made back in the '70s and early '80s, would get me fired, today <G>. Back then, mainframes crashed on their own. It seemed expected.
But what goes around, sometimes comes around. I run into people that want to boot the z9 for any problems and/or updates. Just like any other Windows box. It all depends on how critical the production is on that box. Hopefully, management understands that less qualified people (of any time) cause more problems than qualified ones. You said you had duplicate volumes. I thought you were second level? On second level, you only give that guest the volumes it needed. There should be no duplicates. Anyone, one point that is lost on system programers from other operating systems.... 1. The volume you boot from, is the only disk that CP knows by address. For all other volumes, it is based on VOLSER. And in the grand scheme of things, when duplicate volumes are encountered, you can't predict which volume will be used, and which will be shown as duplicate. (I say that it can't be predicted, as it is based on which one your DASD subsystem returns first. Usually, this will be the same, every IPL for a given shop. But if you have multiple DASD subsystems, which system responds first, the IBM dasd or the EMC dasd? for example) Your USER DIRECT (or the program product DIRMAINT), then guides disk usage via VOLSERs. Duplicates become a problem. True, there are also DEDICATEs and ATTACH command which is by addr. But at VM IPL time, they don't come into play. What I'm trying to stress about, is duplicate volumes that your 1st level VM can see at IPL time. Been there, done that. Come up with the wrong spool volume, and your only options, destroy your spool data. Yea, that's fun. It use to be you could go over to your disk volumes and disable the duplicate drive and reipl. In my case, I reipled and older VM system, which had different volsers. I then attached the drive to myself and relabeled it to get rid of the duplicate volser which allowed the correct one to be seen at IPL. Then IPL'ed VM normally. And you won't find this problem until you boot your first level VM system, months/years later. When Operations calls you in the middle of the night, saying "we've got a problem". Fun Times.... Tom Duerbusch THD Consulting Law of Cat Acceleration A cat will accelerate at a constant rate, until he gets good and ready to stop. >>> Stewart Thomas J <[EMAIL PROTECTED]> 5/14/2008 4:26 PM >>> If you remember your first years, everyone starts out as an unqualified VM system programmer, then we learn and become qualified! ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
