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 a TACL prompt, use the
SCF INFO FILESET *,
DETAIL command.
Functional limit is imposed
by functional limit on
directories (a fileset must
have a directory as a mount
Functional limit: 1,000,000
Theoretical maximum:
33,553,952
OSS filesets per node
point). Theoretical maximum
is determined by maximum
number of device labels.
A smaller limit is
configurable. The default is
500,000Entries in an inode cache
4,096. Prior to RVU
G06.24, the limit was
250,000.
A smaller limit is
configurable. The default is
500,000Entries in a link cache
4,096. Prior to RVU
G06.24, the limit was
250,000.
A smaller limit is
configurable. The default is
16,000.
128,000 bytesBuffer size for Network File
System (NFS) nonretryable
operations
A smaller limit is
configurable. The default is:
OSS message-queue IDs that
can be cached
• 1,024 prior to the
J06.17 and H06.28
RVUs
• 32 prior to the J06.17
and H06.28 RVUs
• 16,384 beginning with
the J06.17 and H06.28
RVUs
• 256 beginning with the
J06.17 and H06.28
RVUs
At an OSS shell prompt use
the ipcs -oq command.
A smaller limit is
configurable. The default is:
OSS message-queue
messages per node
• 16,384 prior to the
J06.17 and H06.28
RVUs
• 1,024 prior to the
J06.17 and H06.28
RVUs
• 8,388,608 beginning
with the J06.17 and
H06.28 RVUs
• 4,096 beginning with the
J06.17 and H06.28
RVUs
A smaller limit is
configurable. The default is:
OSS message-queue length
• 65,535 bytes prior to the
J06.17 and H06.28
RVUs
• 65,535 bytes prior to the
J06.17 and H06.28
RVUs
• 1,073,741,824 bytes (1
GB) beginning with the
J06.17 and H06.28
RVUs
• 1,048,576 bytes (1 MB)
beginning with the
J06.17 and H06.28
RVUs
A smaller limit is
configurable. The default is
32,000 bytes.
OSS message-queue
message length
• 32,000 bytes prior to the
J06.17 and H06.28
RVUs
• 2,000,000 bytes (~2
MB) beginning with the
J06.17 and H06.28
RVUs
417