Guardian Procedure Calls Reference Manual

J System Limits
This appendix presents a series of tables that summarize the architectural and programmatic limits
that apply on NonStop servers.
• Table 53: System-Level Limits
• Table 54: Per-Process Limits
• Table 55: Per-Processor Limits
• Table 56: TNS vs. Native Limits
• Table 57: Enscribe File System Limits
• Table 58: DP2 Limits
For SQL/MP limits, see the "Limits" entry in the SQL/MP Reference Manual. For TMF limits, see
the TMF Configuration and Planning Guide. For the locations of other published limits, See Table 59:
Other Published Limits
Table 53 System-Level Limits
CommentMaximum ValueLimit Description
16Processors per node
255Nodes per Expand network
63Direct neighbors per node
G-series only14Nodes per Fox ring
OSIMAGE must be on the system-load
volume. The OSIMAGE is much smaller, on
128 MBOSIMAGE size
H-series and J-series than on G-series
because the libraries and programs that
were formerly in OSIMAGE are now in
separate object files.
TAL limit. The maximum is 32 for a callable
function and 31 if procedure is callable and
32Number of parameters to a
procedure
variable or extensible. Parameters must also
fit in 64 mask bits. For C/C++ functions that
are not variable or extensible, there is
effectively no limit.
There is no specific limit for identifiers in
C/C++, but function names longer than 32
31Number of characters in procedure
name in TAL or pTAL
characters cannot be exported from the
system library.
Devices share DCT with named processes.65,376Number of entries in destination
control table (DCT)
65,376Logical device numbers (LDEVs)
64KDevice types
64Device/process subtypes
See appropriate subsystem manual.Varies by subsystemNumber of subdevices per device
20Number of tape drives per node in
a labeled tape environment
Names in the form $Xnaa, $Ynaa, or
$Znaa, where a is alphanumeric and n is
numeric.
30,720System-generated names (default,
4-character form)
1579