TNS/R Native Application Migration Guide

Introduction to Native Mode
TNS/R Native Application Migration Guide—523745-001
1-19
Constraints of Native Mode
°
Native shared run-time libraries (SRLs) are consulted automatically
If a TNS COBOL85 program calls utility routines, it must put the libraries that
contain those routines (one or more of COBOLLIB, CBL85UTL, and CLULIB)
on search lists (using the compiler directives SEARCH, LIBRARY, and
CONSULT).
For a native COBOL85 program, search lists are optional. If a program does
not have search lists, or if the compiler cannot find an external reference in the
files on the search lists, the compiler automatically searches the SRLs
ZCOBSRL and ZCRESRL and then the file NMCOBEXT (the native equivalent
of COBOLEXT).
ZCOBSRL contains the COBOL utility routines which, for TNS COBOL85,
resided in the system library, COBOLLIB, and CBL85UTL. ZCRESRL contains
the COBOL run-time routines which, for TNS COBOL85, resided in the system
library or in CLULIB.
Constraints of Native Mode
Before you start migrating applications to native mode, be aware of the constraints of
the native environment:
•
pTAL, unlike TAL, cannot contain embedded SQL statements.
•
Programs that contain embedded SQL must use the SQL release 2 feature set.
•
TNS object code, accelerated object code, and native object code cannot be mixed
in one program file.
•
A program and its user library must both be native object files.
•
Mixed-language programs can consist only of C, C++, COBOL85, and pTAL.
•
Native object files do not run on TNS systems such as the NonStop Cyclone
system.
•
NonStop DCE programs cannot be converted to native mode at this RVU.
•
Customer-built native programs cannot contain privileged code.
•
Native COBOL85 does not support fault-tolerant process pairs.