COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

information on tools that can help you migrate HP C or HP C++ programs to TNS/E, see
the C/C++ Programmer’s Guide.
• pTAL
Recompile pTAL programs with the EpTAL compiler, using the SYMBOLS directive if you
want to reference a pTAL routine in a CALL or ENTER statement. For information about
the EpTAL compiler, see the pTAL Reference Manual.
• Data Alignment
The ECOBOL compiler aligns each level-01 item and each level-77 item on a physical
8-byte boundary, not on a physical 2-byte boundary as the NMCOBOL compiler does.
Offsets from the containing level-01 or level-77 item are the same in both compilers. The
difference in alignment of level-01 and level-77 items for the ECOBOL compiler will not
affect a program unless the program depends on the relative placement in memory of
distinct level-01 or level-77 items. If your program depends on such relative placement,
correct it.
3. (Optional) Put converted routines in a DLL.
If you want to put the routines that you converted to native mode in Step 2 in a DLL, follow
the directions in Dynamic-Link Libraries (DLLs) (page 600)).
4. Compile your source program with the ECOBOL compiler.
For the Guardian environment, see Running the Compiler (page 527). For the OSS environment,
see Chapter 19: Using HP COBOL in the OSS Environment (page 711).
The ECOBOL compiler needs more symbol table space than the NMCOBOL compiler does.
If the ECOBOL compilation fails due to dictionary overflow, use the PARAM SYMBOL-BLOCKS
(page 528) command to increase the space available for the symbol table and embedded
SQL/MP statements and then recompile.
5. Run the HP COBOL program that you compiled in Step 4.
6. If necessary, debug the program.
Source Program Changes
Source program changes fall into these categories:
• General Migration Tasks
• Removal Required
• Possible Changes Required
• Removal Optional
General Migration Tasks
If your HP COBOL program calls obsolete or changed Guardian procedures, replace them. Change
any 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 the obsolete or
changed procedures, see the H-Series Application Migration Guide.
Source Program Changes 959