To open log files, from the Windows
menu, click .The first part of each log filename indicates which function caused the log file creation. Enterprise Server creates a log file for each of the above functions and closes it when the function is finished. The next time that function runs, a new log file is created.
The end of each Enterprise Server log contains statistics indicating the counts and time spent performing various activities. The term "Tics" in the statistics summary refers to milliseconds. The "Cases" column is the number of times that statistic was recorded.
Function |
Log Filename |
---|---|
Loading ( LOAD or CONFIGURE command) |
Enterprise Server (configfilename) dayname, month day, year time.log where configfilename is the name of the Enterprise Server configuration file. |
Serving a Databridge Client |
databaseClientType Server (ipaddress) dayname, month day, year time.log where databaseClientType is the database type of the Databridge Client, and ipaddress is its TCP/IP address. This log file appears in the subdirectory named for the data source the Client is using. Example: BANKDB\MS-SQL Client Server (192.168.16.2) Friday, December 11, 2009 07-54-47 PM 542.log |
Caching updates |
Cacher (basesourcename) dayname, month day, year time.log where basesourcename is the name of a Server Accessory source. This name appears in both Databridge Server sources tree and the Enterprise Server sources tree. |
Using the enumerating disk function |
EnumerateDisks (localhost) dayname, month day, year time.log |
Using the CODE function |
Code Listing (basesourcename) dayname, month day, year time.log where basesourcename is the name of the data source. This log file appears in the subdirectory named for the data source being mirrored. |
Browsing/interactive configuration through the user interface |
Browser dayname, month day, year time.log Example: Browser Wednesday, December 9, 2009 11-18-11 PM 125.log |
Transferring a file using the XFER command |
File Transfer dateTime.log where dateTime is the start time of the file transfer. This log file appears in a sub-directory named "Xfer from ipaddress" where ipaddress is the host name or TCP/IP address of the Unisys host source of the file transferred, with decimals replaced with underscores. Example: Xfer from 192_168_16_1\File Transfer Monday, December 7, 2009 07-17-21 PMPM 422.log |
Mirroring audit files from the primary DMSII database |
Mirror DMSII Audit (datasource) dayname, month day, year time.log where datasource is the data source being mirrored. This log file appears in the subdirectory named for the data source being mirrored. |
Serving audit mirror files to the host running DBAuditMirror |
AuditMirror Server (ipaddress) dayname, month day, year time.log where ipaddress is the host name or TCP/IP address of the host system running DBAuditMirror. This log file appears in the subdirectory named for the data source being mirrored. |