TNS/E Native Application Conversion Guide

Developing a Conversion Strategy
TNS/E Native Application Conversion Guide—529659-003
2-5
Determining Optimization Levels
The recommended solution is to replace the affected procedures with updated
procedures that can handle increased DCT limits:
For more details using the replacement procedures, see the Guardian Procedure Calls
Reference Manual .
Determining Optimization Levels
The native C, native C++, COBOL, and pTAL compilers support three levels of
optimization:
Use optimization level 0 to debug a program, and then use optimization level 1 or 2.
The optimize pragma (in the Guardian environment), the -Woptimize c89 flag (in
the OSS environment), and the -O optlevel c99 flag (in the OSS environment) set
the optimization level for the native C and C++ compilers. The OPTIMIZE directive sets
C-Series Procedure Replacement Procedure
FILEINFO FILE_GETINFOLIST_
GETDEVNAME DEVICE_GETINFOBYLDEV_
CONFIG_GETINFOBYLDEV_
CONFIG_GETINFOBYLDEV2_
FILENAME_FINDSTART_
FILENAME_FINDNEXT_
GETPPDENTRY PROCESS_GETPAIRINFO_
GETSYSTEMNAME NODENUMBER_TO_NODENAME_
LOCATESYSTEM NODENAME_TO_NODENUMBER_
LOOKUPPROCESSNAME PROCESS_GETPAIRINFO_
Optimization Level Characteristics
0 (No optimization)
•
Slower execution
•
Supports symbolic debugging
•
Data always in memory
•
Useful during development and migration; not intended for
production
1 (Intermediate
optimization)
•
Faster execution
•
Supports symbolic debugging
•
Data not always in memory
•
Useful in production
2 (Full optimization)
•
Fastest execution (on average, a 15 percent reduction in
pathlength over level 1)
•
Limited support for symbolic debugging
•
Data not always in memory
•
Useful in production