After a program is successfully compiled it is ready for immediate execution with the ACUCOBOL-GT runtime. There is no link
Using the Runtime System for details on using the runtime.
On UNIX, Linux, and OpenVMS systems, the runtime executable file is named
runcbl.exe. On some UNIX systems the runtime is provided as a shared object library named
Several distinct runtimes are available for Windows systems. Each is licensed separately.
- The standard Windows runtime is named
wrun32.exe. It is used with all standard deployments
- Thin client deployments use a special runtime named
acuthin is used in conjunction with AcuConnect and a standard runtime, both of which are installed on the application host. See
Thin Client, in the
AcuConnect User's Guide for more information about Thin Client technology.
- The Windows console runtime
crun32.exe supports applications originally developed for Extended DOS and other character-based applications. The console runtime uses
the Windows Console API and runs in a virtual DOS window. See
Windows Console Runtime for more information.
- The Alternate Terminal Manager (ATM) runtime, named
run32.exe, lets you use a 32-bit Windows server in much the same way that some UNIX servers are used. With the ATM runtime, the user
can telnet to the Windows server (with a third-party telnet service) to execute character-based ACUCOBOL-GT programs in the
telnet window. See
Alternate Terminal Manager (ATM) for more information.
- A special CGI runtime supports Windows-based deployment of applications accessed via the World Wide Web. For more information
on these options, see
A Programmer's Guide to the Internet.