IBM i Runtime Environment

  • ftp is required when doing a remote GUI or remote batch installation.

  • IBM TCP/IP must be installed and running.

  • The installation directory must be created prior to the installation and must be created in the IBM i UNIX interface strqsh or iSeries Navigator under the integrated file system “Root” structure.

  • The file system where Data Integration is installed must have at least 50 megabytes of disk space.

  • Java SE must be installed on both the installer and recipient hosts.

Note: Although the user is required to obtain a JDBC driver for other platforms, the one exception is IBM i hosts where Data Integration installs the JDBC driver.
  • Ensure that the correct Greenwich Mean Time (GMT) or Coordinated Universal Time (UTC) offset is defined on all machines in your Data Integration system. To automatically adjust for time zone differences, Data Integration relies on a time zone setting that the operating system on each host machine keeps. This setting specifies the difference between the machine’s local time and the current time in Greenwich, England.

You must also reset the offset if you have seasonal changes in local time (for example, when Standard Time changes to Daylight Saving Time in the USA).

For an IBM i machine, the timezone offset is kept in the system value, QUTCOFFSET. You can use the DSPSYSVAL and CHGSYSVAL commands to display and change the value. For example:

DSPSYSVAL QUTCOFFSET
            CHGSYSVAL QUTCOFFSET offset

where offset is in the form +hhmm or -hhmm, that is, hours (maximum 24) and minutes ahead of or behind UTC, respectively. A sample offset for New York, for example, is -0500. Locations east of Greenwich are preceded by a positive sign (+).

You can obtain the current GMT online by accessing the U.S. Naval Observatory web site, for example, at:

http://tycho.usno.navy.mil

For more information about GMT in general, you can search on UT (universal time) on the Astronomical Applications Department of the U.S. Naval Observatory website:

http://aa.usno.navy.mil

Prepare your DB2/400 Environment

Data Integration is designed for distributing SQL tabular data or user changes to that data. If the data can be accessed through an SQL entity that is represented in the SQL system catalog, it should be distributable. The table below lists the table types are eligible for distribution as DB2/400 source or target tables.

DB2/400 object

Data Integration Director category

Copy or Replication source

Copy or Replication target

Table (SQL)

Table

Both

Both

Physical file

Table

Both

Both

View

View

Copy

Both (only if updateable)

Logical file

View

Copy

Both (only if updateable)

Alias for table

Alias

Both

Both

Alias for multi-member file member

Alias

Both

Both

a The check box label you select in Director when you retrieve that object’s data from the DB2 system catalog into your Data Integration model.