Release Notes 330 (May 2026)

Pro2 Data Collector Overhaul

The Pro2 data collector has been redesigned for better compatibility with Pro2 v6 and standalone database architectures.

Key Connection Changes

The collector now utilizes two distinct logical database connections:

• pro2repl: Contains the classic Pro2 replication tables.
• pro2v6: Contains new Pro2 v6 replication tables.

Configuration Requirements:

v6 Standalone: If your Pro2 database is a standalone instance (remote or local), you must provide the specific database name and connection parameters (-H and -S for remote).

v6 Embedded: If your schema is embedded in the application database, only the -ld prorepl flag is required.

v5 Compatibility: For Pro2 v5 environments, use the single logical name pro2repl and set pro2version "v5" in your configuration.

Note: If you cannot connect to the Pro2 v6 database, the collector will still function in a "degraded" mode (e.g., it may not be able to distinguish between a queue being "enabled" vs. "actually running").

Functional Improvements

Exact Queue Depths: Queue depth now uses the "exact count" method exclusively; estimated counts have been removed.

CDC Support: v6 now supports multiple CDC queues, with depths depending on the active data collector.

Cleanup: The "orphans" column has been removed from the interface.

See Pro2 Monitoring for all the details.

Maintenance & Outage Automation (maintenance.sh|bat)

We have improved the behavior of the maintenance script to ensure heartbeat alerts and agent restarts are more reliable when an outage ends.

Strict vs. Loose Mode: New properties (maintenanceOnMode and maintenanceOffMode) allow you to specify whether the script should "abort" or "continue" if a maintenance state is already active/inactive.

Automatic Restarts: Removing the MAINTENANCE file now triggers an automated restart of dbmonitor and associated agents.

Restart Verification: A new timer (maintenanceRestartDelay) waits for the monitor to successfully restart before notifying the portal that the outage has ended.

Logging: Output has been streamlined to reduce console noise, showing only the final log state upon completion.

See Stopping ProTop for Maintenance for more.

New Metrics & Data Collectors

PICA Buffer Metrics

New metrics have been added to monitor the OpenEdge PICA buffer more effectively:

• picaHWM / picaHWMpct: Track the High Water Mark and current percentage of use.

• picaFilled: Tracks how often the buffer reaches capacity.

• picaCollisions: Monitors access contention for the buffer.

PASOE & Linux Memory

PASOE UI: Reformatted columns in the PASOE collector for better readability in ProTop RT.

Private Dirty Memory (Linux): Now utilizes smaps_rollup when available, significantly increasing the speed of memory usage calculations.

Configuration & Hierarchy Enhancements

TRXMON Migration

TRXMON configuration has been modernized to follow the standard ProTop hierarchy (Site > Server > Group > Resource).

Real-time Updates: Changes to TRXMON properties in etc/protop*.cfg are now recognized instantly without requiring agent restarts.

New Property Names: Several properties have been renamed for consistency (e.g., adding the "trx" prefix).

Exclusion Lists: The etc/exclude.trx file is replaced by the trxUserExcludeList property.

Action Required: A conversion utility is provided to migrate your old trxmon.cfg files:

Linux: bpro -p util/convtrxcfg.p > convtrxcfg.log 2>&1

Windows: bpro -p util\convtrxcfg.p -basekey INI -ininame etc\protop.ini > convtrxcfg.log 2>&1

General Configuration Reminders

Do not edit etc/protop.cfg directly. Always apply your specific overrides in the appropriate hierarchical file (e.g., protop.site.cfg).

Inheritance: New properties and default values are automatically inherited from the base configuration.

See trxmon - Disconnecting Long Running Sessions for more detail.

Bug Fixes & Minor Improvements

Service Telemetry: Improved error messaging for misconfigured log directories and improperly formatted NDJSON lines.

Color Picker: Fixed an issue where the "0" key incorrectly assigned color palettes in ProTop RT.

PTCOMPILE: Added logic to purge r-code at both the start and end of the process when purgeRCode=yes is used.

Report Naming: Fixed an issue where "dbparams" and "servers" reports failed to use the database "Friendly Name" in filenames.