Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

increase global sections

SOLVED
Go to solution
Sjors Takes
Advisor

increase global sections

Hi all

For new s/w 190 global sections are required, but:

$write sys$output f$getsyi("free_gblsects")
163

I have modified modparams.dat:

MIN_GBLSECTIONS = 1200 (was 625)

After that I ran Autogen:

$@SYS$UPDATE:AUTOGEN GETDATA SETPARAMS

After a reboot, the free global sections were still 163. Why didn't this number increase?

Thanks in advance. Greetings, Sjors
11 REPLIES
Wim Van den Wyngaert
Honored Contributor
Solution

Re: increase global sections

Do your autogen again or check the output of the previous run. Sometimes autogen finds something suspiscious and cancels the setparams. You need to do the set params as

@SYS$UPDATE:AUTOGEN SETPARAMS

Wim
Wim
Jim_McKinney
Honored Contributor

Re: increase global sections

> Why didn't this number increase?

You only show what is free - not how many sections are SYSGENed. It is probable that the actual number of global sections was/is greater than 1200.

You'll want to get the current GBLSECTIONS value

$ write sys$output f$gets("gblsections")

and then increase your MIN_GBLSECTIONS value above that number.
Peter Zeiszler
Trusted Contributor

Re: increase global sections

Check the SYS$SYSTEM:AGEN$PARAMS.REPORT and see what it has reports for the GBLSECTIONS value.
Steven Schweda
Honored Contributor

Re: increase global sections

ALP $ type SYS$MANAGER:GBL.COM
$ G = F$GETSYI( "GBLPAGES")
$ GF = F$GETSYI( "FREE_GBLPAGES")
$ GC = F$GETSYI( "CONTIG_GBLPAGES")
$ WRITE SYS$OUTPUT -
" Global pages: ''g', free: ''gf', contiguous: ''gc'."
$ G = F$GETSYI( "GBLSECTIONS")
$ GF = F$GETSYI( "FREE_GBLSECTS")
$ WRITE SYS$OUTPUT -
" Global sections: ''g', free: ''gf'."


ALP $ @ gbl.com
Global pages: 3679322, free: 3248256, contiguous: 3232992.
Global sections: 1350, free: 258.
Robert_Boyd
Respected Contributor

Re: increase global sections

Sjors,

You might download SHOW_NODE_INFO.COM from

http://dcl.openvms.org/stories.php?story=05/04/04/7482362

There is a section of information about global pages and global sections that is part of the output.

Robert
Master you were right about 1 thing -- the negotiations were SHORT!
Daniel Fernandez Illan
Trusted Contributor

Re: increase global sections

Sjors

Are you display file SYS$SYSTEM:AGEN$PARAMS.REPORT
to check some error message about MODPARAMS.DAT lines?
It is possible, if line refer to MIN_GBLSECTIONS is EXACTLY
MIN_GBLSECTIONS = 1200 (was 625)
that AUTOGEN has detected an error.

Line will be:

MIN_GBLSECTIONS = 1200 ! (was 625)

(See comment ! character)

Saludos.
Daniel.
Sjors Takes
Advisor

Re: increase global sections

Thanks all.
@SYS$UPDATE:AUTOGEN GENPARAMS SETPARAMS FEEDBACK
Did the job.

Greets, Sjors
John Gillings
Honored Contributor

Re: increase global sections

Sjors,

>For new s/w 190 global sections are required, but:
>
>$write sys$output f$getsyi("free_gblsects")
163
>
>I have modified modparams.dat:
>
>MIN_GBLSECTIONS = 1200 (was 625)

The intended way to deal with this situation is in MODPARAMS.DAT:

ADD_GBLSECTIONS = 190 ! For product "new s/w"

Hopefully, each product with a specific requirement for GBLSECTIONS will have its own line and comment.
A crucible of informative mistakes
Thomas Ritter
Respected Contributor

Re: increase global sections

Sjors, some advice.
When changing system parameters and before rebooting use $ difference/parall to compare the before and after differences in parameters.
This very simple technique will save you.
Consider
+++
$ mc sysgen
use sys$system:alphavmssys.par !Real Version
set/output=users:[autogen]wiza_new_params.txt
show/all
show/special
!!!use sys$system:alphavmssys.old !Previous version
use users:[autogen]wiza_PARAMS_CURRENT.PAR
set/output=users:[sautogen]wiza_old_params.txt
show/all
show/special
exit
$
$differences/parallel/out=differences.lis wiza_new_params.txt wiza_old_params.txt
$type/p differences.lis
$exit
___
Also these days with gigabytes of RAM think big, but not too big. There is very little overhead in having some parameters configured generously.

We have not autogen our production cluster for over 2 years and work load has increased three fold ! Once you know your work mix and expected growth adjust
accordingly.

My AUS 2 cents.
labadie_1
Honored Contributor

Re: increase global sections

In addition to the very good post by Ritter, I do, just after the autogen
$ sea sys$system:AGEN$PARAMS.REPORT; suspect

If the string "suspect" is found, this usually means that I have fat fingered a parameter, so my new value for gblsections will not be here, as I may have done a typo, such as
min_glbsections=1200
instead of
min_gblsections=1200
Heinz W Genhart
Honored Contributor

Re: increase global sections

After executing Autogen I do

$ DIFF/PAR SYS$SYSTEM:SETPARAMS.DAT

This way you can see every parameter changed during last Autogen

Further: Autogen searches for a procedure sys$update:agen$mail.com. If this procedure exists it will be executed by autogen.

I added
$ DIFF/PAR SYS$SYSTEM:SETPARAMS.DAT/out=sys$scratch:agen_diff.tmp
$ MAIL/SUBJECT="Autogen executed on ''F$GETSYI("NODENAME")'" sys$scratch:agen_diff.tmp 'mail_address'

to the procedure SYS$UPDATE:AGEN$MAIL.COM
This way I receive a Email with the differences after executing autogen.

Regards

Heinz