We recommend that you ship the whole of Enterprise Test Server with your application. However to provide backward compatibility, you can still select and ship specific files.
| If you require support for: | Single-threading files needed: | Files needed: |
|---|---|---|
| CBL_EXEC_RUN_UNIT (graphical user interface applications) | cblxecws.exe | cblxecwm.exe |
| CBL_EXEC_RUN_UNIT (character user interface applications) | cblexecs.exe | cblexecm.exe |
| Character user interfaces (for true console applications only) | cblvios.dll | cblviom.dll |
| Character user interfaces (for applications that use the default COBOL text window) | cbldwins.dll | cbldwinm.dll |
| Enhanced ACCEPT/DISPLAY syntax (ADIS) | adis.dll | adis.dll |
| File handling or enhanced ACCEPT/DISPLAY syntax (ADIS) or OO persistence | mffh.dll | mffh.dll |
| Print support module | cblprnt.dll | cblprnt.dll |
Other run-time support files that you might need to ship depending on the functionality that your application uses are as follows:
| If your application uses: | Files needed: |
|---|---|
| Command-line Sort |
|
|
CCI:
|
|
| Client/server binding |
|
| Fileshare |
|
| Host Compatibility Option |
|
|
Micro Focus run trigger program:
|
Note: run.cfg must be placed in a sub-directory named
etc; it is an internal file, and must not be edited manually.
|
| Microsoft Transaction Server |
|
| ODBC |
|
| OUTDD directive or DBCS CODESET support |
|
| Rebuild facility (command-line file recovery tool) |
|
| SQL, OpenESQL, and ODBC |
|
| Web Services support |
|