Note that all these settings require that you are running an Aurora kernel (that is, OS/2 kernel version 4.5 or higher: Warp Server for e-business, Warp 4 with at least fixpak 13 installed, or an IBM "Convenience Pack", or eComStation). Otherwise all these settings will be disabled.
VIRTUALADDRESSLIMIT
statement in &cfgsys;
and may be in the range of 512 up to 3072 MB.
If this is set to 512 MB, which is the default (and the only available state with non-Aurora kernels), high memory usage is disabled altogether.
Values in excess of 512 MB will reduce the number of processes that can concurrently run on a system.
See &os2; Virtual Address Space for more information on this topic.
DLLBASING=OFF
statement in
&cfgsys;.
Enabling this setting may prevent fragmentation of the shared arena and thus reduce the likelihood of running out of shared memory, but performance for loading DLLs may suffer.
This corresponds to the SET JAVA_HIGH_MEMORY=1
statement in &cfgsys;.
As with all high memory, this will prevent 16-bit code from accessing that memory. Most notably, this requires that you have TCP/IP 4.1 or higher installed.