This is a provider for Linq2DB to allow access to DB2 running on an IBM iSeries (AS/400) server.

It has been tested on iSeries v7.1 & 7.3 with iAccess for Windows version V7R1M0 with service pack SI55797

Installing the Linq2Db4iSeries NuGetPackage will automatically install the Linq2Db package.

IBM do not provide a standalone install of the IBM.Data.DB2.iSeries packages nor do they provide a NuGet package for them. They are include with iSeries Access for Windows (http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzaij/rzaijrzaijinstall.htm) which will need to be installed onto each machine that runs the software.

You will need to add a linq2db section to your app.config/web.config file in order to add the DB2iSeries provider into Linq2DB

<configSections>
	<section name="linq2db" type="LinqToDB.Configuration.LinqToDBSection, linq2db" requirePermission="false"/>
</configSections>

<linq2db>
	<dataProviders>
		<add name="iSeriesProvider" type="LinqToDB.DataProvider.DB2iSeries.DB2iSeriesFactory, LinqToDB.DataProvider.DB2iSeries" default="true"/>
	</dataProviders>
</linq2db>

The data provider name (e.g. iSeriesProvider) is what you will use as the providerName in you connection string.

You will need to provide valid iSeries connection strings at the very least specifying Data source, User Id and Password. e.g. Data Source={SERVER_NAME}; Persist Security Info=True;User ID={USER_ID};Password={PASSWORD};Library List={LIBRARY_LIST};Default Collection={DEFAULT_LIBRARY};Naming=1"

The rest of the usage is exactly the same as Linq2DB. See https://github.com/linq2db/linq2db/blob/master/README.md for further examples.

The provider can create SQL compatible with V7.1 and above.

V7.1 PTF Level 38, V7.2 PTF Level 9 and V7.3 introduced a proper syntax for SKIP (OFFSET n ROWS). To have the provider generate this new syntax add MinVer="7.1.38" to the Provider or, if instantiating the provider in code set the parameter appropriatly.

DB2 doesn't have a GUID type. By default GUIDs will be stored as CHAR(16) FOR BIT DATA. This works and is probably the most efficient however it is unreadable when queried directly.

Setting MapGuidAsString="true" (or setting the parameter true in the constructor) will save the GUID in clear text. The underlying column should be set to VARCHAR(38) data type.

1. The SchemaProvider implementation only returns details of the objects within the library list configured in the connection string even if the iSeries configuration for the user has other default Libraries specfied
2. Any objects created using this provider (e.g. as the result of a Create table statement) will be created in the Library in the Default Collection connection string parameter. If this is not specifed then it wil be created in the default library for the user account.
3. Transactions can only be used if journalling is set up on the table (file). If the iSeries schema is created with a CREATE SCHEMA command then this will be set by default however if the schema is created using the iSeries commands then you will need to either add journalling to the table explicitly OR create a journal receiver called QSQJRN in the Library to have journalling automatically applied to each table.
4. This is currently only working for .Net 4.0/4.5

See https://github.com/LinqToDB4iSeries/Linq2DB4iSeries/wiki for further information.