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

• 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
  
  
• 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!)
• for a website project or a web app, installation of the .NET Data Provider is the only component that is required on Windows Server running IIS and development workstations, so specify custom install
  
• 
• 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 but works fine in a lot of cases, provided it was installed properly 
• get the full scoop on downloading and installing the latest version of the ACS Windows Application Package, without registering on the website by attending our new presentation at POWERUp19™, Get Running with the IBM .NET Data Provider and Db2 for i  (included hand-outs and downloads no longer visible now that the conference is over)
  
• The SQL features available to use will be based on the IBM i server OS level.  Similarly, the .dll works fine 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 (provided the web.config file specifies the .dll to run at v2.0.50727)
  
  
• 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=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