Knowledgebase

Monitoring FairCom DB Client Activity

FairCom DB provides a variety of ways to monitor FairCom DB client activity. The following sections discuss the available options.

In This Section ctadmn Options for Monitoring Client Activity Server Configuration Options SystemConfiguration Options

ctadmn Options for Monitoring Client Activity

The FairCom DB Administration Utility, ctadmn, can be used to monitor FairCom DB client activity by following these steps:

1. Start ctadmn. When prompted, enter the user ID of a member of the ADMIN group, the user’s password, the optional FAIRCOM.FCS file password, and name of FairCom DB.
2. Select option 4, “Monitor Clients”, from the ctadmn main menu.
3. Select option 1, “List Attached Clients”, from the Monitor Clients menu. ctadmn displays an entry such as the following for each connected client:

UserID: GUEST NodeName:

Task 11 Communications: F_TCPIP

Memory: 25K Open Files: 2 Logon Time: 0:02

Tran Time: 0:01 Rqst Time: 0:00 InProcess Rqst# 13 TRANEND

The meaning of each field is shown in the following table:

Field	Explanation
UserID	The user ID specified by this client when connecting to the server.
NodeName	The application-assigned node name for this client.
Task	The server-assigned task ID for the server thread servicing this client. Entries logged by this thread to the server status log include this task ID (for example, “- User 11”).
Communications	The communication protocol used by this client.
Memory	The current server memory usage attributed to this client thread.
Open Files	The current number of open files by this client.
Logon Time	The total logon time for this client connection.
Tran Time	The current elapsed transaction time for this client’s currently active transaction. Watch for unexpected high transaction times.
Rqst Time	If the text to the right of this value reads “InProcess”, this thread is currently executing a request on behalf of a client and this time is the current elapsed time for this client’s current request. In this case, a large “Rqst Time” value indicates that the server is taking a long time to complete this client’s request. If the text to the right of this value reads “NoRequest”, this thread is waiting for the next client request and this time is the current elapsed time since the completion of the previous client request. In this case, a large “Rqst Time” value indicates that it has been a long time since the server has received a request from this client.
Rqst#	If the text to the left of this value reads “InProcess”, the function number and function name refer to the FairCom DB API function currently being executed on behalf of the client. If the text to the left of this value reads “NoRequest”, the function number and function name refer to the FairCom DB API function that were most recently executed on behalf of the client.

Server Configuration Options

The following server configuration options can be used to monitor client activity:

• Specifying DIAGNOSTICS LOGON_COMM in the server configuration file causes the server to write detailed logon status messages to its console. This option is useful for tracking down the cause of failed client connection attempts.
• Specifying DIAGNOSTICS TRAP_COMM in the server configuration file causes the server to log all communication messages received from FairCom DB clients to the file TRAPCOMM.FCS. This option provides a way to capture the exact sequence of client requests, and if a copy of the initial data and index files are preserved, the cttrap utility can be used to replay this TRAPCOMM.FCS log in order to reproduce the original client activity. Note that using this option may impact server performance.
• Specifying FUNCTION_MONITOR YES in the server configuration file causes FairCom DB to display details about each client request to the function monitor window or standard output. Another variation is to specify FUNCTION_MONITOR <logfile>, which causes the server to log function details to the file named <logfile>. When function monitor output is directed to a log file, the function return codes are included, which makes this option useful for tracking down the occurrence of unexpected FairCom DB errors. Note that using this option may impact server performance.

SystemConfiguration Options

The FairCom DB SystemConfiguration() API function can be used to monitor FairCom DB client activity. SystemConfiguration() returns three values referenced with the following constants used as subscripts in the output array of LONG values as shown in the following table:

Array Subscript	Explanation
cfgLOGONS	Current number of logons.
cfgUSERS	Maximum number of logons set in server configuration file.
cfgMAX_CONNECT	Maximum number of logons set by server activation.