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

Removal Optional
The ECOBOL compiler ignores these items, so you can (but need not) remove them from your
source program.
• LARGEDATA
For the NMCOBOL compiler, the LARGEDATA directive determines whether individual data
items are located in the small data area or the large data area. The default value for the
LARGEDATA directive’s parameter is 64.
The ECOBOL compiler ignores the LARGEDATA directive and issues a warning.
• LESS-CODE
For the NMCOBOL compiler, the LESS-CODE directive determines whether the program
generates code that initializes the Working-Storage Section or Extended-Storage Section or
uses a system call to initialize the Extended-Storage Section.
The ECOBOL compiler ignores the LESS-CODE directive and issues no warning.
• NON-SHARED Directive
For the NMCOBOL compiler, the NON-SHARED directive generates nonshared code (non-PIC).
The ECOBOL compiler, which always generates PIC, ignores the NON-SHARED directive and
issues a warning.
Maintaining Common Source Code
To maintain “common source code” that can be compiled with D44.01 and later RVUs of the
NMCOBOL compiler and the ECOBOL compiler, follow these guidelines:
• Either do not use HP COBOL language features that are not supported by both compilers, or
use conditional compilation to isolate those features.
You can effect conditional compilation with these directives:
◦ IF and IFNOT (page 553)
◦ ENDIF (page 549)
◦ SETTOG (page 567)
◦ RESETTOG (page 561)
• Use separate build scripts to run TNS and native tools, including the NMCOBOL and ECOBOL
compilers.
• For each compilation, use the appropriate file (or files) of dummy routines.
Files of dummy routines enable the compilers to accept ENTER statements that are to be
resolved at program load time (see Table 89: Files of Dummy Routines (page 610)).
Using the Inspect, Native Inspect, and Visual Inspect Debuggers
NOTE: You can debug TNS/E PIC files with either Visual Inspect or Native Inspect.
The Inspect and Visual Inspect interactive symbolic debuggers handle TNS and native HP COBOL
programs differently. For a TNS/R native HP COBOL program, the Inspect debugger’s STEP
command is line-oriented. If the current statement is on a single line, the STEP command steps to
the next statement (that is, the debugger works as the command STEP 1 V works for a TNS HP
COBOL program). If the current statement is on the same line as another statement or statements,
the STEP command steps to the next line on which a new statement starts. The Inspect debugger
cannot step one sentence in a native HP COBOL program (that is, the command STEP 1 S does
not work).
962 Migrating TNS/R Programs to TNS/E Programs