If the thin client automatic update process fails for any reason, a message box appears and a log file is created on the server by default. This file contains a log of the update operations and details about the failure. The following configuration variables affect the failure notification process:
This configuration variable lets you set the title bar text for the message box that appears on update failure. Its default value is
ACUCOBOL-GT Thin Client
This configuration variable lets you specify the text in this message box. Its default value is
ACUCOBOL-GT Thin Client: Automatic update was unsuccessful
In some cases, you may not want the thin client to inform the user that the automatic update failed. Set this configuration variable to “false” (0, off, no) to configure the thin client so it does not notify the user if the automatic update fails. The default value of TC_AUTO_UPDATE_NOTIFY_FAIL is “true” (1, on, yes). Note that the message box does not appear if the user cancels the Windows installer download process.
You can use this configuration variable to configure the location and name of the log file created on the server. The name can optionally include the hostname of the client machine and the process ID of the server runtime that was managing the automatic update at the time of the failure.
By default, this file is named autoupdate.%c.%p.log, where %c is replaced by the client hostname and %p is replaced by the process ID of the server runtime. The default location is the working directory specified in the alias on the server. The directory must exist at the time of the failure. Otherwise, this file is not created. The location of the log file is relative to the working directory specified in the alias. For example, the following setting:
configures the log files to be created in a directory named updatefailed relative to the working directory. The files are named with the hostname of the client followed by a dot and the process ID of the server runtime, ending with the .log file extension.
The client and server may be in different time zones. You can look at the file’s creation date to see what time the update failed according to the clock on the server, and view the timestamps at the beginning of the lines in the log file to see what time it failed according to the clock on the client.
Set this configuration variable to “true” (1, on, yes) to prevent the creation of a log file for a thin client automatic update failure. The default value of TC_DISABLE_SERVER_LOG is “false” (0, off, no).