Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!convex!mic!montagar!fallout!bruns
From: bruns@fallout.uucp (Alan Bruns)
Newsgroups: comp.sys.dec
Subject: Re: VMS upgrade path question
Message-ID: <6522@fallout.uucp>
Date: 15 Jun 91 19:21:41 GMT
References: <962@hadron.COM>
Organization: DECUS DFWLug BBS - Dallas, TX
Lines: 35

In article <962@hadron.COM>, klr@hadron.COM (Kurt L. Reisler) writes:
> Disclaimer, I know zilch about VMS or DECNET.
> 
> With that out of the way, is it possible to upgrade from VMS 4.4 to VMS
> 5.1 or higher, without first upgrading to VMS 5.0?

As several postings have already mentioned, your best bet is to do a virgin
install.  But...

	o With version 5 there was a change made to the layout of
	  JBCSYSQUE.DAT.  There's a conversion procedure that shipped with
	  V5.0 that does this.  You can probably pick it up from somebody.
	  Or, use a command procedure that was recently posted on DECUServe
	  called FIXQUE.  I think a pre-V5.0 version of it was posted as
	  well as the post-V5 copy I grabbed.  If you don't have much in the
	  way of forms, ques, etc., defined, this is a don't-care item.

	o There have been at least two changes to the SYSUAF file, in V5.2
	  (I think) and V5.4.  CAPTIVE/RESTRICTED flag is new since V4.x, and
	  the password dictionary/validation stuff was added in V5.4.  Once
	  again, if you only have a few UAF entries, do a UAF LIST/FU before
	  the install and key it all in afterwards.

There have been a number of postings on the same basic subject on DECUServe
over the past year or so.  These are the main sticking points (as I remember
them) in doing a jump past V5.0.  Doubtless some other folks remember other
things and will jump in.

Kurt, if you're not still on DECUServe and would like, I'd be glad to extract
as much of the discussions as I can find there on this and send them to you.

Alan Bruns
Allied Electronics, Inc.		Bruns@Fallout.UUCP
Fort Worth, TX  76118			Bruns@Eisner.DECUS.Org
(817) 595-6420