SQL Server DBA working with DB2, Part 2. iSeries Navigator

  
Because we’re SQL Server folks, sometimes we have to fetch data from all sorts of places – we’re the least expensive tool in town with the most bang for the buck. And, in the process might have to use some not-so-familiar tools to get the job done…such as iSeries Navigator. To go along with a previous blog about random things that I noticed when working with DB2, here is a list that I came up with for using the query tool specifically. I haven’t used iSeries Navigator since I was a Transamerica Life Long-Term Care Division back in 2003, so it’s been awhile for me. And I certainly haven’t missed it I might add.

I hope that these two blog postings help someone somewhere down the road. Otherwise, if you get a chuckle or two out of this, I’m good.

• Use CTRL + Y to run queries. I have no idea what the Einstein who threw in CTRL + T and CTRL + ALL had in mind
• However, the problem with using CTRL + Y…this is the SQL command to “move forward” after using CTRL + Z undo in many Windows IDEs, and we’re all getting used to using it. Well unfortunately in this tool it’s already assigned to run a query and it looks like there is no replacement for redo. When I try a redo, I end up running a script on my query screen wherever the cursor happens to be located at the time. Brilliant!
• Separate batches with a semicolon. If the cursor is anywhere on a query and before or between semicolons, iSeries will run that DML statement.
• Watch capitalization in this thing when using wildcards and DB2.
• If you are looking for extra tabs or a Window menu option to view two script files at the same time, forget it. They ain’t one. You get one and only one window. WTF?
• The results tabs below the query window are stacked on top of each other. Strange feel if you ask me.
• The messages and errors that are output to the query pane don’t go away. What the hell do I need to reference the fact that I misspelled SELECT two hours ago? Very annoying.
• I never figured out how to change the default library. Sure, there’s a way, but I didn’t spend time trying to find it. I suggest that you do, so that you don’t have to type it every time you reference a table. Please email me when you have it.
• If you place your cursor in the middle of DML, the statement gets highlighted when you run CTL + Y. Fine enough. However if you have a statement below it, separated by a semicolon of course, it highlights that one upon completion of the query. WTH. Don’t confuse me on which query I just ran for crying out loud! I feel like i’m playing hopscotch from one query to the next down the page with this behavior. Leave the cursor where it is!!!
• It’s funny how the screen jumps when you use CTL + F to search a file. It flickers like it’s about to jump off the screen! I actually opened perfmon to see if it registered CPU usage, and it did. OMG!
• Love the syntax highlighting. (None, sorry). No color coded syntax. Suckage.
• Love the Intellisense. (You know that i’m kidding you here).
• F1 is not how you get help to open. Need to go to the menu. And no shortcut keys either.
• The open file button and the save file button look the same, save an arrow pointing to save. Nice.
• I don’t know how you get an execution plan, but I tried a button that looked like the one in SQL Server. Bad idea. I’m still on the hourglass now as I type this.
• CTRL + F – when you use it, and then reuse it, it doesn’t highlight the text that you search on. So you have to tab on the text or mouse over before you can write.
• I must be missing this, but HTH do you get the query window up? I always go down to the database or schema and then right click. Duh.

-----------------------------

What’s more difficult - Interfacing these tools or working with the folks that administer them? LOL