I apologise. I read that remark at the end of a very tiring day, much of it spent cleaning my PCs of the Microsoft virus that's going to download 3Gb of Windoze 10 whether you want it or not. Although my response was intemperate and, as Breck points out not befitting the forum, at least he understands my point.
There is no circumstance in which you'd want any software to automatically commit changes to the database. Being of the old, tired and very grumpy persuasion I can do a whole bunch of SQL and just close the dbisql session, not pausing to think about any updates I might have tried. Ask any PowerBuilder instructor (if you can find one) and amongst the first thing you talk about when discussing database connections is to set AutoCommit=FALSE. The default for dbisql to autocommit is, in my view at least, criminal.
The plain fact is that DBISQL isn't very good, and I generally use another tool. However, certain things, especially the OUTPUT command, mean that you have to use it.
So the question remains unanswered. How can I get rid of this stupid, and this time I mean it, message?
Paul