Hi Jeff, Unfortunately, right now, we don't formally support DB/2 for z/OS (or for iSeries), as we do not have access to actual database instances for integration testing, which is needed to provide warranties and support for such an integration.
Nonetheless, I'm sure we can help you get this integration to work. Among your listed options, I suspect that SYSCAT and SYSIBM aren't similar enough to be used as substitutes for one another. So I think that option 1) can be ruled out. Option 2) would certainly work, but it seems a bit tedious. Option 3) would be interesting in general. I think that, if you open source your own version of SYSCAT views based on SYSIBM queries, this would be rather useful for a lot of people out there. We could help you promote such a project, if you're interested. There are more options: 4. You can use the org.jooq.util.jdbc.JDBCDatabase from jOOQ-meta, which loads schemas, tables, sequences, and primary keys via the JDBC DatabaseMetaData API. 5. You can use jOOQ's org.jooq.util.xml.XMLDatabase and generate your database schema based on our XML version of the SQL standard INFORMATION_SCHEMA (http://www.jooq.org/xsd/jooq-meta-3.5.4.xsd) 6. You can implement your own org.jooq.util.Database in jOOQ-meta, and supply the necessary information to the code generator. We would love to help you integrate with z/OS - our favourite option would be #6. We could maintain such an implementation for you, and add official support for DB2 for z/OS to the jOOQ Enterprise Edition. I'm curious to hear what option seems to be the most reasonable to you, and whether you're interested in working on such an intergration with us. Looking forward to hearing from you again, Lukas - from Data Geekery 2015-04-21 14:23 GMT+02:00 Jeff Keene <[email protected]>: > Hi, > > > > We have a need to generate code bindings from DB/2 on z/OS. So far we've > been doing it by copying the schema from the z/OS database into a DB/2 LUW, > then running the code generator against the LUW. We've had to do this > because the jooq is coded to use the SYSCAT catalog, present on LUW but not > on z/OS. > > > > I'm looking for alternatives to this process. Came up with a few ideas, > but I was wondering if anyone else has solved this problem or has some > different recommendations? > > > > 1. Find a way within jooq to map the SYSCAT schema over to SYSIBM. I've > done this just fine for regular data tables, but the catalog schema > remapping is not something I see how to do. > 2. Automate the schema synchronization with a tool like liquibase, and > keep generating from an LUW DB/2 > 3. Create views onto SYSIBM named SYSCAT, sufficient to meet the needs > of the jooq code generator. I don't know quite how many views that > would be, but looking at o.j.u.d.syscat.Tables it seems to start at > thirteen. > > > > Any thoughts or guidance would be appreciated. > > > > Thanks, > > Jeff > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
