Documentum Connection Utilities, Part III

This is the third and final post on Documentum-supplied connection utilities in the %DM_HOME\bin directory, although there are more intriguing files in there to explore.  This post is about the dm_who and dm_error scripts.

dm_who

The dm_who AWK script is a thin wrapper around the APPLY API function LIST_SESSIONS.  It simply lists all users that are currently connected to the Docbase, when they connected and from where they connected.

Example:

dmawk32 -f dm_who.awk -- repo1 -Udmadmin -Ppassword

Current users on docbase 'repo1'

User            Connected From  Start Time            Last Activity         Session ID
~~~~            ~~~~~~~~~~~~~~  ~~~~~~~~~~            ~~~~~~~~~~~~~         ~~~~~~~~~~
dmadmin         repo1           6/10/2010 11:27:16 A  6/10/2010 11:27:16 A  0101d93580042a1b
dmadmin         repo1           6/10/2010 10:58:03 A  6/10/2010 11:23:03 A  0101d935800429fd
dmadmin         repo1           6/9/2010 3:04:35 PM   6/10/2010 11:27:07 A  0101d93580042902
dm_fulltext_in  repo1           6/10/2010 11:17:56 A  6/10/2010 11:20:06 A  0101d935800429dd
dm_fulltext_in  repo1           6/10/2010 11:17:57 A  6/10/2010 11:18:59 A  0101d935800429dc
dm_fulltext_in  repo1           6/10/2010 11:17:57 A  6/10/2010 11:18:59 A  0101d93580042993
dm_bof_registr  repo1           6/10/2010 11:16:04 A  6/10/2010 11:16:04 A  0101d93580042a06
JamesA          repo1           6/10/2010 10:05:16 A  6/10/2010 10:05:16 A  0101d935800429a0
AllenZ          repo1           6/10/2010 9:56:32 AM  6/10/2010 9:56:32 AM  0101d93580042928
PeterQ          repo1           6/10/2010 9:13:01 AM  6/10/2010 9:13:02 AM  0101d93580042916
AlmaP           repo1           6/10/2010 8:17:11 AM  6/10/2010 8:17:11 AM  0101d9358004293c

Local Usage
If you would like to use this tool from your workstation instead of from the Content Server, copy the following files to a directory on your hard drive:

  • dm_who.awk
  • dmawk32.exe
  • dmcl.dll

dm_error

The dm_error AWK script will lookup errors generated by the Content Server and provide a brief description of the cause of the error and possible actions to take to correct the error.  The script parses through the set of error files (*.e) in the %DM_HOME%\messages directory looking for a match to the error you pass on the command line.  The script returns no output if it cannot match the error passed in.

Example:

C:\Documentum\product\6.5\bin>dm_error DM_SESSION_E_CLIENT_AUTHENTICATION_FAILURE

[DM_SESSION_E_CLIENT_AUTHENTICATION_FAILURE]
        "Failed to authenticate client.  Please check server log for
        more detail."
CAUSE:  The client installation sent a certificate that uniquely
        identifies the client instance.  The Content Server was unable
        to successfully verify this certificate.
ACTION: Check the reason listed in the error message as to why
        the certificate failed to verify.

A nice feature of the script is that you don’t have to search on complete error messages, you can search on partial messages or even just single words.

Example:

C:\Documentum\product\6.6\bin>dm_error user_not_exist

[DM_ACL_E_USER_NOT_EXIST]
       "The owner_name or accessor_name '%s' given in the ACL '%s' does
       not exist."
CAUSE: The owner_name or accessor_name given does not exist.

As nice as it is to look up errors with the dm_error script, it might be nicer to just have a set of static web pages with all the errors and corrective actions listed.  That will be the topic of next week’s post.

Advertisements

About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: