Yes it's a mouthful. and right now it tastes pretty bad..
Hi There.. First post and Maybe I'm just venting .. But I have couple of questions that hopefully someone can answer
Powerhouse (PH to save typing) was running on an HP3000.. for those that don't know PH is a 4GL..
I'm working for a client that has chosen this path and it's not working so well..
My problems;
PH controls the ODBC connection and I'm limited to a few things I can pass to the connection via variable basically user ID, password and I can select what ODBC connection to open..
It appears the the iSeries connector or DB2 is prefixing the table name with the schema name (ALA schema.table) so I can't select a like table from 2 different schemas using a different ODBC connection
Then we hit redefines; in the PH dictionary I can have an DB element redefined for type, size or into multiple new elements .. But since ODBC is essentially replacing my dictionary and DB2 doesn't do redefines.. I'm hosed again..
So I have a couple questions
Anyone have ideas about either of my issues above? If we can keep the solution stack I'm sure the client would be happier!
Then about inter-connectivity between DB2 on iSeries and on Windows.. Can I create a table in DB2 on windows which a actually a virtual table, the data would reside in DB2 on an iSeries?
If I can do this I'm hoping I can keep the dictionary functionality in PH and get rid of my ODBC limitations..
thanks in advance.
Hi There.. First post and Maybe I'm just venting .. But I have couple of questions that hopefully someone can answer
Powerhouse (PH to save typing) was running on an HP3000.. for those that don't know PH is a 4GL..
I'm working for a client that has chosen this path and it's not working so well..
My problems;
PH controls the ODBC connection and I'm limited to a few things I can pass to the connection via variable basically user ID, password and I can select what ODBC connection to open..
It appears the the iSeries connector or DB2 is prefixing the table name with the schema name (ALA schema.table) so I can't select a like table from 2 different schemas using a different ODBC connection
Then we hit redefines; in the PH dictionary I can have an DB element redefined for type, size or into multiple new elements .. But since ODBC is essentially replacing my dictionary and DB2 doesn't do redefines.. I'm hosed again..
So I have a couple questions
Anyone have ideas about either of my issues above? If we can keep the solution stack I'm sure the client would be happier!
Then about inter-connectivity between DB2 on iSeries and on Windows.. Can I create a table in DB2 on windows which a actually a virtual table, the data would reside in DB2 on an iSeries?
If I can do this I'm hoping I can keep the dictionary functionality in PH and get rid of my ODBC limitations..
thanks in advance.