...
Follow these steps to create and gather NLINK Trace Files (aka "workset dumps" or "dump files") to send to Junot Support for help with troubleshooting data problems.
Step-by-step guide
Gather Logs
Use the NLINK Management Module (NMM) to gather diagnostic trace files:
Remove old files (optional). If you are unsure whether existing log files might be helpful, just skip this step.
From the NMM menu, choose either Tools >> Clear Messages, Logs or Options >> Goto Logs Folder.
Clear out any old files and/or folders that you know are irrelevant. You may not be able to delete all the files if NLINK is running, so don't worry about those.
Gather logs.
From the NMM menu, choose Tools >> Gather Logs.
You may choose to deselect any files you know are irrelevant. If you are not sure, just leave everything selected.
Change the name of the destination zip file, if desired.
Optionally, choose the Upload to AWS S3 checkbox (the machine must have internet access)
Click the OK button to create the designated zip file.
Create Logs
NLINK 8x is designed to run in "perpetual logging" mode, but if your particular environment has been set to not generate logs, you will need to follow these steps to create the diagnostic logs.
...
| Panel | ||
|---|---|---|
| ||
NLINK trace files tend to be small, but they do accumulate over time. Use the System Property Keep logs for n days to let the NLINK Manager service clean up the contents of the Logs folder automatically based on file modification date. Note that cumulative log files may not get purged if they are written to frequently, so you should still monitor the Logs folder to purge obsolete files on a regular basis. |
Video
Product Note: NLINK Traces and Logs
...