Details
Context of question - Being compared to Teamcenter's log files:
It is difficult to compare errors in the Teamcenter log with errors in the NX log when there are no timestamps in the NX syslog.
Solution
1. The syslog generation in principle is
a. Per session of NX
b. A syslog is generated for EVERY session of NX (however much or little is done within the session)
c. BY DESIGN (for optimization), if no problems occur during an NX session, the syslog will be deleted
after a problem-less session of NX is completed and closed
d. Therefore the ideal is for syslogs to remain only for when a problem DOES occur.
And currently, this is how NX handles syslog generation
2. Timestamping
a. The time stamp at the very top is sourced from the machine / OS localization
b. Could be very important if you are dealing with NX clients across the globe, the time stamp
near the top is per the geographical region of that machine, time zone and language.
c. A timestamp may appear at the bottom of the syslog (barring an abrupt aborting of the session)
3. UGII_KEEP_SYSTEM_LOG
If you need EVERY syslog for EVERY NX session, add an NX environment variable
UGII_KEEP_SYSTEM_LOG= (any of the following, 1, true, yes)
VERY IMPORTANT - There is NOT a "0", "false" or "no"
Therefore the either / or (binary) is to either have the variable UGII_KEEP_SYSTEM_LOG
defined/present (meaning a syslog remains after EVERY session of NX) or
NOT defined / NOT present (meaning the syslog will only remain when a problem occurs
which is the optimally intended design)
4. NX development's best recommended suggestion (and includes provisions for "timers")
Especially if you have particular NX operations of interest you need to monitor and timestamp
a. MACROS - no code
b. Using NX Programming / API
Hardware/Software Configuration
Platform: INTL64
OS: windows
OS Version: 1064
Product: NX
Application: SYSENG
Version: V1903
Function: INSTALL_ISSUES
Ref: 002-8014465