Getting the
Db2 for i .NET Data Provider
Up and Running

• Use Visual Studio IDE and c#, VB.NET or 3rd Party Languages to run Db2 for i SQL and stored procedures
  
  
• Installing and Specifying Settings (Plumbing)(Call Us if you get stuck!)
• the latest version of the .dll shows File Version 13.0.20.2 (in Windows/assembly).  13.0.0.2 is quite a bit older (Client Access 7.1) but works fine in a lot of cases 
• for a website project or a web app, installation of the .NET Data Provider is the only component that is required on development workstations and the only component required on the production web server (Windows Server 20xx running IIS). 
  So specify a custom install as shown in the picture. 
  
• 
  
• In other words, please do not, for example, follow the instructions in this video, Installing ACS Windows Package, for purposes of loading the IBM. NET Data Provider because it does the default behaviour which is to install everything which results in a bunch of stuff you don't need for the workstation being installed and stuff you definitely don't want at all when installing on the Windows Server.
  
  
• Let us help you with Q&A, providing examples or custom development contracting
• We can help you formulate strategy, train your resources or do the development
  
  
• Get the full scoop in our new tutorial, training and source code bundle, Get Running - TechCrystals Code Package
  
  
• The SQL features available to use will be based on the target IBM i server OS level, so the latest and greatest stuff from IBM i 7.3 and 7.4 will be available.  Similarly the .dll works fine with i5/OS V5R4 through IBM i 7.2.
  
  
• For compiling of the .NET project, the .dll will work with FW projects compiled all the way up to the latest, such as FW 4.8
• In some cases, when targeting older versions of the FW and/or using old versions of the .dll and/or using the website project model, special web.config syntax may be required, please contact us.
  
  
• 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.
  
  
• 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=192.168.1.10; 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
  
  

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