Logging

The hospitality service logs its own activity to the HOSTELn log, where n is the server instance number.

In most cases, there is only one instance so the log will be named HOSTEL1. Systems licensed and configured for multiple PMS instances may have a HOSTEL2 log as well (and possibly others, depending on the instance count).

Log files use the file extension .LTT and are stored in the path C:\DuVoice\TRACELOGS.

Each night around midnight, the log files "roll over," meaning the current log HOSTEL1.LTT is renamed as HOSTEL1-YYYYMMDD0000.LTT, or something similar, where YYYYMMDD is the year, month and day of the content of the file (that is, the date that most or all of the log entries were logged). Older files are moved to the ARCHIVE sub-folder.

Log files may be viewed using the Trace Display application, shown below. Refer to the Trace Display page for more details on using this utility.

The example above is for the HOSTEL1 log, showing start of a session. Among other things, it indicates a TCP link to a PMS using the Nortel protocol, the receipt of a polling message and some message traffic with the PMS Monitor application.

The log file contains the following fields, shown as columns in the dialog above.

Column	Description
Log	The base name that identifies which log the entry was logged to. For the PMS link log, this will always be PMSLINK followed by the server instance number. In most cases, it would be PMSLINK1.
PID	The process ID of the process from which the log entry was generated.
TID	The thread ID of the thread from which the log entry was generated.
Date-Time	The date and time when the log entry was logged. Format is Year/Month/Day-Hour/Min/Sec.msec. All values are padded with leading zeros; the millisecond value is padded to three digits and all others to two digits. The hour value is always in 24-hour clock notation.
Filter	Filter level. Can be ignored.
Data	The actual log statement generated by the service. Log statements can be a little cryptic and are generally intended as a debugging aid for the manufacturer's technicians and developers. Still, they can sometimes be useful even to on-site technicians to verify or troubleshoot certain issues.