The iSeries is managed elsewhere and they claim there is no problem because it works using DB2 connect and Operations Navigator. I had always thought these products used APPC not ODBC. Is this correct?
- DB2 connect indeed uses a different approach then ODBC
- Navigator works with JDBC (and not ODBC)
- Sometimes it is recommended to upgrade the ODBCdriver when changes occur on the iSeries. (I assume you use ODBC driver from iSeries access).
- Try to "play" with dates format (in the ODBC configuration use tab server -> advanced)
Dig Deeper on Physical connections to iSeries
Related Q&A from Shahar Mor
Use work station customize object or printer type in iSeries Access to print the output of an RPG file from the AS/400 to an HP printer. Continue Reading
On the AS/400 library, source files are multi-member. View source files using GET QCLSRC.membername or MGET QRPGSRC.* Continue Reading
Connecting the iSeries in AS/400, issue STRHOSTSVR *ALL. Make sure the as-signon port is in listen state and check the firewall settings. Continue Reading