We have several sales history files–one for each year. When I need to combine data for more than one year, I have to use an SQL UNION. I am trying to group “unioned” data and can’t seem to get it right. Is it possible to group a dataset that is built by a union?

–Tom

This appears to be an easy problem to resolve, but appearances can be deceiving. If you’re not careful, you can get the wrong results when you UNION two or more tables, especially when you’re summarizing data.

Divide the query into two steps: one to union

Because we run packages, we do not get to use our i5/OS system knowledge very often any more, and thus some things fall through the cracks. For example, I recently had to add a field to a file that we had made accessible to Microsoft Access.

This special physical file (ALTINVEN) reflected a one record view of our two-file item master file. We store static info in one item file (ITEMSTAT) and dynamic info in the other file (ITEMDYN). As well-intentioned as this design may have been, both parts change regularly. The production department has some specific uses for the

We have some users who misuse the System Request menu by locking critical records and then transferring to an alternate job. They also sometimes use System Request-2 to cancel their previous requests when they should let those requests run straight through to completion. We’d like to restrict access to the System Request menu just for those users. How can I lock them out?

–Bert

There have always been some security and processing issues with allowing everyone to access the System i and AS/400 System Request menu. System Request menu access can be abused and some people need to be kept