Actually, I've been working with other users on this for a while as noted in the comments on this feature request:


You can get the latest snapshot and give it a try if you would like to report back on the request linked above.

Also, I believe we've narrowed the identification to a value of simply "DB2" for database product name which uniquely identifies z/OS.  Other platforms seem to have other values for this field.


On Wed, Nov 7, 2012 at 1:12 PM, Nubio Revoredo <nubio@nubio.com.br> wrote:
Robert Manning <robert.m.manning <at> gmail.com> writes:

> Hi Cris,Can you (or anyone else paying attention to this thread) when you
connect to DB2 on Z/OS with SQuirreL, look at the "Metadata" tab in the object
tab (click on the root node of
> the object tree) and tell me the value of the property named
> "getDatabaseProductName".  I need this in order to branch the logic that
chooses which SQL statements to use when connected to DB2-UDB, DB2-OS400 or
> On Sat, Sep 8, 2012 at 3:55 PM, Cristiano Guadagnino <criguada <at> gmail.com>
> Robert,I sent the correct queries for DB2 Z/OS a couple years ago. They are
stilll available on sourceforge: in the "Feature Requests" tracker, ID 3134781.
I could not attach a file so I wrote the queries as a comment.Hope you can make
something out of it. I am able and willing to test.ByeCris
> On Sat, Sep 8, 2012 at 12:54 PM, Robert Manning <robert.m.manning <at>
gmail.com> wrote:Since none of us SQuirreL developers have access to this
platform, its hard to test.  However, if you could look at the "Metadata" tab in
the object tab (click on the root node of the object tree) and tell us the value
of the property named "getDatabaseProductName", we may be able to update the
plugin to use the tables you have suggested.Rob
> On Fri, Sep 7, 2012 at 3:14 PM, Tony (Antonious) Anderson <aanderson <at>
bcbsal.org> wrote:
> When looking through the object tree for Triggers and Indexes, Squirrel
attempts to run queries against SYSCAT.TRIGGERS and SYSCAT.INDEXES.  These are
not valid catalog objects in mainframe DB2.  This causes -204, -514, and -516 
sql errors in the tool.  How would one go about getting Squirrel updated to use
> Thanks.
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Squirrel-sql-users mailing list
> Squirrel-sql-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users

Hi Rob!

I work in the largest public bank in Latin America and we started using Squirrel
SQL Client in order to access DB2 in z/OS from the developers workstations.

The value of the "getDatabaseProductName" property is "DB2" and the value of the
"getDatabaseMajorVersion" is "9".

I think the property "getDatabaseProductVersion" may be more useful. Itīs value
when connected to an z/OS is "DSN09010". It appears to be sufficiently specific.

We want Squirrel SQL Client to be fully funcional with DB2 in z/OS and want to
collaborate in this goal by testing it on this platform.



LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
Squirrel-sql-users mailing list