J06.10 Release Version Update Compendium

Fallback Considerations
Code that was recompiled with the “globalized” compiler option to use the –cross_dll_cleanup
linker option does not need to be recompiled to stop using the –cross_dll_cleanup linker option.
However, recompiling without using the “globalized” option might improve performance.
New Functionality for Non-Local Jumps in Mixed-Language HP COBOL
Programs
With this RVU, the TNS/E Native COBOL compiler and TNS/E Native Run-Time Library (ECOBOL
RTL) introduce support for cobsetjmp( ) and coblongjmp( ), HP COBOL-friendly versions
of the standard HP C functions setjmp( ) and longjmp( ). Like setjmp( ) and longjmp(
), cobsetjmp( ) and coblongjmp( ) provide the functionality for non-local jumps and are
typically used for handling errors and interrupts encountered during program execution.
Applications must call cobsetjmp( ) and coblongjmp( ) from an HP C module (not directly
from HP COBOL).
For more information about cobsetjmp( ) and coblongjmp( ), see the COBOL Manual for
TNS/E Programs.
Migration Considerations
If an HP COBOL application is linked with HP C module(s) that call cobsetjmp( ) and
coblongjmp( ), all HP COBOL components of the application must be compiled with the new
TNS/E Native COBOL compiler released with this RVU and executed on a system with the new
ECOBOL RTL installed.
Any HP COBOL application (that does not use cobsetjmp( ) and coblongjmp( )) compiled
with a TNS/E Native COBOL compiler from a previous RVU will run with the new ECOBOL
RTL without requiring modification or recompilation.
Fallback Considerations
Applications that use cobsetjmp( ) and coblongjmp( ), cannot be executed on systems
running J06.09 or earlier RVUs unless the ECOBOL Run-time Library SPR T0357AAK is installed.
T0357AAK cannot be installed on RVUs prior to J06.07.
16 Application Development Products