Autogen and Modparams problem

[rcrosbie]

We are running OpenVMS 6.2 on a 2 node 7000-600 cluster. When running autogen "@sys$update:autogen savparams testfiles feedback" after removing the 2 parameters from modparams.dat we still generate the following errors in agen$feedback.report

The following was detected within MODPARAMS.DAT
Please review immediately.

** WARNING ** - The value of RESHASHTBL specified or calculated
(131072) is more than the maximum permissible value of 65535.
Please review the MODPARAMS definitions of RESHASHTBL,
MAX_RESHASHTBL & ADD_RESHASHTBL.
RESHASHTBL will be set to 65535.

RESHASHTBL parameter information:
Feedback information.
Old value was 65535, New value is 65535
Current number of resources: 155359
Override Information - parameter calculation has been overridden.
The calculated value was 131072. The new value is 65535.

And;

The following was detected within MODPARAMS.DAT
Please review immediately.

** WARNING ** - The value of SYSMWCNT specified or calculated
(54285) is more than the maximum permissible value of 32767.
Please review the MODPARAMS definitions of SYSMWCNT,
MAX_SYSMWCNT & ADD_SYSMWCNT.
SYSMWCNT will be set to 32767.

SYSMWCNT parameter information:
Override Information - parameter calculation has been overridden.
The calculated value was 54285. The new value is 32767.

Anyone have any ideas? I have checked to make sure we do not have a modparams.dat hiding in the sys$common area.

Thanks in advance,
Rich

[John Gillings]

Rich,

   AUTOGEN has corrected the numbers to the maximum values, so there's nothing to panic about.

The workings of AUTOGEN are rather arcane and circuitous, and very changeable between versions. Since I don't have a V6.2 system, I can't try to decode how SYSMWCNT and RESHASHTBL are calculated on that version. Best guess is some other entry in MODPARAMS, or possibly some feedback data are causing the values to go higher than allowed.

To find out for sure read through AUTOGEN.COM (not for the feint of heart!), try to work out what other parameters influence SYSMWCNT and RESHASHTBL and check that they're all reasonable. I'd also be doing DIFFs on MODPARAMS to see what changed since the last clean AUTOGEN.

On the other hand you could choose to just ignore the warnings, in the knowledge that AUTOGEN has "fixed it". The system hasn't been upgraded in almost 20 years, so it's unlikely you'll be discovering any show stoppers.