×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
A legacy RPG seems to be doing "funny" stuff. We *think* it creates a
duplicate-keyed record, then deletes the previous record, resulting in SQL
replication errors. Very hard to catch.
The thought is we could go to the journal used by replication and find the
sequence of events. Start replication and rush to observe the journal when
we get an error.
Not very easy in DSPJRN which presents negligible navigation capabilities.
Anyone have any tips on hunting this down?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
