Most often, you install an ACUCOBOL-GT runtime license on the server running AcuServer. The license should accommodate the number of concurrent Web runtime users that you anticipate. (If you anticipate 100 concurrent users, you need a 100-user runtime license file on the server in addition to the AcuServer license file.) AcuServer detects the Web control connections and checks out a standard runtime license for each connection if a local license file is not found. When a Web runtime user disconnects from AcuServer by exiting the COBOL program, the runtime license authorization is released and made available to subsequent users. If the number of users exceeds the number of authorizations available on the server at any given time, the COBOL program receives a file status code 9D/105 and this message is output to AcuServer's error log:
You have exceeded the licensed number of clients for AcuServer. If you would like to add clients, please contact your customer service representative
If your COBOL program receives a status code of 9D/105, we recommend that you display a message box stating that the Web file server is busy, and to please retry later.
It is important to note that the Web runtime continues to run even when no license file is available, but in a restricted mode. In restricted mode, programs cannot use the following features:
If an end user tries to perform an activity that is not permitted, your program should present a message that explains why the activity cannot be completed. For example, if an end user tries to print something in restricted mode, your program could display a message that says A software license could not be found. XYZ Software is unable to print. Otherwise, the user might think that the printer is turned off, unplugged, or jammed. Your program should accommodate all of the limitations of a restricted runtime in some manner.
Programs running in restricted mode can use AcuConnect to call programs on a server machine that can use Acu4GL, AcuSQL, and the server's printing facilities. AcuConnect counts the number of concurrent runtimes it launches on the server. Programs running in restricted mode can also use COBOL applets, local sequential and relative files in permissible directories, C$GETURL, ActiveX, and OLE.
If you want to test from COBOL whether a Web control application is running in restricted mode, you can test the SERIAL-NUMBER field of the SYSTEM-INFORMATION item after an ACCEPT from SYS-INFO. If the SERIAL-NUMBER field is SPACES, the COBOL program is being run in restricted mode.