The following examples are valid entries for either an application launch configuration file or a default application launch configuration file.
The following example binds the application (built with dynamic binding enabled) to COBOL Server installed in C:\SvInstallDir, and uses myces.ini at the location specified.
set SERVERPATH=C:\SvInstallDir set CESDYNAMIC=C:\ces\myces.ini
The following example binds the application (built with dynamic binding enabled) to COBOL Server installed in C:\SvInstallDir using the specified path, and uses ces.ini, located in the bin or bin64 directory of C:\SvInstallDir.
set SERVERPATH=C:\SvInstallDir set CESDYNAMIC=ces.ini
The following example, for any native COBOL application, locates the specified licensing configuration file in the same directory as the application.
set CESDYNAMIC=myces.ini
The following example binds the application (built with dynamic binding enabled) to COBOL Server using the binary files located in the rt-files sub-directory of the application's working directory.
set BINPATH=\rt-files
The following example amends the current PATH. This particular example is a specific workaround when deploying applications that require the character Dialog System (DSCHAR) - in order that the character version of the Dialog System is picked up in preference to the default GUI version of the Dialog System (DSGUI), you need to amend the PATH to the location of DSCHAR.
SETENV PATH=C:\dschar-addpack\bin;%PATH%