SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

The following are the Publish/Subscribe counters:
KB54765Publish/Subscribe bytes..
0Keys In Use......512Max Subscribers..........
0Resyncs..........0Subscribers Active.......
512Maximum Tables...........
0Tables Active............
• Publish/Subscribe bytes denote the number of kilo bytes allocated for publish/subscribe events.
• Max Subscribers denote the maximum number of subscribers allowed per disk volume (512).
• Subscribers Active denote the number of active subscribers.
• Maximum Tables denote the maximum number of tables allowed per disk volume for
publish/subscribe operations (512).
• Tables Active denote the number of tables on the disk with at least one active subscriber.
• Keys In Use – NonStop Data Access Manager (DAM) adds an entry into a list if the position
of a streaming cursor in the table logically succeeds the position of the newly published row.
Keys in Use denote the number of keys in this list and can be either a primary key, clustering
key, or a system generated key.
• Resyncs is not used currently. 0 is always displayed against this field.
DP2 Savepoint counters
The following are the DP2 Savepoint counters:
16384KBMax..............KB1024Savepoint Buffer
Data....
- 16KB Blocks - - - - - - - - - - - Failures - - - - - - - -
12SavePoint Limit..16Max......................
0Buffer Full......0In Use...................
0Memory Pressure
0No Memory........
• Savepoint Buffer Data denotes the current size of buffer allocated to hold savepoint data. The
value is in KB. The minimum value is 1024KB.
• Max denotes the maximum savepoint buffer size per volume. The value is denoted in KB.
• Max denotes the maximum number of blocks that can be used to store savepoint data.
• In Use denotes the current number of blocks holding savepoint data.
Failures
• SavePoint Limit denotes the number of failures caused because the savepoint limit was reached.
The savepoint buffer limit for a statement is 1/64th the Max Savepoint buffer size per volume.
• Buffer Full denotes the number of failures caused because the buffer limit was reached. The
buffer limit is considered reached if the total amount of savepoint buffer data for all the
statements on a volume exceeds the Max savepoint buffer size.
Managing SQL/MX Buffer Space 301