Using CitectSCADA > Monitoring and Debugging Runtime > Using the Kernel > Page Table
Page Table

Contains information about Citect's runtime data structures. This area is very extensive and is initially a bit difficult to navigate. Currently there are about 50 tables of information - most of which are only relevant in specific circumstances and are otherwise not useful.


Page Table [<Name>]



Optionally the name of the table to display.

Use Page Up and Page Down keys to navigate through the table list. Use Up Arrow and Down Arrow keys to scroll the table data.

The MASTER_TABLE (Table 1) lists every table. The following tables are particularly useful:

Page Table Stats

This very useful table contains the cycle and execution times of every task that is running in Citect. The Execution time is the time taken for the entire task to run. The Cycle time is the time between when a task starts and when it starts again. The CPU is the percentage of total available CPU that the task is using (fast tasks often have 00 CPU).

The Citect 0 entry is the display task (graphics page updates) for the main window. That is, the total time taken for the Client to request data from the I/O Server, the I/O Server to get the data and send it back to the Client, and the Client to update the display.

Note: Citect 0 corresponds to the display task for the main window. Citect 1 for the first child window, Citect 2 for the third, and so on.

The CodeX entries correspond to Cicode tasks, where X is the handle of the task. You can find out which task corresponds to which handle by viewing Cicode table.

Note: There will be a Trend Acq entry for every different trend sampling period you have defined in your project.

Page Table Cicode

This table contains a list of Cicode tasks currently running. It contains the task name, handle and running state, as well as some statistics. CPU_Time is the total time that the task has run for - it is incremented each time the task runs. The CPU is the percentage of total available CPU that the task is using (fast tasks often have 00 CPU).

Page Table Users

This table displays a list of users currently logged into the system either locally or remotely.The Page table users contains the following columns:

Field Description
Name The user name for a particular user
Last Login Time at which user last logged in
Last Logout Time at which user last logged out
Num connected Number of references, both internal and external.
Default Indicates whether user is the default user for the Citect process. Only one user can be a default user.
Logged In Indicates if user is currently logged in.
Local User Indicates if user is the local user of the current process. Only one user can be the current processes local user.

Page Table Tran

This table shows a list of channels of communication between CitectSCADA components. A tran exists between exactly two separate components. A client tran initiates a connection, a server tran waits for a connection. Client and server in this context bears no relation to the type of component that owns the tran.

There are two modes for viewing the tran table: Standard and Verbose. The Standard mode shows information for every tran in a tabular format. It can be scrolled using the up/down arrow keys, the top row indicates the currently selected tran. Extended information for the selected tran can be viewed by toggling to Verbose mode by pressing the "v" key. Once in Verbose mode, the tran to display can be changed using the Page Up/Page Down keys.

In standard mode the tran table contains the following columns:

Field Description

The name and type of communication channel truncated to 20 characters:

  • Client
    Format: <cluster name><service name>
    Examples: Cluster1Alarm, Cluster1Report, Cluster1Trend
  • Server
    Format: <server name><cluster name>
    Examples: AlarmServer1Cluster1, ReportServer1Cluster1, TrendServer1Cluster1
  • Dedicated (Client and Server)
    Format: @@<cluster name><server name>
    Examples: @@Cluster1.AlarmServer1, @@Cluster1.ReportServer1, @@Cluster1.TrendServer1
  • Platform (Client and Server)
    Format: <server name><cluster name>
    Examples: AlarmServer1Cluster1, IOServerCluster1

Either the node to which the tran is connected, or the status of the connection:

  • <call>
    The client tran is attempting to connect.
  • <listen>
    The server tran is waiting to be connected.
  • <disabled>
    The tran is currently disabled.
  • node name
    The tran has connected and is online. The value is the name of the node/computer to which the tran is connected. This could be the current computer or a different computer depending on the TCP/ IP configuration of the project.

This is either:

  • Client - indicates a client tran. This tran actively attempts to connect to a server tran.
  • Server - indicates a server tran. This tran passively waits for a connection attempt from a client tran.
  • SerRnd - indicates a server-to-server redundant tran. This is the connection between the primary and standby servers when a project is configured for server redundancy.

This is either:

  • Local
    This tran connects two components which exist in the same process. For instance, when CitectSCADA is run in single process mode, every server component runs in the same process as the client. In this case, the connections between these components would be marked as Local.
  • OutPro (Out of Process)
    This tran either has an established connection or is attempting to establish a connection between two components via TCP/IP. The components exist in different processes. They may exist on the same computer or on different computers.
  • OutPrD (Out of Process Dedicated)
    A dedicated connection exists between the client and each server process on a single machine when CitectSCADA is run in multi-process mode. These trans use named pipe connections to verify that a communication path exists between every CitectSCADA component running on one computer regardless of the project's TCP/IP configuration. Dedicated connections do not exist between different computers.
  • Platfo (Platform Tran)
    This tran uses the Platform networking module as the transport layer between components. For v7.0, it is only used to connect to the I/O Server.
    Note: There are client-side Alarm Server platform trans which will show up in the Tran Table. The server-side Alarm Server platform trans were not necessary or implemented for v7.0 so these client-side trans will always remain in a state of Connecting. They can safely be ignored.
  • Remote
    This server tran is waiting for a connection attempt via TCP/IP. Upon connection, this mode changes to OutPro.
Hnd This value represents the handle number in the tran table of the record.

This value indicates the number of times the tran has established a connection. Specifically it counts the number of times the tran receives the MSG_OPEN message. This value has no meaning for local trans for which it remains 0.

If the number is high, it can indicate that your network is dropping and then re-establishing connections. However, it could also mean that the server has been running for a long time and many clients have started and stopped, thereby closing and opening sessions.

Send This value displays the number of messages that have been sent by the tran.
Rec This value displays the number of messages that have been received by the tran.
Wait This value represents the number of times the tran had to wait to get a buffer in order to send a message.

This value indicates the protocol number. Historically, this incorporated the NetBIOS LanA numbers with the TCP/IP protocol stacks. However, NetBIOS support was removed for v7.0 while TCP/IP support was enhanced to include redundant Network Interface Cards (NIC).

The Stack value displays an index (1-based) which indicates on which redundant IP address the server tran is listening or connected. Its value is only used for out-of-process TCP/IP server trans; it has no meaning for every other tran.

Service This column displays the type of the service used by the tran (regardless of the tran mode). The valid services are Alarm, IO, Report and Trend.
State This is the current state of the tran. Valid states are Online, Offline, Connecting (client trans only), Disconnecting, Listening (server trans only) and Disabled.
Login The user login name for remote Tran connection.

Page Table CSAtoPSI.Subs

Displays a list of client tag subscriptions.

See Also