QIO Configuration and Management Manual

Configuring the QIO Subsystem
QIO Configuration and Management Manual—424717-008
2-9
Configuring QIO to Reside in System Data Space

You can specify an attribute multiple times in the configuration file, but only the last
attribute processed is applied.

Blank lines are ignored.

The configurations specified are not case-sensitive.

Only one configuration parameter is allowed per line.
If an invalid or undefined parameter is found in the configuration file, QIO will not start,
and an EMS message is issued.
Example Configuration Files
The following example sets all CPU pool sizes to 64 MB:
PoolSize 64MB
The following example specifies that processor 1 has its QIO segment in Kseg2:
CPU 1
SegmentType 202
The following two examples specify that all processors are to run in Kseg2:
SegmentType 202
and
CPU -1 SegmentType 202
Configuring QIO to Reside in System Data Space
One way to solve many heap and flat segment memory problems is to move QIO to
the system data space area by configuring the QIO configuration file. (For more
information, see Understanding the Configuration File on page 2-7.)
The system data space area is privileged data space reserved for the NonStop OS and
system processes.
Moving QIO to system data space frees QIO shared memory space such that the
globals and heap, and flat memory space can use this empty space to grow. This move
might provide enough space for large process globals and process heap space
requirements, and also solve the problem of not enough free space for program
allocations in flat memory.
Note. In system data space, the QIO size is limited to 128 MB for NonStop S-series and 256
MB for Integrity NonStop NS-series. However, for H06.22/J06.11 and all subsequent RVUs, the
maximum QIO segment size for Integrity NonStop NS-series is increased to 512 MB, while the
default size remains 256 MB.