We have a sequential (i.e., unkeyed) database file that contains several years of shipment transactions. We’ve built a lot of indexes over it, and we slice and dice it daily, all day long, from both programs and queries. We have two problems that surface occasionally.

The first problem is that sometimes we are not always able to see shipments in chronological order. Since we only store a shipment date, but not a time, we depend on the order in which shipments are loaded into the file to tell us which shipment occurred before another. Depending on the order in which

The following question was posted to the online forums at IT Jungle: We are getting a new iSeries and upgrading to V5R3. At present, we are on V5R1. We plan to run parallel for testing. Is there a way to move the output queues and/or their contents to the new machine?

—pmslic

Here is the answer that RussK provided.

I just found a note I’d made on iSeries Navigator: “In a multi-system environment, you can even drag from an outq on system ‘A’ to an outq on system ‘B’, and the spooled files will move from one system

One big pain in configuring iSeries Access for Windows PC5250 sessions is determining where to store your session files and how to create shortcuts so that your users can easily locate and launch their 5250 sessions. Like many things in the computer world, however, session file management is not as clear cut as it should be. But there are a few simple tricks for simplifying the process on a Windows desktop.

What Are PC5250 Session Files?

As you probably know, PC5250 session files are executable Windows files created by using the PC5250 emulation program in IBM‘s iSeries Access for