On August 6, 2004 6:54 am, [EMAIL PROTECTED] wrote: > [ Not really DBI related, but Tim suggested I post here ] > > We're starting to write our own administration functions for DB2, and > are currently developing a perl module that provides access (through > XS code) to the DB2 administrative API. This allows us to perform > tasks like getting database snapshots, decoding binary snapshot and > event data, getting/setting configuration options, etc - without going > through the "db2" command line processor. We've succesfully used this > to write DB2 monitoring tools. > > In a similar vein, generating DB2 catalog files (which are binary and > differ per platform / DB2 release) is a pain using the DB2 tools; > we've reverse-engineerd the files and written (pure perl) modules so > we can generate them directly from perl. > > We're considering open-sourcing these modules, but before starting the > internal argument (lawyers get involved) I'd like to find out whether > anyone in the perl / DBI community would be interested in using such > an API. If you are, please let me know and prepared to be patient > while we sort things out internally.
I've been after the author of DBD::DB2 to provide much of this as "private" functions in the driver itself ... I wonder if you could bypass some (probably not all) of the lawyering by donating it to the DBD::DB2 author in the form of patches. Since DBD::DB2 is written by IBM itself, if IBM released it, that would take care of some of the concerns, wouldn't it?
