Sometimes when coding a Windows client/server application it can be a bit pesky dealing with the problem of knowing everything about the operating environment. In the System i and AS/400 world, factors like the host i5/OS version and release, and the iSeries Access (now called System i Access) version and fix pack level, can determine whether or not your software can run correctly. In the “IBM AS/400 iSeries Access for Windows ActiveX Object” library, IBM has given developers the tools to programmatically detect this information and thereby circumvent potential problems for environments that are not at the correct software level.

I hope my question is an easy one to answer. I have a file that stores the location of inventory in a warehouse. Location consists of a row (an aisle), column, and level. Why will an SQL UPDATE let me change the column and level, but not the row?

–Scott

You can update the column like this:

update qtemp/inventory 
   set column=4        
 where item = 'SL-701'

But updating the row gives you error SQL0104. (Token 4 was not valid. Valid tokens: ( : DAY CAST CHAR DATE DAYS HOUOUR LEFT TIME TRIM YEAR COUNT MONTH.)

update qtemp/inventory 
   set row=4           
 where item 

In a recent article, I detailed how to use common i5/OS commands to easily transfer System i objects between partitions. After publication, several readers wrote to say that if you have a working SNADS network between your target and source partitions, transferring objects is incredibly easy if you just use the commands that come with IBM‘s free ObjectConnect licensed program. And you know something, they’re right! ObjectConnect is easier.

This week, I’ll review what ObjectConnect does for i5/OS object movement between systems, how to make sure that you have it installed on your machine, and how to use