Define a System DSN to your iSeries:
in the General tab enter a name for it under "Data source name" and under "System" enter the server's IP address, in the Servers tab set the "SQL default library" to "web2py" and under the Packages tab set "Package library" also to "web2py", use the defaults for everything else.
On the iSeries run the following commands to create the WEB2PY library where your tables will be stored and to enable automatic journaling on them (Note: the values in the CRTDTAARA command are exactly 10 chars each):
CRTLIB WEB2PY CRTDTAARA DTAARA(WEB2PY/QDFTJRN) TYPE(*CHAR) LEN(100) VALUE('WEB2PY QDFTJRN *FILE ') CRTJRNRCV JRNRCV(WEB2PY/QDFTJRNRCV) CRTJRN JRN(WEB2PY/QDFTJRN) JRNRCV(WEB2PY/QDFTJRNRCV)
Now authorize your ODBC user (in this case TEST) to the journal:
GRTOBJAUT OBJ(WEB2PY/QDFTJRN) OBJTYPE(*JRN) USER(TEST) AUT(*ALL)
In your model use:
Please read the following extract from a paper written by Ken Milligan and available from:
Distinguishing the three DB2 family members
With the addition of DB2 for i5/OS to the DB2 UDB family, there are now three members in the DB2 product line, as follows:
The most common misconception about DB2 branding is this: It infers that IBM has implemented a single, common code base on all of the supported platforms and operating systems. On the contrary, each DB2 brand member's code version is unique and developed by different IBM laboratories, but a tremendous amount of technology sharing takes place at various levels across IBM and the DB2 brand. The different code bases allow IBM to exploit the hardware, microcode, and operating system of each of the respective platforms. Thus, at the lowest level, each DB2 offering is tightly integrated into, and exploitive of, its operating environment. This is good news, as you can imagine, and as you will come to understand more clearly as you continue reading.
Another misconception is that the DB2 9.5 product is the master version of DB2 – meaning that the SQL functionality it contains is a superset of all the functionality in the DB2 product family. Much of that confusion is caused by the fact that the version numbers used by DB2 for i5/OS version numbers are completely independent from the version numbers used by the other two DB2 products. The DB2 for i5/OS version number matches the version of the i5/OS operating system with which it ships. The reality is that each DB2 product has SQL functionality that it delivered first to the market and that is unique to that product. For example, DB2 for i5/OS was the first DB2 product to support SQL stored procedure and is the only product that supports encoded vector indexes.