TNS/E Native Application Conversion Guide

Converting COBOL Programs
TNS/E Native Application Conversion Guide—529659-003
4-4
Changing the Source Program
6. Compile your source program with the native COBOL compiler. For instructions,
see the COBOL Manual for TNS/E Programs .
The native COBOL compiler needs more symbol table space than the TNS
COBOL compiler does. If the native COBOL compilation fails because of dictionary
overflow, use the PARAM SYMBOL-BLOCKS command to increase the space
available for the symbol table, local label table, and embedded SQL statements
and then recompile. The maximum value of the PARAM SYMBOL-BLOCKS
command’s count parameter is 25 for the native COBOL compiler (compared to
14 for the TNS COBOL compiler).
7. Run the COBOL program that you compiled in Step 6.
8. If necessary, debug the program.
The H-series native environment provides different debugging tools than the TNS
environments. See Native Mode Debugging Tools on page 1-10 for an overview of
TNS/E native debugging tools.
Changing the Source Program
Source program changes fall into these categories:
•
General Conversion Tasks
•
Removal Required
•
Possible Changes Required
•
Removal Optional
•
New Features
General Conversion Tasks
If your TNS COBOL program calls obsolete or changed Guardian procedures, replace
them. Change calls to procedures affected by either the Kernel-Managed Swap Facility
(KMSF) or the native process architecture (for example, process creation calls). For
more information on obsolete or changed procedures, see Section 10, Converting
Programs With Guardian API Calls.
Note. The only debugger currently available to TNS/E native COBOL programs is Visual
Inspect.