iSeries survival guide for a Unix/Windows techie

I'm a developer working mostly on a Java application which interfaces with an iSeries back end (the iSeries is running OS 6.1). I consider myself to be reasonably strong on DBA and sysadmin topics (*nix and Windows) but the iSeries world is quite alien. I don't need to become an expert, I'll never be called upon to do admin work but I would like to talk the language of iSeries people. Terms are so loaded that it's very easy to get the wrong end of the stick but the iSeries admins have an exclusively iSeries background so it's quite difficult to gain a common understanding.

So, what I would love to find is a guide to iSeries systems for someone who already has a good knowledge of software and systems. Any suggestions would be greatly appreciated.


The best guides to iSeries are probably redbooks. Here's one that looks like it might be on the level you described: http://publib-b.boulder.ibm.com/abstracts/sg247713.html?Open

Here's the link to a search of 6.1 in iSeries redbooks: http://publib-b.boulder.ibm.com/Redbooks.nsf/searchdomain?SearchView&query=%5Bsubjects%5D=AS400+and+6.1&SearchOrder=1&category=systemi


For a DBA, it is quite simple (in my opinion anyway).

  • Library = Database
  • File = Table
  • Logical (or logical file) = View or Index depending on the use
  • Record = Row
  • Field = Column
  • Object = Anything on the system. It could be a file, a library, a program. They all become objects.

As far as resources, quite the collection is being built at the Midrange.com Wiki. The IBM i Information Center is another good resource. Specifically the section on SQL.

One note, the i has a "language" that creates these physical and logical files called DDS. Many programmers that I know still seem to use this instead of SQL. SQL can of course be used to create the tables as well.

For the security aspect, I haven't worked enough with other databases to properly compare. Typically, the built-in object security is used using one of a few methods. Authorization List is one I like as a better solution for securing large numbers of objects.