Query is the system killer. The lights dim. The system slows to a crawl. It must be a user running an interactive query.

Enough! No more interactive query for users–we are removing the *INTERACT option on the ALLOW parameter on the RUNQRY command. Sound familiar?

This extreme reaction of disabling interactive query is both unnecessary and, to be blunt, downright unfair to users. By disabling interactive queries, you also disable the ability to use the F5 (Report) key in Query, which is probably the most used function. And that, in turn, gets users into the frame of mind that, if

It’s not uncommon to have to update one file based on data found in another file. In fact, it’s a very common requirement, due to the way that data is “normalized” in relational database management systems. When only one field links the two files–the file that is being updated and the file that contains the search criteria–the SQL syntax is simple. But joining on two or more fields requires more challenging syntax.

Here’s an example of an update when only one field joins the two files. I add a week to the scheduled ship date of orders of type B

Buying a new Power i machine can be complicated. Not only do you have to correctly size everything for future growth, you also have to purchase the hardware, software, and maintenance at a reasonable price. And if your organization wants to lease its new machine, you may wind up scratching your head wondering just what those leasing numbers mean, or if your organization is being taken advantage of.

This issue, I’ll describe a way to approach a new lease, such that you can put yourself in a better bargaining position and better understand how the leasing company is pricing your