[Info-vax] Undo Autogen on VMS 7.3

[Bob Gezelter]

On Nov 1, 7:11 pm, "Rob Jarratt" <nos... at nospam.no> wrote:
> "Jan-Erik Soderholm" <jan-erik.soderh... at telia.com> wrote in message
>
> news:ianft6$j5s$1 at news.albasani.net...
>
>
>
> > On 2010-11-01 23:35, Rob Jarratt wrote:
>
> >> "Jan-Erik Soderholm" <jan-erik.soderh... at telia.com> wrote in message
> >>news:ianepk$hfi$1 at news.albasani.net...
> >>> On 2010-11-01 23:21, Rob Jarratt wrote:
>
> >>>> "Jan-Erik Soderholm" <jan-erik.soderh... at telia.com> wrote in message
> >>>>news:iane5h$ggt$1 at news.albasani.net...
> >>>>> On 2010-11-01 23:00, Rob Jarratt wrote:
> >>>>>> I have an old Alpha 433au to which I just added some extra memory. So
> >>>>>> I did
> >>>>>> an Autogen, but it looks like there were some problems with the
> >>>>>> parameters
> >>>>>> as there were conflicting SCSNODE values etc. I pressed ahead, but
> >>>>>> would
> >>>>>> now like to go back to the previous configuration. Is this possible?
> >>>>>> If so,
> >>>>>> how do I do it? Note that I have not purged any files in sys$system,
> >>>>>> so I
> >>>>>> am wondering if it is just a matter of deleting the most recent
> >>>>>> SETPARAMS.DAT and rebooting?
>
> >>>>>> Thanks
>
> >>>>>> Rob
>
> >>>>> Or simply fix the problems and rerun AUTOGEN.
> >>>>> What actual problems are you seeing ?
>
> >>>> All my licenses seem to have expired, even though they are still valid
> >>>> and
> >>>> within the expiry date.
>
> >>>> Regards
>
> >>>> Rob
>
> >>> What "licences" ? "Seem" to have expired ?
> >>> Show output of the rellevant commands or don't mention it at all.
>
> >> Just realised the problem is a different one to the one I thought. I was
> >> jumping to some conclusions. It looks like the actual problem (or at
> >> least
> >> one of the problems) is that DECnet won't start because of this error:
>
> >> DECnet address of local node must match VMScluster system ID.
>
> >> As I am not especially expert on clustering I would rather go back to
> >> where
> >> I was before, even though this looks like an excellent learning
> >> opportunity
> >> :-) But I would prefer to save that for another day if there is a way to
> >> rollback.
>
> >> Regards
>
> >> Rob
>
> > OK, SCSNODE and SCSSYSTEMID are critical for same parts of VMS.
>
> > SCSSYSTEMID for e.g. DECnet and SCSNODE for already configured
> > queues (The /ON=xxx must match SCSNODE, if not the queue does
> > not start).
>
> > Was this a clustered system at all ?
>
> > Note that the error message mentiones "VMScluster" since some
> > parts of it uses the the SCSNODE/SCSSYSTEMID system parameters,
> > but this system does not have to be part of a cluster as such.
>
> > Anyway, you can fix this by simply entering the correct
> > SCSNODE and SCSSYSTEMID in the MODAPRAMS.DAT file and
> > rerun AUTOGEN.
>
> Thanks. MODPARAMS.DAT had multiple entries for SCSSYSTEMID with different
> values, most were not the value I wanted. They seemed to have been derived
> from some other configuration command procedures, here is an example:
>
> !****************************************************************************
> ! This section contains System Parameters found in
> ! SYS$SYSDEVICE:[SYS0.SYSEXE]ALPHAVMSSYS.PAR
> ! with values that must be preserved when AUTOGEN is run.
> !
>
> and also
>
> !****************************************************************************
> ! This section contains any parameters found in
> ! SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT
> !
> !vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
> !
> ! SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT
> ! Created during installation of OpenVMS AXP V7.2 30-AUG-2001 14:32:14.33
> !
>
> I changed all the entries to be consistent and in agreement with DECnet and
> DECnet was able to start.
>
> Yes, I think the system was clustered at some point before I got it (this is
> a hobbyist system now).
>
> Regards
>
> Rob

Rob,

If the problems were caused by the inconsistency between the DECnet
node id and SCSSYSTEMID, I would normally opt to go forward, and not
attempt to go backward.

If you are working with a system that has history (e.g., you did not
wipe the disks and start over with everything fresh), it is likely
that someone made the changes and did not touch MODPARAMS.DAT. In that
case, falling back will not result in progress, it will simply result
in a system that is difficult to maintain.

Since we could fall back if we needed to, I would correct the problems
in MODPARAMS.DAT. I would then re-run AUTOGEN through the TESTFILES
stage (as has been mentioned; it is worth noting that AUTOGEN does
have HELP, and the HELP is reasonable, albeit actually a little
verbose at times). I would then see what state I was in.

I have recovered many systems from similar problems, I cannot recall
the last time that I was forced into deleting the AUTOGEN output
rather than simply correcting the problem and re-running AUTOGEN.

- Bob Gezelter, http://www.rlgsc.com