Mobile Log In
       Where ERP Meets the Web

Getting the
Up and Running
  • Let us help you with development services or to supply examples
  • We can help you formulate strategy, train your resources or do the development

  • Use Visual Studio IDE and c#, VB.NET or 3rd Party Languages such as ASNA's Visual RPG for .NET

  • Installing and Specifying Settings (Plumbing)(Call Us if you get stuck!)
  • download .dll from NuGet Package Manager to Visual Studio project on client workstation; deploy/publish this version (shows as in the GAC)
  • note: latest .dll framework version is at 2.0, so this will require .NET Framework version overrides in web.config if you are running on or compiling to a later framework.  This is not a big problem in most cases really, however this means you cannot use FW 3.0 or later data features with the DB2i class, such as Entity Framework and obviously not projects based on .NET Core.  You can use the commit/rollback transaction construct as well as, for example, some nice features for working with stored procedure parameter initialization and OO datasets based on Db2 record layouts (or subsets of columns).
  • The SQL features and syntax are based on the IBM i server OS version as far was we can tell.  Similarly, the .dll works well with i5/OS V5R4 through IBM i 7.3 and .NET FW projects compiled all the way up to the latest, such as FW 4.7.2 as far as we can tell.
  • install only the .NET Data Provider and OLE DB Provider (only these two!) from IBM i Access for Windows 7.1, as specified in IBM i Access Client Solutions (ACS) Windows Application Package ReadMe document, onto both the client workstation (for development) and the web server running IIS (for production).  There will be some installation infrastructure that occurs with these installations that is required, which explains why the .dll does not run if this supplemental installation process does not occur...  The providers install on Windows 10, but again if you try to install more components from Access for Windows 7.1 or don't tell the project to run the .dll at FW 2.0, you are asking for quirky errors to surface at run time.

  • connection strings can take advantage of *LIBL technique (with Db2 for i version only)

  • Eliminate library and schema and testing-based hard-coding with library list technique!

    Please use the Contact Us phone number and extension for a no-cost, no-obligation discussion.  Or register and get a free code snippet of your choosing.

  • Here is a connection string example from a web.config file, based on a working production version, using the library list technique.  Remember to create your stored procedure and SQL PL with compatible syntax and options based on the system naming technique. 

  • <connectionStrings>

  • <add name="strDotNetDB2iCnnName" connectionString="DataSource=; UserID=USRPRFNAME; Password=USRPRFPWD; Naming=System; LibraryList=LIBNAME1,LIBNAM2,LIBNAM3;"/>

  • </connectionStrings>

  • Use inline SQL or stored procedure calls

  • Use Equivalent Constructs as with Other Data Providers for .NET Environment
  • define methods for Db2 for i access at the same scope and with the same functional equivalent as with those for MS SQL Server
  • most adapters are supported
  • populate and work with .NET FW OO dataset objects that were created via drag and drop from Db2 for i file columns and subsets
  • we like to characterize dataset objects as multi-occurrence data structures on steroids
  • you can even qualify to the column names based on ALIAS names, thus enabling verification of column names and data type and OO object compatibility at compile time

  • At POWERUp 2019 conference, we will be doing a presentation called Get Running with the IBM .NET Data Provider and Db2 for i, which will be focusing on the quickest ways to get this stuff up and running

  • A Pattern for Master File Data Layer (introductory plus options for industrial strength)
  • essentially a data access layer to support user maintenance activities with optimistic and pessimistic row locking features (and change detection for a subset of columns (not a row level timestamp)), is handled by 8 stored procedures... Here is a list of SQL PL stored procedures on Db2 for i.

  • Digital Asset Delivery Event file - Pertinant Details - Stored Procedures on Db2 for i

  • Additional features
  • meta data for stored procedure parameters is available to HLL such as c# or VB.NET
  • *LIBL (library list) path support for stored procedures
  • Good applicability of this technique with T-SQL and MS SQL Server
  • but probably not Oracle, at least for the locking and commit parts, as our understanding is there are some significant differences in how locking and commit technique are handled in the majority of Oracle relational database versions

Click below to Play Video:
Using Navigator for i to Update a Db2 for i v7r2 SQL PL Stored Procedure
with *LIBL and Record Lock features

Click below to Play Video:
Using System i Navigator to Update an SQL PL Stored Procedure on i5/OS V5R4
with *LIBL and Record Lock features

IBM.Data.DB2.iSeries.dll illustration

Microsoft Visual Studio Professional 2015 picture (for illustrative purposes only)

IBM Db2 for i picture (for illustrative purposes only)

  • Let us help you with development services or to supply examples
  • We can help you formulate strategy, train your resources or do the development

        go to the home page Top of Featured Services     go to next series page Next in Featured Services     Site Map     Switch to
Mobile View

You are at the web site of Tegratecs Development Corp.  Click here to go to the home page of this site...
Integrity, Integration and ROI from Your Software
Our contact information:
Tegratecs Development Corp.
1320 Tower Road
Schaumburg, IL 60173
( please register or sign-in )
© 2019 Tegratecs Development Corp.