Analyze update manager signups and queues with pilistupd

• Use the pilistupd utility to monitor PI Update Manager. Run pilistupd from the ..\PI\adm directory. Data Archive must be running to use pilistupd.

  Note: Data Archive exposes PI Update Manager counters as Windows performance counters. You can view these counters with Windows Performance Monitor, and you can store these counters as PI points using the PI Performance Monitor Interface.

At the PI\adm directory, type:

pilistupd -ss

You will see a summary of the current state of update signups:

• Producer

  This is the source of update notifications. For example: PI Snapshot Subsystem produces snapshot events; PI Base Subsystem produces PI point database and Module Database changes; PI Archive Subsystem produces archive changes; and PI Batch Subsystem produces Batch Database changes.

• Consumer

  Application currently signed up as a consumer. For example, a PI ProcessBook display is a consumer.

• Qual

  The qualifier. If the producer is snapshots or archive, the qualifier contains a point ID. If the producer is PIUnitBatchOnUnitUpdates, the qualifier contains a unit batch storage point ID. Not used for other producers.

• Flag

  If the producer is archive, contains archive event modes. Not used for other producers.

• Pending

  Number of events available for the consumer to retrieve. The value goes up and down as events come in and the consumer pulls them out. Values that increase continuously might indicate that the consumer is not working properly or disconnected.

  Note: The Pending column display is not accurate above 65,536 events.