Release Notes 330.3 (June 2026)

Some Pro2 configurations write a single control row that lists multiple thread numbers (e.g. 6, 61, 62, 63) instead of one row per thread. ProTop was reading those rows as a single integer — OpenEdge silently drops the commas during conversion, so 1,2,3,4,5 became 12345, and longer lists exceeded the INTEGER range entirely. That runtime error aborted the entire collection cycle, wiping the Pro2 Queues screen and portal data completely.

330.3 detects these split thread rows and skips them. Each thread they reference already has its own individual row, so nothing is lost.