🚀 go-pugleaf

In article <1992Oct7.142934.1006@beckman.com>, dsroberts@beckman.com writes:
> In article <1992Oct7.130134.1005@beckman.com>, dsroberts@beckman.com writes:
>> I've run across an anomoly in autogen.  Don't know if I'd call it a bug or a
>> feature :-).  I was making some changes to modparams.dat to install a new
>> product, and ran autogen.com.  It would error in the SETPARAMS phase with
>> "parameter out of range".  It turned out that LRPCOUNTV was getting set
>> to 4800 even though the sysgen max is 4096.  My modparams.dat file had a
>> "MIN_LRPCOUNTV=957" in it.  I added a MAX_LRPCOUNTV=4096 to resolve it.
>> 
> It has been pointed out to me that this behaviour is documented in either the
> 5.5-1 or 5.5-2 release notes (I'm at 5.5, so haven't taken the time to look
> them up on the CD).  I think I'll call it a bug :-)  The workaround given is
> precisely what I did (add a MAX_ value in the case above).
> 
> Anyway, this happened to SRPCOUNTV (too high) and PAGFILCNT (too low!) for me.

A note on AUTOGEN. 

First, AUTOGEN Calculates the value (from the VMS side of things), then
after that, ADD_, MIN_, and MAX_ limits are applied.  Although it would
be NICE that autogen should compare the range of values, it simply
doesn't.   (keep remembering-- it's just a stupid DCL procedure...)

I suspect that if/when dec ever re-does autogen to be an IMAGE instead
of a PROCEDURE, more "Smarts" will be built in.   Until such time, we
(as system managers) simply have to keep adding lines to MODPARAMS.DAT
that tell autogen "don't DO that......"
-- 
Kent C. Brodie - Sr. Systems & Network Manager	 InterNet:  brodie@fps.mcw.edu
Faculty Physicians & Surgeons			 uucpNet:   fps.mcw.edu!brodie
Medical College of Wisconsin			 MaBellNet: +1 414 266 5080

begin 700 sig.file
M+BYW:&%T(&1I9"!Y;W4@97AP96-T(&9O<B!A('1W;RUL:6YE('5U96YC;V1E
?9"!F:6QE+"!A(&-O;&]R('!I8W1U<F4_(" Z+2D@("UL
 
end