In order to connect to an iSeries server, the DB2 Development Center requires DB2 Connect for a connection that uses Distributed Relational Database Architecture (DRDA). Because the DB2 Development Center is a Java application, it also requires the iSeries Toolbox for Java JDBC driver for the JDBC connection. This driver can be downloaded at http://www.ibm.com/servers/eserver/iseries/toolbox/.
DB2 Enterprise Server Edition (ESE) for LUW comes packaged with DB2 Connect functionality, although if you are using the DB2 Application Development Client, then you will need DB2 Connect for a DRDA connection. (The CD packaged with this book is a trial server version of DB2 for LUW.)
Assuming you have access to the Development Center and connectivity through DB2 Connect, you will be able to use this environment for many development tasks available to DB2 for Linux, UNIX, and Windows, but not all. Specifically, the tasks that cannot be performed are debugging stored procedures and creating, building, and deploying user-defined functions (UDFs).
To debug stored procedures, you can use the IBM Toolbox for Java iSeries System Debugger, which is easily launched from the iSeries Navigator SQL Script window. A document showing how to accomplish this can be found at http://www.ibm.com/servers/enable/site/education/abstracts/sqldebug_abs.html.
The option to debug stored procedures natively always exists. By using the SET OPTION DBGVIEW=*SOURCE statement in the procedure declaration, the native debugger (STRDBG) or the GUI debugger (found under the Run pull-down menu on the Run SQL Scripts window) can be used.
For further reference on using the Development Center, a document showing the use of (a slightly older version) of the Development Center with iSeries can be found at http://www.ibm.com/servers/enable/site/education/astracts/db2dev_abs.html.
For developing UDFs', other interfacessuch as the Run SQL Scripts window of the iSeries Navigatorcan be used, as well as native iSeries interfaces (STRSQL, RUNSQLSTM).