Cybersecurity
DevOps Cloud
IT Operations Cloud
Did you know that you can now do logging from within the Dimensions CM Desktop Client without having to stop/restart your Dimensions CM Listener or Processes?
This is one of the new features of Dimensions 14.1.
So what do you need to do?
set cmd_trace on /user_filename="<drive>:\<path to a directory on the server>\cmdLogfile.log"
set dbio_trace on
set sdp_trace on /user_directory="<drive>:\<path to a directory on the server>"
Note: All logs will be written to the Server.
set cmd_trace off
set dbio_trace off
set sdp_trace off
So what will this give me?
You will now have 3 files which will aid us in helping you to debug your issue. Providing these files to Serena Support will help us to determine what our next steps are.
What do these log files provide you and how is this different than the tracing which is enabled in the Listener.dat file?
The listener.dat file tracing, also known as DFS tracing, helps us to debug connection and or process problems when first attempting to login or starting up Dimensions.
The cmd_trace logging provides us with connection details and the command which was ran by the user. This records the commands similar to what you see in the Console view of the Desktop Client.
The dbio_trace and sdp_trace files provide us with details of the commands which we use to communicate between the Dimensions Server and the database. Both files together give us a broader, more extensive view of what is happening.
Also, please check out our Solution S140288 on the Knowledgebase.
There is also a KBTV Video to help if needed.