I am facing a unique problem. Could you suggest some work around. I am using OJB with STRUTS in a project. I am using the ODMG APIs. The problem is that the database is on a Mainframe (DB2). Unfortunately, there is a restriction on the length of 'KEY' field that we can specify on a Mainframe (DB2) that limits it to 255 characters. Now in the OJB_LOCKENTRY table we have a composite primary key of OID_(250) and TXID_(50) combining to 300. So the DDL's are failing due to some implicit restriction on key field on the Mainframe that's not suppose to exceed 255 in length and I am not able to use OJB after successfully testing on NT version of DB2, and Linux version of DB2, where there were no problems. However there is little choice left with me to make a choice on the platform of DB2 at this stage in the project. I would like to know if we really need OID_ to be of 250 length and TXID_(50) - (I mean is it a padded field with empty spaces...I can reduce the pad). What if I drop one of the keys? Will there be an impact? I thought to get a quick answer from you before I enter into a 'surgery' mode on the OJB source code!! Sincerely, Vatatmaja -- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
