How do I capture SQL warnings issued by DB2?

I'm using DbVisualizer 5.0.0.3 (licensed) against a DB2 database using a JDBC/ODBC driver. I'm running a create table statement which runs fine and creates the table. When a colleague runs the same query from the official DB2 query tools they are seeing a warning issued because the USER system value is a VARCHAR(128). CREATE TABLE MYSCHEMA.MYTABLE ( some_date DATE NOT NULL, -- audit fields last_op_ind CHAR(1) NOT NULL WITH DEFAULT 'I' constraint CC_RFVE_1 CHECK (LAST_OP_IND IN ('I','U','D')), last_op_by CHAR(8) NOT NULL WITH DEFAULT USER, last_op_date_time TIMESTAMP NOT NULL WITH DEFAULT CURRENT TIMESTAMP ); By convention, our environment always inserts the current USER into the last_op_by field. I'm making this change so that DB2 handles that by default. There was some confusion as DBVis didn't report the warning, or at least, I didn't see the warning. We know that errors are clearly reported but what about warnings on successful statements? Is this just a driver issue or do I need to make some setting changes to pick these up?

When running the create statement I should see what you see but my log entry just shows me: 09:20:29 [CREATE - 0 row(s), 1.828 secs] Command processed but no rows were affected ... 1 statement(s) executed, 0 row(s) affected, exec/fetch time: 1.828/0.000 sec [0 successful, 1 warnings, 0 errors] It doesn't include the warning itself. I have the "retrieveMessagesFromServerOnGetMessage" flag set to "true". Is there anything else I need to set? I'd expect it to run fine on insert, that's okay. I've attached a screenshot showing DBVis straight after running the sql.

> Mark, > > It may be driver dependent whether the warning is > handled properly or not. I've just set my system up to use the DB2 jdbc driver and I am getting the warning messages back, so yes, this is driver-dependent behaviour. Thanks for your efforts.