Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!AIM.RUTGERS.EDU!hobbit From: hobbit@AIM.RUTGERS.EDU.UUCP Newsgroups: mod.computers.vax Subject: What's the *story* here?! Message-ID: <8703281743.AA28202@ucbvax.Berkeley.EDU> Date: Sat, 28-Mar-87 02:09:00 EST Article-I.D.: ucbvax.8703281743.AA28202 Posted: Sat Mar 28 02:09:00 1987 Date-Received: Sun, 29-Mar-87 10:47:16 EST Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Distribution: world Organization: The ARPA Internet Lines: 22 Approved: info-vax@sri-kl.arpa VMS upgrades involving image patching usually patch an extant image in the system tree, write a new image in the "kit working directory" and then copy that over to the tree, superseding the original image. If Patch finds an ECO level already set when the .VUP file tries to set it, the replacements performed under that ECO level aren't written when Patch finds an UPDATE command. There are several files in the 4.5 VMS update that already have ECO levels set and from what I can see already have the fixes provided by the 4.5 .VUP file. So why is the .VUP file there? A short example is LOGINOUT, which has ECO level 1 already set from the 4.4 mandatory. No new image is written at all, since no changes are done under anything but ECO level 1, so your "provide_file" or equivalent *fails*. What's going on? Did someone completely lose track of what versions of things were being shipped/updated? Should I simply go ahead and use the extant images for those cases that weren't updated, or should I mung around with the ECO levels? What did other people who upgraded from 4.4 to 4.5 do with this? _H* ------