To prevent unnecessary network traffic and improve response time, notifications of certain schema changes are automatically sent to remote clients.

You can use startup parameters, the PROMON utility, and VSTs to control the method and frequency of notification delivery.

To check the current status of notifications, check the columns Complete Seq and In Progress Seq on the User Notification Processes screen in the PROMON Processes/Clients Status display.

For more information, see Processes/Clients in OpenEdge Data Management: Database Administration.

The _Connect VST fields associated with these columns are _Connect-NotifySeq and _Connect-NotifySeqChecked.

For more information, see Database connection (_Connect) in OpenEdge Data Management: Database Administration.

Startup parameters that control notifications are:

  • Database Notification Operations (-dbnotifyops) – sets the maximum number of concurrent notifications.
  • Database Notification Time (-dbnotifytime) – controls how often a 12.2 client polls for notifications. If set, notifications are sent directly to clients, and clients incur no network traffic checking for them.
  • Database Client Notification ( -usernotifytime) – if set to non-zero value, specifies how often a self-service client polls the database to see if schema changes are in progress, or how often a remote client asks the server for notifications. For less frequent polling, specify a large number. This parameter generally affects only clients prior to version 12.2, but also affects 12.2 clients if you set -dbnotifytime to 0.

You can change the settings of these parameters while the database is online.

For more information, see Change database parameters while the database is running.