How Your Program Executes

To execute your program, the Web runtime actually makes a copy of it, delivers the copy to the browser client, and then executes the copy. Because the Web runtime utilizes the browser cache, the cache retains a copy of the object file as long as it is not reloaded. When the application is closed, the copy is removed as well.

Because of browser limitations, you cannot run multiple instances from a single Web page. When your browser shuts down, the Web runtime instance also shuts down. For each browser process, you can run only one instance of the Web runtime. However, you can run multiple browser processes, each hosting a single instance of the Web runtime.

Although the recommended method of executing the ACUCOBOL-GT Web Runtime is with the <OBJECT> tag, it can be executed by the browser in direct response to receiving data with the MIME content type, "application/vnd.acucobol." Internet Explorer looks at the Windows Registry to execute the program.

The browser loads the Web runtime and feeds it the data coming from the Web server. In this context there is no concept of a command line.

To pass "command line" style parameters to the ACUCOBOL-GT Web Runtime, you must specify them in HTML when you invoke the application in your Web page. Note that any file specified as a runtime option that requires write access (such as "errors.txt") is written to the directory listed in the authorization file, "acuauth.txt". If the authorization file is missing, an error results.