HP OpenVMS Systems

Ask the Wizard

HP OpenVMS Systems

OpenVMS information

» What's new on our site
» Upcoming events
» Configuration and buying assistance
» Send us your comments

HP OpenVMS systems

» OpenVMS software
» Supported Servers
» OpenVMS virtualization
» OpenVMS solutions and partners
» OpenVMS success stories
» OpenVMS service and support
» OpenVMS resources and information
» OpenVMS documentation
» Education and training

Quick Links

» Non-javascript page
» Ask the Wizard

Test Drive OpenVMS

» OpenVMS I64 test drive
» Java test drive

Other information resources available to you include:

» OpenVMS freeware
» ECO kits, software and hardware support, prior version support
» Alpha SRM, ARC, and AlphaBIOS firmware updates
» ENCOMPASS - HP user group
» OpenVMS software downloads, OpenVMS freeware CD-ROM
» OpenVMS firmware locations
» DECconnect passive adaptor charts
» Cables reference guide
» MicroVAX console commands
» OpenVMS student research

Select a topic below to see Questions Frequently Asked by partners

» Using the online documentation library(installing BNU from the asap SDK)
» Global sections(how to create and use.)
» xx$CREATE_BUFOBJ system service(usage)
» Ethernet address(methods of determination)
» Shareable images(cookbook approach to creating one)
» Sharing data/code at absolute addresses(a guide with examples)
» Determining the Alpha microprocessor
» Using GETSYI to get hardware status

Evolving business value

» Business Systems Evolution
» AlphaServer systems transition planning
» Alpha RetainTrust program

Related links

» HP Integrity servers
» HP Alpha systems
» HP storage
» HP software
» HP products and services
» HP solutions
» HP support
disaster proof
HP Integrity server animation
HP Integrity server animation
Content starts here

Ask the Wizard Questions

what is "procsectcnt"?

The Question is:

hello wizard,

what means the describtion of the systemparameter

we don't know what means process SECTIONS that can be

you can help?

thank's for your helping hand

The Answer is:

      A process section is defined as "a group of contiguous virtual pages
    with the same characteristics, such as writability and shareability"
    When you run an image, memory must be segregated into sections to make
    sure it is used correctly. For example, CODE is not writeable, nor are
    constants. You can see the image sections created by the linker for
    a particular program by examining the link map. (see LINK/MAP)

      A complex image may require many process sections, but it's not
    practical to allow an unlimited number, hence the system wide limit
    PROCSECTCNT. The default value (32) is often sufficient, but is perhaps
    a bit on the low side (it was high for 1979). 64 is probably a more
    reasonable value for todays images.

      Note that PROCSECTCNT is not a hard limit. The process section table
    data structure can "overflow" into unused parts of the process working
    set list - for example, if a process's WSEXTENT is less than WSMAX, the
    unused space can be used for extra process section entries. In a pinch
    you may be able to get around a SECTBLFUL error without rebooting by
    reducing WSEXTENT on the process getting the error.

      For all practical purposes, the details are not really important. If
    you are consistently getting SECTBLFUL errors, you should probably
    raise PROCSECTCNT. I wouldn't worry about going as high as 96. If you
    continue to get errors, examine the MAP files to determine why the
    image needs so many sections.