On Mon, Oct 19, 2015 at 12:33 PM Charles Wilt <charles.wilt@xxxxxxxxx>

Personally, I'd just you iNav to right click on an object and Generate SQL.

IBM provides the API so that other tools, for instance my CMS system, has
access. But I don't see any advantage to manually calling the API vs.
having a UI of some sort call it.

I don't have client access installed, and I'd rather work with SQL
workbench at least at the moment.

Yes, I agree, the API is not good for adhoc calling. I'd like to write a
wrapepr around it that calls this API, checks the system catalog views to
ensure the object and source member exists and return any joblog messages
get created. This way I can write CREATE TABLE statements in my SQL exditor
of choice, and them "commit them" to the source member when I am ready.

So, that least me to a more generic version of my last question. If a SQL
statement fails, whats the best way to associate that with particular rows
in the joblob? Capturing timestamps before the message, or can i get the
rowid somehow?

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2021 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.