Db2 for i as Target - DSS 6 | Data Source Solutions Documentation
Documentation: Db2 for i as Target - DSS 6 | Data Source Solutions Documentation
Db2 for i as Target
Data Source Solutions DSS supports integrating changes into Db2 for i database. This section describes the configuration requirements for integrating changes (using Integrate and refresh) into Db2 for i location. For the list of supported Db2 for i versions, into which DSS can integrate changes, see Integrate changes into location in Capabilities.
Pre-Requisites
- The default library (current_schema) of the DSS database User must exist.
- Journaling must be enabled for the default library (current_schema), so that the table(s) created in it are automatically journaled.
Grants for Integrate and Refresh
This section lists the grants required for integrating changes into Db2 for i database.
-
To read and change the replicated tables, the DSS database User must be granted the following privilege:
grant select, insert, update, delete on <em>tbl</em> to <em>dssuser</em>;Alternatively, you can run the following command from AS/400 console:
GRTOBJAUT OBJ(DSS/*ALL) OBJTYPE(*FILE) USER(DSSUSER) AUT(*CHANGE) -
To use the default library (current_schema) and to create and drop DSS state tables in it, the DSS database User must be granted the following privilege:
grant createin, dropin, usage on schema <em>current_schema</em> to <em>dssuser</em>;Alternatively, you can run the following command from AS/400 console:
GRTOBJAUT OBJ(DSS) OBJTYPE(*CURLIB) USER(DSSUSER) AUT(*CHANGE) -
The DSS database User should have permissions to read the following system catalogs:
- qsys2.systables
- qsys2.syscolumns
- qsys2.systypes
- qsys2.syscst
- qsys2.syscstcol
- qsys2.sysindexes
- qsys2.syskeys
- sysibm.sysdummy1
- sysibm.sqlstatistics
According to IBM documentation, the tables and views in the catalogs are shipped with the
<b>select</b>privilege to PUBLIC. This privilege may be revoked and the<b>select</b>privilege granted to individual users. For example, to grant the<b>select</b>privilege on table columns in qsys2.syscolumns schema, use the following statement:grant select on qsys2.syscolumns to <em>dssuser</em>;
Intermediate Directory
{% partial file="dss6/requirements/source-and-target-requirements/intermediate-directory.template.md" /%}
Intermediate Directory is Local
{% partial file="dss6/requirements/source-and-target-requirements/intermediate-directory-local.template.md" /%}