Using SQL rather than native I/O to query and manipulate the database is more than replacing one syntactical regulation with another. It requires a different way of thinking. Nevertheless, corresponding features do differ, and today I show one way that the SQL update differs from a native update.

Consider the following scenario from a project in which I was recently involved.

I needed to read a database table (physical file) from top to bottom. After I retrieve each row (record), I called one or both of two high-level language programs, using parameters to pass data values from the table and

The Work with Links (WRKLNK) command is underwhelming. If it were my software, I would add a lot of options to it. But since it isn’t my software, I’ll content myself by using an alternate green-screen interface that has features that are missing from WRKLNK.

The alternate interface to IFS directories is the Edit File (EDTF) command. If you specify a single file name in the FILE parameter, EDTF opens the file in the editor. However, if you specify a directory name or a wildcarded name, EDTF presents a directory listing. (The Display File (DSPF) command works the same way.)

I’m looking at my work management setup on one of my System i boxes. I noticed that all the jobs in my QBATCH subsystem are executing at run priority 20, the same priority as my interactive jobs. What’s going on, here, and how do I reset my batch jobs to run priority 50 where they belong?

–Henry

In three steps, here’s what I think is happening and how you can change your batch run priorities.

Step 1: Your job and its routing data

Each submitted job has its own routing data. Job routing data can easily be viewed through the