× 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.



Hello John,

Am 16.07.2021 um 09:39 schrieb John Yeung <gallium.arsenide@xxxxxxxxx>:

Vern suggested calling IBM.


Given the fact that meanwhile, 7.2 is out of service, and the 8203 running it is'n exactly new, there's no point in trying that.

Patrik, did you ever find out anything more about this? I am fascinated too, because it happens on our 7.3 system.

Nope. I was resolving to add a "if there was an error, try DELETE FROM" after all truncates. Most annoyingly, truncating an empty table is also considered as an error condition. Note that I'm using ODBC from Linux to access the databases, and the (to me) only reliable way to tell if there was an error is to not look at affected row count, or return value, but see if the Error-method from Perl-DBI returns some text.

Given the tiny table sizes in question (rarely more than a few hundred records), that's okay. I'm not happy with it because it's a dirty workaround.

:wq! PoC


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.