All, I am just introducing myself to the list. My name is Andy Abate and I have been a professional developer for over 30 years. I'm deep into parsing and systems development with Java, C/C++, Assembly and a ton of scripting languages.
At the moment, I am working on the DRDA portion of Derby to make it compatible with LUW. I have pretty much everything working except for the validation responses for when a remote stored procedure is being defined. The LUW instance is sending a request for a bogus entry in the syscat.routines table. It is looking for something named AMP.TESTFEDERTAION which of course won't exist. Or at least wouldn't exist if the table syscat.routines did. I am defining the Derby database as a DB2/LUW server so it will use the DRDA driver. I'm not really sure how else to do it because I have a specific set of database types from which to choose on the LUW server. Before I do something totally ugly here, I was wondering if anyone had any ideas on how to deal with this. Or at least provide the right answer to the calling LUW. What Derby is sending back right now is TABLE/VIEW doesn't exist. I can dummy the response, but that would mean interrogating all the requests. Not something I really want to do unless I absolutely have to.
