Use this page to view the communications processes console log for this enterprise server.
To access this page:
Click the radio button to the left of this control if you want to view a subset of the entries. Then specify the start and end of the subset in the two entry fields to the right. Click Refresh to view the specified subset.
Click this if you want to view a subset of the entries at the end of the log. Then enter the number of entries you want to view in the entry field to the right. The default is that the last 10 lines are shown. Click Refresh to view the specified subset.
Shows the number of the event. Events are numbered in chronological order, with the most recent last.
Shows a description of the event. Each description starts with the date and time it occurred.
Click this if you want to view the entire log. It should open in another browser window.
If the status of the server is anything other than "Started", and the Directory Server is running on your machine, shows the location on your machine of the most recent Communications Server console log for the server. If you click the right-pointing arrow at the end of the location, the file should open in another browser window. If the file fails to open, you can go to the location and open it from there.
Unless you have customized your system, there is only one Communications Server console log file (log.html). This file resides in the directory you specified in the System Directory field on the Properties tab for the server. This log file may become quite large, as the system is continually appending data to it.
If you wish to configure your system to have more than one log file, you can enable the rotating log file feature. To do this, you edit the file mf-server.dat file, located by default in the %ProgramFiles(x86)%\Micro Focus\Visual COBOL\bin (Windows) or $COBDIR/etc (UNIX).Add two parameters under [logging]:
files=number | Specifies the number of log files before rotation occurs. |
filesize=kilobytes | Specifies the size in kilobytes of each log file. |
Example:
[logging] files=3 filesize=100