Guardian Procedure Calls Reference Manual

Table 55 Per-Processor Limits (continued)
CommentMaximum ValueLimit Description
use the PEEK /CPU N/ MQCINFO
command
Higher messaging performance is achieved
when a message request and/or reply is
cached in an MQC.
2,048 bytes
6
8,128 bytes
7
Maximum MQC size
Larger MQC sizes support a wider range of
message sizes that can benefit from the
MQC caching optimization.
1
All G-series RVUs, H06.20 and earlier H-series RVUs, and J06.09 and earlier J-series RVUs.
2
H06.21 and later H-series RVUs and J06.10 and later J-series RVUs.
3
G06.24 and earlier G-series RVUs.
4
G06.25 and later G-series RVUs; all H-series and J-series RVUs.
5
H06.20 and later H-series RVUs and J06.09 and later J-series RVUs.
6
All G-series RVUs; H06.06 and earlier RVUs.
7
H06.07 and later H-series RVUs; all J-series RVUs.
Table 56 TNS vs. Native Limits
CommentMaximum ValueLimit Description
PEP size; code segment = 128 KB510TNS procedures per code segment
XEP size512Unique external procedures called
from TNS program, per code
segment
Practical limit64 KBTNS procedure size
32 segmentsTNS user code and user library
64 KBTNS total stack and globals
Does not include extended segments data
space.
128 KBTNS total user data space
28 MB eachAccelerated user code, user
library, or system code
TNS/R32 MBNative user code
TNS/E256 MB
TNS/R32 MBNative user library
TNS/E256 MB
TNS/R128Native process SRLs
The native process DLLs do not have to be
contiguous; DLLs and flat segments can be
interspersed in the flat-segment area.
1,000 on TNS/R systems,
700 on TNS/E systems
Native process DLLs
Default = 1 MB on TNS/E32 MBNative stack
This value represents the default size. By
calling the HEADROOM_ENSURE_ procedure
128 KBNative priv stack
you can increase the size in H-series and
J-series systems up to 880 KB.
TNS/R1.1 GBNative globals + heap + flat
segments
TNS/E1.5 GB
1582 System Limits