Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Table 20 OSS Environment Limits (continued)
To Check Amount Currently
UsedCommentMaximum ValueDescription
At an OSS shell prompt: ps
-lA lists active and zombie
processes.
Beginning with the J06.14
and H06.25 RVUs, EMS
events occur for: limit
warning, limit error, and
status normal.
1
OSS processes per node
• Approximately 160,000
processes (active and
zombie), beginning with
the J06.14 and H06.25
RVUs
For systems running J06.07
and later J-series RVUs and
• Approximately 63,000
for J-series RVUs prior to
H06.18 and later H-series
RVUs, you can also use the
J06.14 and
H06.11–H06.24 RVUs
Guardian PEEK POOL
command and check the
PME entry.
• Approximately 29,000
for H-series RVUs prior to
H06.11 and G06.24
and later G-series RVUs
• For G-series RVUs prior
to G06.19 (prior to SPR
T9050AOU), the limit
was approximately
16,000.
At a TACL prompt, use PEEK.There is no specific limit on
OSS processes in a single
OSS processes per
processor
• Approximately 12,000
total processes beginning
processor. There is a limit on
with the J06.11 and
H06.22 RVUs
total processes (system and
user, Guardian and OSS).
• Approximately 8,000 for
J06.10 and earlier
The limiting factor is the
number of possible process
J-series RVUs and
control blocks (PCBs) per
H06.21 and earlier
H-series RVUs
processor. OSS zombie
processes do not count
against that limit
• Approximately 4,000 for
G06.19 and later
G-series RVUs
• Approximately 2,200 for
G06.08–G06.18 RVUs
(prior to SPR T9050AOU)
• Approximately 1,800 for
G06.00–G06.07 RVUs
4,500OSS file opens per process,
without using the select()
function to manage I/O
For G-series RVUs prior to
G06.26 (prior to NPV
4,096OSS file opens per
application process, using
T9055 G12), the limit was
1,024.
the select() function to
manage I/O
412 Environment Limits