Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
bwhicks at aep.com wrote: > So the function works as expected. The return value just seems to get lost > before the next query happens (to insert something like taglog data). > I can only guess something getting lost in the ODBC driver... although I've never heard of that happening before. I don't think db2 has an accessible native API (at least not according to the online ibm documentation) so bypassing ODBC probably isn't an option. Best thing to do is to get it logged as a bug (it probably already is if arthur is reading this) and if we can reproduce it try to find a workaround. Just a thought - can you run a command that causes and audit log with full tracing? (cvs -ttt with server tracing enabled). There's only one thing I can think of that could go wrong and that is to do with parsing the ODBC recordset, where we only bother with types that are expected to be returned - if it returns one we don't know about you'll see a line "Bogus value return for field xxx" appear. Tony