Ok, here’s something that’s frustrating me slightly:
For various reasons, we’re using DB2 at work – Stand-alone for testing, and mainframe for UAT/Production. I’m wondering if anyone with solid DB2 experience can tell me why my SQL clients won’t auto-complete when looking at the various mainframe DB2 databases? Is it because I’ve got old drivers? Or is it just because the mainframe is an older version of DB2 than the stand-alone ones we’re running (SA is 9.1, MF is 8.2)? Or is it just a quirk of the mainframe?
Other thing is that, when I bring my laptop out of sleep mode, the connections have all typically been dropped, which is fine. What is not fine, however, is that my SQL Client (SQuirrel SQL, 3.0.2) doesn’t realise this and attemps to run the SQL anyway. Unfortunately, I can’t tell it to cancel execution due to JDBC Drivers not supporting it. Again, is this a DB2 quirk or simply due to the fact that I have old drivers for DB2?
Currently writing this post as I wait for SQuirrel to time out because I forgot to reconnect before running the SQL…
Tags: db2, jdbc, mainframe, quirks, standalone