GBLPAGFIL

[Mulder_1]

Please let me know how to calculate the sysgen parameter GBLPAGFIL.

Just wanted to make a comparison with the value suggested by Autogen

Thanks

[Volker Halle]

Hi,

consider to run @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK

$ MC SYSGEN HELP SYS_P GBLPAGFIL contains some explanation.

GBLPAGFIL is consumed by RMS (or RDB) global buffers or application global sections not connected to a file on disk.

Volker.

[labadie_1 · Accepted solution]

You can see how much you still have available

$ ana/sys
SDA> eval @mmg$gl_gblpagfil
Hex = 00000000.0006BA92 Decimal = 440978 SDA$SHARE+39A92
SDA> Exit
SAM_super_info>mc sysgen sh gblpagfil
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
GBLPAGFIL 442624 512 32 -1 Pages D

So on this node, GBLPAGFIL is 442624 and now we still have 440978 available.

[Mulder_1]

Thanks for the info.

Could you please tell me by increasing this sysgen parameter, RMS global buffers be increased ?


Thanks

[Robert Gezelter]

FOX2,

As Labadie and Vollker have already pointed out, GBLPAGFIL controls the amount of space available for global items (e.g., RMS Global Buffers) that are not otherwise associated with backing store.

The control for RMS Global Buffers is on a file by file basis. One of the ways of manipulating this is using SET FILE/GLOBAL_BUFFER=n.

Generally, AUTOGEN computes reasonable values, unless there is something that it has not been informed of (e.g., a file which has not been recently used).

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

[Hein van den Heuvel]

>> Could you please tell me by increasing this sysgen parameter, RMS global buffers be increased ?

Hmmm, maybe you can try to explain the problem before worrying about to detail for somethign that may or might not be related to a solution.

In an other topic (#1266726) you mention VASFUL.
In that topic RMS global buffer were not mentioned in the problem description.
Did they play a role? Is that what changed?

If so, PLEASE upgrade to OpenVMS 8.2 at least, but 8.3 preferrably where the RMS GLobal buffer potential problem with VASFUL is pretty much fixed. RMS was tought to remember its REGIONs and re-maps same sized global buffers back to the last space used for that size which fixes that for all.
Not to mention that in 8.3 RMS will use P2 space for desperate case... but you would eventually run out of P1 if you really eat into P2 over and over.

hth,
Hein.