Tracing can be enabled using the dmcl32.dll through the dmcl.ini file by including some trace statements in the DMAPI_CONFIGURATION section.
There are two keywords used: trace_file and trace_level.
The trace_file keyword can be specified as either a file name or a directory name. If you specify a directory name, then a trace file will be generated automatically. The name will appear like dmcl_trace_2658878. The seven digits will be generated as unique numbers. These trace files will be created each time a client application is used that initializes the dmcl32.dll.
The trace_level keyword sets the level of trace information put into the trace file. Trace levels are:
0 = Informational messages (Note: no trace will be created on Desktop Client if set to "0")
1 = Trace messages
2 = Warning messages
3 = Error messages
4 = Fatal error messages
10 = Timing information
11 = Load operation information
For more information on the Trace API Server method, please refer to the Documentum Server Reference Manual.
Below is an example of a dmcl.ini file used by a Windows 95 client running WorkSpace 3.1.
#Default DMCL.INI. Refer to DMCLFULL.INI for other options
# Assuming No Network File System
# Assuming No Compression for Content Tunneling
[DOCBROKER_PRIMARY]
host = barracuda
port = 1489
#host = shark
[DMAPI_CONFIGURATION]
cache_query = F
trace_file = c:\tracefiles
trace_level = 3
Example:
[DOCBROKER_PRIMARY]
host =10.47.101.119
port =1489
[DOCBROKER_BACKUP]
host =10.47.101.120
port =1489
[DMAPI_CONFIGURATION]
cache_queries = T
token_storage_enabled=F
token_storage_path=D:\Documentum\apptoken
secure_connect_default=try_native_first
client_codepage=UTF-8
client_os_codepage=UTF-8
max_session_count=1000
connect_pooling_enabled=T
cache_query =F
trace_file=c:\trace.log
trace_level=10
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment