The way to run this on DQL is:
execute show_sessions
execute list_sessions
Main Topics
Browse All TopicsHi experts,
I support a Documentum 5.3 SP6 implementation. The content server is accessed by a fairly large user base using Documentum Webtop from multiple application servers. It is also accessed by a few custom applications and services utilizing the foundation classes. In addition to this, I have an imaging solution releasing documents to the content store.
I want to know: how do I count the total number of active connections/session on the content server that would inlcude all the users and applications etc.
There must be a DQL or something....
Please let me know
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
omoralesm
Thanks
The problem with list_sessions is that it lists the sessions. How do you know how many there are?
Count_Sessions shows me more the format of results that I'm looking for but I don't know what the columns mean! there are warm sessions and hot sessions etc etc...
What the hell is the difference bewteen all these?
All I need to know is how many connections are active on the content server.
Any comments on those different columns?
Thanks
You'll find this information on the DQL Reference, here is an excerpt of it:
root_start The time when the main server thread (root server process) was started
root_pid On Windows, the process ID of the Content Server process.
On UNIX, the process ID of the root Content Server process.
shared_mem_id The ID of the shared memory segment used by the servers.
This property is returned only on UNIX platforms.
semaphore_id The ID of the semaphore used by the servers.
This property is returned only on UNIX platforms.
session The object ID of the session begun by user_name.
db_session_id The ID of the database session.
typelockdb_session_id The database session ID for type locking
tempdb_session_ids List of temporary database sessions
pid The ID of the session thread (process).
user_name The user name of the user who started the session.
user_authentication The user authentication state for the session. Possible values are password,
ticket, trusted client, change password, or in progress.
If the value is change password, the user logged in for that session can only
perform the change password operation. No other operations are allowed.
client_host The host name of the machine on which the session was started.
client_lib_ver The version number of the DFC in use for the session.
client_locale A verbose description of the clients environment, including the operating
system version, the character set in use,the language in use, and the date format.
start The starting time of the session.
last_used The last time the client session contacted the server.
session_status The session status. Active means that the session is connected and has not timed
out. Inactive means that the session has timed out.
shutdown_flag Records the setting of the immediacy_level argument in the kill method.
last_rpc The last RPC the server ran for the session
current_rpc The current RPC being run by the server for the session
Note that after the RPC is completed the server will not clear this field. Therefore,
if last_rpc and current_rpc have the same value, either the server has completed an
RPC for the session and has not executed another RPC, or the server is running the
same RPC again.
last_completed_rpc The last time theserver completed an RPC for the session
Business Accounts
Answer for Membership
by: omoralesmPosted on 2009-06-04 at 08:34:44ID: 24548118
According to Content Server 5.3 DQL Reference Guide, the LIST_SESSIONS and SHOW_SESSIONS should behave as follows:
LIST_SESSIONS: returns information about all currently active sessions and user_specified number of historical sessions.
SHOW_SESSIONS: returns information about all currently active sessions only.
When you run these commands you can see that the output is exactly the opposite.