NetCOBOL for SPARC Architecture SAF Subroutines User's Guide

118 Appendix D. CGI To SAF Subroutines Conversion Guide
Web page for invoking applications modified for SAF applications
...
Note: NES checks the extensions to identify applications. Thus, each application
name need not be identical to the .DLL name, but will be the name of extension
(MIME type) registered on NES.
Compilation and Linking Methods
Compilation Method
In the case of CGI applications, there are no particular options for compiling
programs. The only exception is the compilation option "MAIN", which the user has
to set in the main program. On the contrary, the user must not set the compilation
option "MAIN" in a SAF routine because each SAF application must be created in
a.DLL format. In addition, SAF applications require the compilation option shown
below. For details of the compilation option, refer to the "NetCOBOL User's Guide."
• THREAD (MULTI)
SAF applications are designed for multi-threaded operation. Set the compilation
option THREAD (MULTI) in every source program.
Linking Method
In CGI applications, object files are linked to make .EXE files as shown below.
LINK Main-program.obj F3BICIMP.lib LIBC.lib F3BICWSR.lib /OUT:
Execution-format-name.exe
SAF applications, however, must be created in .DLL format. In addition, linked the
import library are different from CGI application program as follows.
Unit of Execution
LINK /DLL Initial-program.obj Work-program.obj End-program.obj
F3BICBDM.obj F3BINSRT.lib F3BICIMP.lib KERNEL32.lib LIBC.LIB
/OUT:Execution-format-name.dll /ENTRY:COBDMAIN
Changing CGI applications into SAF applications means changing process-based
applications into thread-based applications. The user should pay attention to the
following:
• Compilation method
• Accessing common resources