Yes, you are sure right about the other platforms. My last windows update wouldn't. and wouldn't. and wouldn't. Took lots of google research to find enough tricks to get it past that. God forbid you get one that renders you unbootable.
The commands aren't cryptic with commas all over the place nor do they have funny names like awk. There's lots to love about VM, don't get me wrong. It's just that I think the age of CMS applications has passed and IBM is right in not investing there (course that's a chicken and egg thingie too :) Marcy Cortes "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:[EMAIL PROTECTED] On Behalf Of George Haddad Sent: Wednesday, May 02, 2007 5:36 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] z/VM usability I'm not sure this is a problem with only VM. Having "grown up" with old-school IBM tech manuals and CMS HELP, I still find *IX "man pages" to be cryptic on many occasions. But *IX is taught extensively in schools so that "newbies" arrive with a working knowledge. As for getting from one-version to another, a very wise man (Vito!) taught me early in my sysprog days, that Rule Number 1 is "make sure you can always get back to yesterday". This was almost trivial with a working knowledge of VM due to its modularity. We were almost always able to install maint/upgrades one component at a time. Made it great for troubleshooting/backout. You are correct, Marcy, that most vendors don't document the common VM maintenance tricks -- and for that matter, is GENIPLER ever going to be "standard" ?? But that said, at least the facilities exist. With Windows servers, I find myself often having to update multiple components at once. Backing off a patch is iffy at best. Talk about mixing code and config !!The only "sure bet" is a good image restore. And the Windows Registry design is a nightmare IMO. Fortunately virtualization is on its way. It's still lacking I/O performance to keep it from hosting many prime-time apps, but I'm told the next generation Intel processors will address this by including features that sound an awful lot like DAT. Geez we're almost back to the 1970s! This won't address the MS complexities per se, but will make backoffs an awful lot less painful. Marcy Cortes wrote: > performance data, .. etc) and the fact that the vendor doc isn't > exactly geared for newbies either (e.g. CA :). None of the software > seems to be good at telling you how to get from one version to another > (very few products tell you that you can use alternate minidisks and a > quick edit of the directory entry to flip --- or they are even worse > and mix their code and configuration stuff on the same minidisks, > trusting that you'll want to do the upgrade by running some exec and > hoping for the best instead of allowing you to have test copies). > >
