PMDF System Manager's Guide


Previous Next Contents Index


COUNTERS/SHOW

Display the contents of the cluster-wide database of counters.

Syntax

COUNTERS/SHOW

Command Qualifiers Defaults
/ASSOCIATIONS /ASSOCIATIONS
/CHANNELS /CHANNELS
/HEADERS /HEADERS
/OUTPUT=file-spec None
/TODAY /TODAY

restrictions

Normally WORLD privilege is all that is required. But if the cluster-wide, on-disk database must be created, then privileges sufficient to create a file in the directory are required; or if the node-specific, in-memory section must be created, then SYSGBL and PRMGBL privileges are required.

Description

The contents of the cluster-wide association and channel counters database may be displayed with the PMDF COUNTERS/SHOW command. A PMDF COUNTER/SYNCHRONIZE command is implicitly performed by this command; the database contents are synchronized with the in-memory section(s) before being displayed.

Note that as part of the implicit PMDFCOUNTERS/SYNCHRONIZE operation, if the cluster-wide, on-disk database does not already exist, the PMDF COUNTERS/SHOW command will create it. And if the node-specific, in-memory cache of counters does not already exist, the PMDF COUNTERS/SHOW command will create it too.


Command Qualifiers

/ASSOCIATIONS (default)

/NOASSOCIATIONS

This qualifier specifies whether to show the in-memory cache of association counters.

/CHANNELS (default)

/NOCHANNELS

This qualifier specifies whether to show the in-memory cache of channel counters.

/HEADERS (default)

/NOHEADERS

Controls whether or not a header line describing each column in the table of counters is output.

/OUTPUT=file-spec

Direct the output to the specified file. By default the output appears on your display.

/TODAY (default)

/NOTODAY

This qualifier specifies whether to show PMDF's count for the number of messages processed this day. Note that as discussed in Section 33.4.1, PMDF counters are intentionally designed to be lightweight and as such by design, the value shown becomes increasingly likely to be an undercount as message volume increases. So high volume sites (sites with an unlimited volume PMDF license) in particular should not place too much credence in the reported number.

EXAMPLES

To display the counters for all channels and associations, issue the command


$ PMDF COUNTERS/SHOW
4263 messages processed so far today 
30000 messages per day are permitted by your license 
 
Channel                     Messages  Recipients      Blocks 
------------------------  ----------  ----------  ---------- 
l 
    Received                    3863        3881       25786 
    Stored                        89          89         460 
    Delivered                   3876        3894       26018 (3859 first time) 
    Submitted                     99         114        1611 
    Attempted                     17          17          25 
    Rejected                       0           0           0 
    Failed                         1           1           6 
 
    Queue time/count        29794837/3877 = 7.68502E3 
    Queue first time/count  18904343/3860 = 4.8975E3 
 
tcp_local 
    Received                     208         217        4153 
    Stored                         3           3           9 
    Delivered                    200         212        2461 (197 first time) 
    Submitted                   4053        4078       25919 
    Attempted                      7           7           0 
    Rejected                      46          68           0 
    Failed                        14          14        1695 
 
    Queue time/count        1106266/211 = 5.24297E3 
    Queue first time/count  455897/208 = 2.19181E3 
 
    Current In Assocs            127 
    Total In Assocs             1056 
    Total Out Assocs             132 
    Rejected Out Assocs           11 
    Failed Out Assocs              1 
 
Channel      Timestamp    Association 
------------ ------------ ------------------------------------------------- 
tcp_local    01-Feb 00:27 TCP|192.160.253.70|25|192.160.253.66|3465 
tcp_local    25-Jan 00:31 TCP|192.160.253.70|5|192.160.253.66|3496 
tcp_local    26-Jan 14:50 TCP|192.160.253.70|25|192.160.253.66|2086 
tcp_local    05-Feb 12:23 TCP|192.160.253.70|25|192.160.253.66|3593 
tcp_local    01-Feb 00:34 TCP|192.160.253.70|25|192.160.253.66|3581 
 
...
$ 


Previous Next Contents Index