COBOL Manual for TNS and TNS/R Programs

Migrating TNS Programs to Native Programs
HP COBOL Manual for TNS and TNS/R Programs—522555-006
33-2
Reasons to Migrate
Topics:
•
Reasons to Migrate
•
Migrating HP COBOL Programs
•
Data Alignment
•
Source Program Changes
•
Development and Management Changes
•
Maintaining Common Source Code
•
Using the Inspect and Visual Inspect Debuggers
Reasons to Migrate
A cost is associated with migrating from TNS HP COBOL to native HP COBOL, but in
most cases, it is minor. You must decide whether the long-term return justifies the
expense.
The reasons to migrate to native HP COBOL are:
•
Native object code does not need to be accelerated
•
More code space
The code space limit for a TNS HP COBOL program is 128 KB. For a native
HP COBOL program, it is 32 megabytes.
•
More data space
The data space limit of approximately 60 KB for the sum of all of the Working-
Storage Sections and File Sections of a TNS process does not apply to native
HP COBOL programs. The Working-Storage Section and the Extended-Storage
Section are the same in native HP COBOL. The small data area is limited to
32,768 characters, but you can use the LARGEDATA directive to put additional
data items in the large data space.
•
Native SRLs (for TNS/R) or DLLs (for TNS/E) are consulted automatically
If a TNS HP COBOL 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).