The eleventh, optional, step in creating your Dialog System application, is to link Dialog System object modules to your application to create a single executable object.
This chapter explains:
The following Dialog System object modules are provided:
|dsrun.obj||DSRUN.o||Standard entry module to Dialog System (character and graphical)|
|dscrun||DSCRUN.o||Interface to character DSCHAR|
|dsfld.obj||DSFLD.o||Screen field handler|
|dsrtns.obj||Service routines for shifting and filling data|
|dscvalrn.obj||DSCVALRN.o||Field validation routine|
|dserrhan.obj||DSERRHAN.o||Error file handler|
|dstracer.obj||DSTRACER.o||Dialog trace routine|
|dsdlgini.obj||DSGLINI.o||Initialization for trace routine|
|dsc.obj||DSC.o||Replacement for Dsrun if the application calls Dialog System via the Trap|
|DSTERM.o||Terminal type dependencies|
|DSLCONV.o||Native line drawing routine|
|DSUSRCAL.o||User routine interface|
|System file locator
Handles variable screen size for menu placement
|dscomp.obj||DSCOMP.o||Comp data type handler|
|dspanels.obj||PANELS.o||Micro Focus panels|
|dsnlsrtn.obj||DSNLSRTN.o||NLS support routine - needed only if NLS case-folding is required|
|DSUSRFMT.o||User field formatting|
Depending on the features your application uses, you might not require all of these object modules. Under UNIX, use -X module-name to exclude any such modules. The following sections list the object modules that production applications and applications in development require.
The following table lists the object modules required by production applications:
|All Dialog System applications||dscrun.obj
|Applications using field validation||dscvalrn.obj
|Applications using user validation||dsusrval.obj||DSUSRVAL.o|
|Applications using comp, comp-x, comp-5, comp-3 data types||dscomp.obj||DSCOMP.o|
|Applications using field formatting||dsusrfmt.obj||DSUSRFMT.o|
|Applications using Micro Focus PANELS||dspanels.obj||PANELS.o|
The following table lists the object modules required by applications in development:
|Applications that use the trace facility||dstracer.obj
|Applications that call Dialog System via the Trap||dsc.obj
For more information about using trace, see the section Using the Trace Facility in an Executable Object.
When you have fully tested an application, you should re-link the application without any of these modules to create a smaller production object.
To link your program on Windows systems, use the following command line:
||is the name of your application.|
||is the name of a linker response file. This is a text file that contains a list of all the Dialog System object modules to be linked to your application.|
If you are using file handling, you must link in ExtFH. If you are using user formatting, you must link in Dsusrfmt. If you are using user key translation, you must link in Dsusrtrn.
The following linker response files are provided with Dialog System:
|dsc.lnk||Contains all the object modules listed in the section Dialog System Object Modules except those that are required for debugging purposes only. If you use this file, your application definitely has all the dialog objects that it needs. However, if your application does not use all the Dialog System features (such as field validation), you create a larger object than is necessary.|
|dscbasic.lnk||Contains only those modules that are required for any
Dialog System application to run, which are:
|dscdebug.lnk||Contains all the object modules required for debugging a Dialog System application.|
Links ExtFH and Dsusrfmt for file handling and user formatting.
You can, of course, create your own custom linker response file.
To link your program on UNIX, use a command line of the form:
cob -xv prog module-name...
||is the name to be given to the executable object|
||is the name of an object module to be linked into the object.|
Dsclink is a utility that generates the appropriate linker files and calls the linker to create an executable file. You can use it directly or use it as a template for your own linking procedure to suit your application. It is supplied as a Windows batch file.
dsclink object-name[+object-name...] /d /t /nc /nv /p /nls /st
where the parameters are:
||An object name. The executable (.exe file) is given the same name as the first object filename. You can specify multiple object names by concatenating them with the plus sign. You cannot specify a linker response file in this list because Dsclink creates one and you can use only one as input to the linker.|
||Debug version. Specify this parameter to use the Trap option, which also enables you to use Trace.|
||Trace version. Specify this parameter to use the Trace option without the Trap. If you also specify the /d parameter, it overrides the /t parameter.|
||No COMP support.|
||No field validation support.|
||National Language (case folding) support.
If you use the supplied utility dsclink.bat (Windows), a switch allows you to control this simply.
The linker file DSC.lnk has also been amended to include reference to these NLS supporting .obj files.
||Static linked application (lcobol). Default is shared run-time linked application (coblib).|
Use dsclink.bat to create Windows Dschar executables.
Before linking, ensure your LIB environment variable contains the paths to ...cobol\lib, ...ds\charmode, and any other libraries that your application requires.
Creates customer.exe for Windows that links ExtFH and Dsusrfmt for file handling and user formatting.
You might wish to use the trace facility while you test an executable object. To do this, add code to your application to turn the trace facility on or off, using the following steps:
Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.