TNS/E Native Application Conversion Guide

Converting Programs With Guardian API Calls
TNS/E Native Application Conversion Guide—529659-003
10-7
Using Procedures Enhanced to Support the Native
Architecture
Using Procedures Enhanced to Support the
Native Architecture
These procedures have been enhanced to support native processes, native object
files, and DLLs:
NEWPROCESS
NEWPROCESSNOWAIT
OBJECTFILE_GETINFOLIST_
PROCESS_CREATE_
PROCESS_GETINFOLIST_
PROCESSINFO
PROCESS_SETINFO_
PROCESS_SPAWN_
Depending on the operations performed by these procedures, you might need to
specify new or different parameters. For details, see the procedure’s description in the
Guardian Procedure Calls Reference Manual .
Additionally, the NEWPROCESS, NEWPROCESSNOWAIT, and
PROCESS_CREATE_ procedures have been superseded by the
PROCESS_LAUNCH_ procedure. The PROCESSINFO procedure has been
superseded by the PROCESS_GETINFOLIST_ procedure. You might need to replace
calls to these superseded procedures with calls to the replacement procedures to
specify parameters specific to the TNS/E native architecture.
Using Procedures Affected by KMSF
KMSF manages the swap space for native processes and, to a lesser extent, TNS
processes. For more information on this facility, see KMSF on page 1-19. KMSF affects
procedures that specify and return information on swap space.
Use the following procedures to specify or return the swap volume or file of the user
data segment for a TNS process:
NEWPROCESS
NEWPROCESSNOWAIT
PROCESS_CREATE_
PROCESSINFO
PROCESS_GETINFO_
Note. Because the PROCESS_LAUNCH_ procedure is the only procedure to fully support
native process creation, you should replace calls to the NEWPROCESS,
NEWPROCESSNOWAIT, and PROCESS_CREATE_ procedures with calls to the
PROCESS_LAUNCH_ procedure when converting to native mode.