TNS/E Native Application Conversion Guide

Introduction to Native Mode
TNS/E Native Application Conversion Guide—529659-003
1-20
KMSF
KMSF manages:
•
The globals-heap segment and DLL instance data segments (variable and
constant) for TNS/E native processes
•
The memory stack segment, RSE backing store segment, and privileged backing
store segment for TNS/E native processes
•
The main stack segment and the privileged stack segment for TNS processes
•
The user data segment for TNS processes
•
The default extended data segment for TNS processes, unless it is explicitly
specified not to be managed by KMSF
•
Program-allocated extended data segments (selectable or flat segments), such as
those allocated with the SEGMENT_ALLOCATE_ procedure, for TNS and native
processes, unless you explicitly specify them not to be managed by KMSF
For details on how programs can specify that their extended data segments not be
managed by KMSF, see the SEGMENT_ALLOCATE_ procedure in the Guardian
Procedure Calls Reference Manual .
KMSF benefits include speeding up process creation and deletion and reducing the
total size of swap files on disks.
You configure and manage the swap volumes used by KMSF with the NSKCOM utility.
KMSF emits EMS warnings when swap space is running low. For more information on
KMSF, see the KMSF Manual .
KMSF changes the control you have over process swap files. You can still specify the
space you need, but you cannot decide at process creation where the data is
swapped. As a result of this change, commands and procedures related to swap files
might have reduced or no effects. Swap file information from procedures and
commands might have different meanings for native processes. Table 1-2 provides an
overview of these changes. For more details, see the specific procedure or command.