| |
Results |
|
Dim: How to enable a listener trace
|
Dim: How to enable a listener trace
|
|
|
|
Dim10: DMAPPSRV/RDBMS character set mismatch in listener trace logs
|
Dim10: DMAPPSRV/RDBMS character set mismatch in listener trace logs
|
|
|
|
Dim14: SDP Tracing: How to enable SDP tracing without restarting Dimensions CM Listener
|
To enable, from the Desktop Client Console window or when logged into DMCLI, run the following command: set sdp_ trace on /user_directory=<drive:\path to a directory> Once this is set, reproduce the issue which you wish to trace.
|
|
|
|
Dim: How to trace an http request after a successful logon or logout in the Dimensions Web Client
|
The most obvious way to perform custom actions at login/logout is to implement HttpSessionListener interface - which is standard Java interface - (with methods sessionCreated/sessionDestroyed) and declare custom listener in web.xml.
|
|
|
|
Dim: How to enable DBIO trace
|
The listener then needs to be restarted in order for this to take effect. However all commands run to the server will be logged. This option must be used for server based or standalone Dimensions commands that are run outside of DMCLI, such as: replicator, pdiff, upload, download etc.
|
|
|
|
Dim: How to set up deployment trace
|
1. Stop the Dimensions CM Listener Service 2. Edit the file $DM_ROOT\dfs\deploy_config.dat and make the following changes 3. Modify the line: #log_dir=c:/temp/ by removing the # and ensuring the on the CM Server that the directory specified exists and is writeable for all users
|
|
|
|
Dim10: Scheduled Jobs - Troubleshooting/Tracing Tips
|
To disable, comment out the line by placing a # at the beginning. The Dimensions listener must be restarted for changes to take effect. If a scheduled job is not running, follow these steps:
|
|
|
|
DimCM: Listener.dat settings
|
There may be occasions when it is necessary to diagnose possible issues with the Dimensions CM Listener. Dimensions provides two special initialization parameters that you can use to start the listener in a mode that will trace internal progress and status information to a log file for debugging purposes.
|
|
|
|
KM-Dim9: ZOS DFS_TRACE_DMPOOL.LOG shows up at the root
|
So change the ZOS Listener started task user’s home directory to a different path will resolve this issue.
|
|
|
|
KM-Dim9: Replicator: Error: Dimensions Replicator does not support the use of the following variables: PCMS_LOG, PCMS_TRACE and SQL_DEBUG.
|
listener and retry the operation.
|
|
|
