Use Named Constants to Write Clearer Code

August 18, 2004 Ted Holt

You’d expect experienced programmers to know and use techniques that less experienced programmers might not know. But even programmers with little experience know how to define named constants in one or more languages, although they may not know how to use them effectively. Yet named constants can contribute so much to program clarity, as I wish to show you now. I use RPG IV to illustrate, since that’s the language I use most often, but the principles apply to any language that supports named constants.

THE PROBLEM WITH LITERALS

The purpose of named constants is to avoid using literals, a

Securely Resetting Disabled User Profiles

August 18, 2004 Hey, Wayne O.

We have set system values QMAXSGNACN and QMAXSIGN to disable user profiles after three invalid sign-on attempts. Therefore, a common daily function that we do is to enable users that have typed their password incorrectly three times. As a result I have provided several people in the IT department with *SECADM authority. However, this allows them to change most, if not all, parameters in the user profiles that they have access to.

Is there a way to remove the *SECADM authority but still allow them to be able to change only the “status” parameter in the user profile from *DISABLED

Admin Alert: Searching for Elusive OS/400 Green-Screen Commands

August 18, 2004 Joe Hertvik

In spite of many recent graphical enhancements to OS/400, sometimes the fastest way to finish your work is by running an old-fashioned 5250 green-screen command. But the problem with green-screen commands is that you need to know the exact command name in order to run it, and executing the right command sometimes depends on how good your memory is. Fortunately, IBM offers a few easy to remember green-screen utilities for finding the right command at the right time.

The first place to stop during your command search is at the Major Command Groups menu. You can reach the MCG menu