The ACUCOBOL-GT Run Time

After a program is successfully compiled it is ready for immediate execution with the ACUCOBOL-GT run time. There is no link step. See Using the Runtime System for details on using the run time.

On UNIX, Linux, OpenVMS, and MPE/iX systems, the run time executable file is named runcbl or runcbl.exe. On some UNIX systems the run time is provided as a shared object library named libruncbl.so or libruncbl.a.

Several distinct run times are available for Windows systems. Each is licensed separately.

• The standard Windows run time is named wrun32.exe. It is used with all standard deployments
• Thin client deployments use a special run time named acuthin.exe. acuthin is used in conjunction with AcuConnect and a standard run time, 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 run time crun32.exe supports applications originally developed for Extended DOSand other character-based applications. The console run time uses the Windows Console API and runs in a virtual DOS window. See Windows Console Runtime for more information.
• The Alternate Terminal Manager (ATM) run time, 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 run time, 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 rum time 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.