We’re hoping you are all enjoying your Canada Day or Independence Day celebrations this week. Or, if you're not located in Canada or the United States, we'd still like to wish you a happy July.
Last week we reported on our early experiences with V9 of RDi. Since then, we've had some comments and emails that clarify some of the issues that we experienced. IBM's Edmund Reinhardt also made a number of points regarding these experiences. It was nice to find out that the improvements in speed weren't just a figment of our imaginations. Thanks Edmund - you and the whole RDi team do a great job of keeping in touch with your users.
Also regarding V9 RDi: we said last week that "Adding Data Studio to our workbench seems to have caused the regular help system to fail.” It seems that was not the cause of the problem, but instead the failure might be related to IBM's help system for RDi V9 being offline. When we initially loaded V9, we apparently did not get a complete download of the help info. We hoped that using the update would remedy that, but so far we're still getting connection failures on the update. Hopefully IBM will resolve this issue soon.
With regards to Data Studio (DS), we commented on the problems we had with IBM's Web page, "Data Studio V4.1 features: by data server and component." We haven't really had any updates on that, but we've had help from Paul Bailey via the WDSC-L mailing list at Midrange.com, who had set up DS to use the "IBM Data Server Driver for JDBC and SQLJ (JDBC 4.0)" option, and found that it was clearly one of the drivers that IBM were referencing in the "X1" category. So, now we can try out some of those new functions – we'll report back on what we find. We're certain that we had tried this driver in the past and received a "not found" type of error, but following Paul's suggestion, we checked it out. Sure enough, it worked. Of course, the remaining problem is that there is no provision for using the library list, as this is a generic IBM driver. Luckily, the connection filtering in DS is good enough to largely alleviate this issue.
Speaking of library lists, reader Art Blose, commenting on the blog and in an email, passed on some information that we had forgotten concerning DS default JT400 driver. You can specify a list of library names on the connection string, so it is possible to effectively specify the library list you want without having to specify filtering criteria. There are, in fact, a number of other options you can also specify on the connection string; for a full list, check out this document.
To sum up the current situation with Data Studio: it seems that you can either have a library list (using the default JT400 driver) and miss a number of the new features in DS, or you can miss out on the library list and have all of the features available. We suspect it’s the latter, but time will eventually tell. Either way, we do like DS, and it is certainly a lot snappier to use than Navigator.