- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: PROCSECTCNT documentation
Operating System - OpenVMS
1752305
Members
5120
Online
108786
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2009 12:40 PM
тАО03-01-2009 12:40 PM
Hello,
I get following error when I try to start my application.
"process or global section table is full"
When I increase SYSGEN Parameter PROCSECTCNT to form 256 to 1000 the application starts. OK.
What is the impact on all other processes running on the same I64 server?
Is there any documentation about this sysgen parameter;
Of course there is the help in SYSGEN.
%LIB-E-ACTIMAGE, error activating image -SYSTEM-F-SECTBLFUL, process or global section table is full
%TRACE-E-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
LIBRTL LIB$FIND_IMAGE LIB$FIND_IMAGE_SYMBOL
1812 0000000000002800 FFFFFFFF901BC750
I get following error when I try to start my application.
"process or global section table is full"
When I increase SYSGEN Parameter PROCSECTCNT to form 256 to 1000 the application starts. OK.
What is the impact on all other processes running on the same I64 server?
Is there any documentation about this sysgen parameter;
Of course there is the help in SYSGEN.
%LIB-E-ACTIMAGE, error activating image -SYSTEM-F-SECTBLFUL, process or global section table is full
%TRACE-E-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
LIBRTL LIB$FIND_IMAGE LIB$FIND_IMAGE_SYMBOL
1812 0000000000002800 FFFFFFFF901BC750
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2009 01:27 PM
тАО03-01-2009 01:27 PM
Solution
Mario,
As documented in the internal SYSGEN HELP text, the increased value increases the size of the process header.
Since this increase is 32 bytes/section, I would generally not be concerned. Increasing PROCSECTCNT from 256 to 1,000 will only increase the process header by less than 24K (K==1024 bytes).
See the OpenVMS Internals and Data Structures Manual for details of the layout of the process header.
The impact of increasing PROCSECTCNT is generally small.
- Bob Gezelter, http://www.rlgsc.com
As documented in the internal SYSGEN HELP text, the increased value increases the size of the process header.
Since this increase is 32 bytes/section, I would generally not be concerned. Increasing PROCSECTCNT from 256 to 1,000 will only increase the process header by less than 24K (K==1024 bytes).
See the OpenVMS Internals and Data Structures Manual for details of the layout of the process header.
The impact of increasing PROCSECTCNT is generally small.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2009 01:29 PM
тАО03-01-2009 01:29 PM
Re: PROCSECTCNT documentation
Hello Mario.
The sysgen parameter description (you indicated those already) for this item is pretty clear:
MCR SYSGEN
SYSGEN> help SYS_PARAMETERS PROCSECTCNT
:
"PROCSECTCNT sets the number of section descriptors that a process can contain. Each section descriptor increases the fixed portion of the process header by 32 bytes. Set a value greater than the maximum number of image sections in any section to be run, as indicated by the linkage memory allocation map for the image."
>> What is the impact on all other processes running on the same I64 server?
24KB memory set aside ((1000-256)*32 ).
That's probably 1 extra physocal page touched, and 2 unused.
>> Of course there is the help in SYSGEN.
How about ANALYZE/SYSTEM ... SET PROC ... SHOW PROC /PST
That should tell you how many you really need. It can help figure out WHICH IMAGE contributes how many sections.
For example:
$ pipe write sys$output "SHOW PROC/ID=20200487/PST" | anal/system | perl -pe "$x{$1}++ if /](\S+);/; print if /allo/} { for (keys %x
) { print qq($x{$_}\t$_\n)}"
Last entry allocated 00000033
5 CMA$LIB_SHR.EXE
8 DCE$SOCKSHR_IP.EXE
2 DPML$SHR.EXE
1 WSI$MESSAGE.EXE
1 CXXL$LANGRTL.EXE
1 WSI$COMMON_SS.EXE
6 WSI$COMMON.EXE
1 DCL.EXE
6 DTSS$SHR.EXE
2 DCE$KERNEL.EXE
3 WSI$MANAGER.EXE
1 SECURESHRP.EXE
3 WSI$IPCSHR.EXE
3 CMA$OPEN_LIB_SHR.EXE
5 DCE$LIB_SHR.EXE
1 DCE$RPC_MSG.EXE
2 CXXL$011_SHR.EXE
hth,
Hein.
The sysgen parameter description (you indicated those already) for this item is pretty clear:
MCR SYSGEN
SYSGEN> help SYS_PARAMETERS PROCSECTCNT
:
"PROCSECTCNT sets the number of section descriptors that a process can contain. Each section descriptor increases the fixed portion of the process header by 32 bytes. Set a value greater than the maximum number of image sections in any section to be run, as indicated by the linkage memory allocation map for the image."
>> What is the impact on all other processes running on the same I64 server?
24KB memory set aside ((1000-256)*32 ).
That's probably 1 extra physocal page touched, and 2 unused.
>> Of course there is the help in SYSGEN.
How about ANALYZE/SYSTEM ... SET PROC
That should tell you how many you really need. It can help figure out WHICH IMAGE contributes how many sections.
For example:
$ pipe write sys$output "SHOW PROC/ID=20200487/PST" | anal/system | perl -pe "$x{$1}++ if /](\S+);/; print if /allo/} { for (keys %x
) { print qq($x{$_}\t$_\n)}"
Last entry allocated 00000033
5 CMA$LIB_SHR.EXE
8 DCE$SOCKSHR_IP.EXE
2 DPML$SHR.EXE
1 WSI$MESSAGE.EXE
1 CXXL$LANGRTL.EXE
1 WSI$COMMON_SS.EXE
6 WSI$COMMON.EXE
1 DCL.EXE
6 DTSS$SHR.EXE
2 DCE$KERNEL.EXE
3 WSI$MANAGER.EXE
1 SECURESHRP.EXE
3 WSI$IPCSHR.EXE
3 CMA$OPEN_LIB_SHR.EXE
5 DCE$LIB_SHR.EXE
1 DCE$RPC_MSG.EXE
2 CXXL$011_SHR.EXE
hth,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2009 03:25 PM
тАО03-01-2009 03:25 PM
Re: PROCSECTCNT documentation
Mario,
If you're worried about increasing PROCSECTCNT, and affecting all processes, you may be able to increase the number of sections available to a particular application for a specific process by decreasing the WSEXTENT of that process.
The process section table and the working set list grow into each other. Any unused space in the WSLE is available for additional process sections. PROCSECTCNT is the *minimum* available).
The WSLE is sized by WSMAX. Most modern systems set PQL_MWSEXTENT to WSMAX, so the entire WSLE is used. You would need to reduce PQL_MWSEXTENT, so you can set the WSEXTENT for an individual process lower than WSMAX. That should free up some space in the WSLE to be used for process section table entries.
(on the other hand, an extra page or two per process is unlikely to break the bank).
If you're worried about increasing PROCSECTCNT, and affecting all processes, you may be able to increase the number of sections available to a particular application for a specific process by decreasing the WSEXTENT of that process.
The process section table and the working set list grow into each other. Any unused space in the WSLE is available for additional process sections. PROCSECTCNT is the *minimum* available).
The WSLE is sized by WSMAX. Most modern systems set PQL_MWSEXTENT to WSMAX, so the entire WSLE is used. You would need to reduce PQL_MWSEXTENT, so you can set the WSEXTENT for an individual process lower than WSMAX. That should free up some space in the WSLE to be used for process section table entries.
(on the other hand, an extra page or two per process is unlikely to break the bank).
A crucible of informative mistakes
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP