Guardian Procedure Calls Reference Manual

Table 53 System-Level Limits (continued)
CommentMaximum ValueLimit Description
Names in the form $X0aaa or $X1aaa,
where a is alphanumeric except e, i, o, and
u.
65,536System-generated names
(5-character form)
$X..., $Y..., $Z..., $0, $AOPR, $CMON,
$CMP, $DMnn (n is numeric), $IMON,
--Explicitly reserved process names
$IPB, $KEYS, $MLOK, $NCP, $NULL,
$OSP, $PM, $S, $SPLP, $SPLS, $SSCP,
$SYSTEM, $T, $TMP, $TRPM, $TRMS,
$TSCH
Table 54 Per-Process Limits
CommentMaximum ValueLimit Description
0 - 1,023; reserved for customers;
nonprivileged
Depends on whether the
segment is privileged,
Segment IDs (SEGIDs)
1,024 - 2,047; assigned by HP;
nonprivileged
nonprivileged, assigned or
unassigned.
2,048 - 4,095; assigned by HP; privileged
(in two ranges)
4,096 -65,425; unassigned; privileged
65,426 -65,535; reserved internally, used
for special classes of segments
127.5 MBSelectable segment size
G-series RVUs1,120 MBSize of 32-bit flat segment area
1
H-series and J-series RVUs1,536 MB
Available only on H06.20 and later H-series
RVUs and J06.09 and later J-series RVUs.
508 GBSize of 64-bit flat segment area
2
All G-series RVUs, H06.16 and earlier
H-series RVUs, and J06.05 and earlier
J-series RVUs.
64Open Binary semaphores
H06.17 and later H-series RVUs and J06.06
and later J-series RVUs.
65,536
The default limits are 255 incoming
messages and 1,023 outgoing messages.
4,095
3
16,383
4
Concurrent outstanding messages
These limits can be modified separately
through the CONTROLMESSAGESYSTEM
procedure.
The time slice is the amount of time a process
can run at a given priority before it is
2 seconds for G-series RVUsTime Slice
declared CPU-bound and has its priority
decremented.
This value is for NSE-A processors. This value
could decrease on faster processors.
400 milliseconds for H-series
and J-series RVUs
1
The 32-bit flat segment area is shared with any program global data, process arguments and 32-bit heap. DLLs can
overflow into or be explicitly placed in this area as well. In some processes, such as those using sockets, this area is also
subject to encroachment of segments from the QIO subsystem, if the installation has not configured QIO to use system
data space as recommended; see the QIO Configuration and Management Manual.
2
The 64-bit flat segment area is shared with the 64-bit heap of 64-bit OSS processes (beginning with RVUs H06.24 and
J06.13).
3
All G-series RVUs and H06.05 and earlier H-series RVUs.
4
H06.06 and later H-series RVUs; all J-series RVUs.
1580 System Limits