One of the general paradigms of client/server programming is keeping the server side processing “fat” while keeping the client side processing “thin.” That is, a client/server application should let a server do as much work as possible while making as few assumptions as possible about how much processing power, memory, network bandwidth, etc., the client will have. Of course, sometimes certain applications, such as those requiring a graphics intensive environment, must be heavy on the horse power, but in general it’s good practice to keep network, memory, and processing requirements minimal on the client side.

One of the areas where

Put on your deerstalker hat. I’ve got a mystery for you. We are cleaning up disk and stumbled upon something that has us puzzled. The system tells us that a logical file in a test library has been used many times, and according to the object description, was recently used. None of our programs use the file, and no one has used the test library for a long time. Why does the system tell us we’re using a file that we don’t use?

–Rick

Rick and I solved his mystery with a little effort. There’s something to be learned in

I compiled your PSSWRDCHG program to change user passwords on the fly and modified it with your follow-up information. When we compiled it the normal way, authorized users couldn’t change passwords. We then compiled the program under QSECOFR with the User Profile parameter equal to *OWNER. It worked fine, but doesn’t compiling the program this way allow users with command line access to execute the program?

–Mark

Thanks for writing. This sounds like you have two questions about compiling programs with *OWNER adopted authority.

1. Does compiling a program with the adopted authority of the QSECOFR user profile allow any

Maybe “enhancing” is too strong a word, but “Add-Ons for CGIDEV2” doesn’t have the same ring to it. I have always been (and still am) a big fan of CGIDEV2. A tool, such as CGIDDEV2, must be flexible enough to cater for all tastes. But when you have nailed down your own standards and working methods it is sometimes easier to have add-on procedures to implement those standards and working methods.

With that in mind, I want to share a few of the subprocedures I have written that make CGIDEV2 a little easier to use in my development environment. All

Several good ways exist to convert letters from uppercase to lowercase and vice versa. Some take more effort than others. Here’s a very easy RPG method that you may not have seen.

Suppose a four-character program parameter is supposed to have one of three values: edit, post or both. Suppose further that you don’t want case to matter. The user can enter uppercase, lowercase, or mixed-case values. How do you go about testing the parameter in your program?

You could do it the hard way, that is, test for all possible combinations, like this:

 /free
    if inOption = 'edit' or 

Many standard configuration i5/OS Ethernet lines have a common problem. If the line loses connectivity for any reason, the controllers and devices attached to that line will go into a recovery pending state (RCYPND), which requires manual intervention to restart communication. I ran into this problem a few weeks ago and found two solutions for resolving the issue and automatically recovering communications after an outage.

What Happened To My Communications Line?

I experienced this issue when my network services people took down our core network switch for maintenance one Sunday morning, killing Ethernet and TCP/IP connectivity for all network users.