Modparms functionality

[Wim Van den Wyngaert]

Is there a reason why autogen is not setting all parameters ?
Autogen could set all parameters that are not in modparams to the default value.

Currently it sets all parameters found in modparams (and those calculated based upon the ones in modparams). This leads to the often seen problem that changes are done by hand without autogen being aware of it.

Wim

[David B Sneddon · Accepted solution]

What version of VMS?
The first three lines of my SETPARAMS.DAT (as
created by AUTOGEN) are:

use current
write sys$system:alphavmssys.old
use default

then follows the setting of things in MODPARAMS
and related values.

Dave

[Robert Brooks_1]

Autogen could set all parameters that are not in modparams to the default value.

--

The feedback mechanism will set values that don't have any entry in modparams.

-- Rob

[Wim Van den Wyngaert]

Missed that.

My conclusion was based upon LGI_BRK_LIM which is on 4 while the default show 5 and modparams didn't mention it. So I guessed that we modified it by hand and that it wasn't overwritten by autogen.

But I now did "use default" and "show/all".

The "current" of these defaults is not the same as the default shown for some parameters.
GBLPAGES 77619674 while defaults says 65536.
Idem GBLPAGFIL, MAXPROCESSCNT, MULTITHREAD, PROCSECTCNT, SYSMWCNT, ... NISCS_LOAD_PEA0 ....
Bug ?

So, how can it be that NISCS_LOAD_PEA0 is on 0 after an upgrade if the default is 1 (but shows default 0) ???

VMS 7.3.

Wim

[Wim Van den Wyngaert]

IGNORE MY LAST POST.
Did a bad manupulation.

Wim

[Wim Van den Wyngaert]

I'm getting old. But as an excuse : I didn't have my first coffee.

[David B Sneddon]

I just tried on a V7.3-1 and V8.3 system...

$ mcr sysgen
use default
show/all

and current values matched the default for all
parameters.
Is your V7.3 system fully patched?

Dave

[Wim Van den Wyngaert]

Did it too. Found 1 : TIMEPROMPTWAIT default says -1 while the current is 65535.

Wim