[Info-vax] page, swap and dump files; AUTOGEN, MODPARAMS.DAT, TESTFILES

[Phillip Helbig---undress to reply]

In article <alpine.LFD.2.00.1108051349001.4139 at libra.gmcl.internal>, Rob
Brown <mylastname at gmcl.com> writes: 

> 
> On Fri, 5 Aug 2011 at 11:06 -0000, Phillip Helbig---undress to reply wrote:
> 
> > I have PAGEFILE1_SIZE=0 in MODPARAMS.DAT yet AUTOGEN with TESTFILES 
> > as the end phase suggests resizing it.
> 
> Does it also not specify the override information saying that the file 
> was set to that size by the user?
> 
> Anyway it will do the right thing.  This example from V7.1:
> 
> 
> AUTOGEN Parameter Calculation Report on node: OMEGA
>    This information was generated at  1-APR-2011 15:20:54.49
>    AUTOGEN was run from SAVPARAMS to SETPARAMS - default execution specified
> 
> ....
> 
> SWAPFILE1_SIZE information (for SYS$SYSTEM:SWAPFILE.SYS):
>  	Feedback information.
>  	   Old value was 9200, New value is 9200
>  	   Maximum observed usage (blocks): 2048
>  	Override Information - parameter calculation has been overridden.
>  	   The calculated value was 8100.  The new value is 9200.
>  	   SWAPFILE1_SIZE calculation has been set to current size by user.
>  	   SWAPFILE1 will not be modified. The file size is within 10%

OK, but do you have SWAPFILE1_SIZE=0?  Looking at the above, it appears 
that it won't be modified since the size is within 10%.  Also, the 
calculated value and the user-set value are also within 10%.

> > ... I don't want to try this out since I don't want to create any 
> > unnecessary files;
> 
> You can delete the unnecessary files after your test.

Right, but if they are too large they will fill up the disk, causing 
other problems.

OK, my mistake: I had PAGEFILE1=0 instead of PAGEFILE1_SIZE=0.  Still,
I'm confused.  If I don't set the size to 0, it wants to set both the
primary and the secondary files to the same size, much more than 10%
larger than the size of the primary file (the only one I have now).  OK.
However, if I set PAGEFILE1_SIZE=0, it comes up with the same 
calculations.  My expectation was that if I constrain the primary page 
file to be small, the secondary page file would be correspondingly 
bigger.