Donna,

I had the same kind of problem going to 6.0 on a couple of machines (version
mismatches) because these machines had once had X.25 support (pre-5.5). The
system did not complain when these machines were upgraded to 5.5, nor to any
PowerPatch, but the upgrade to 6.0 was another story. IIRC, we just deleted
the offending files, re-ran jconfjob and the network started fine. [I
believe there was a thread about this on 3000-L sometime in the last year.]

John

> -----Original Message-----
> From: Donna Garverick [mailto:[log in to unmask]]
> Sent: Tuesday, August 01, 2000 1:55 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] how badly can an update go?
>
>
> Dennis Heidner wrote:
>
> > You might want to consider changing to CDROM for the MPEiX
> media, adding
> > a DVD to the e3000 and cut your own update tapes.
>
> <mild rant, not directed at dennis>
> frig fraggin bleep bleep bleep (oh i feel better :-) this
> contract *was*
> marked to get it's updates on cd-rom.  but when hp changed
> their contracts
> system all manner of things disappeared from our contract(s
> in general) --
> including the code for cd-rom.  so when 6.0 arrived, i only
> received tapes,
> no cd <sigh>
>
> > What type of aborts were you getting?
>
> the network would not start...saying something about version
> mismatches but
> nmmaint,6 showed no problems <sigh>            - d
>
> --
> Donna Garverick     Sr. System Programmer
> 925-210-6631        [log in to unmask]
>
> >>>MY opinions, not Longs Drug Stores'<<<
>