If you write RPG subprocedures, you should know about the differences between automatic and static storage. (If you don’t write subprocedures, shame on you!) I’ve found that many writers and/or users of subprocedures don’t fully understand the differences. So let’s start at the beginning.

By default, fields (i.e., stand-alone fields, data structures, arrays, etc.) defined inside a subprocedure (a.k.a. local fields) use automatic storage. This means that the storage doesn’t exist until the procedure is called and it is cleaned up when the procedure returns to its caller. Of course, since the storage goes away between calls to the procedure,

Note: The code accompanying this article is available for download here.

In the past couple of years, I have talked with colleagues and read articles about the complexity of WebSphere and the resources it uses. There are alternatives to WebSphere when you need a Servlet or JSP container. Apache Tomcat is probably one of the better known competitors to WebSphere. However, I would like to introduce you to another one that is smaller, easier to manage, and just plain works: Jetty.

Introduction to Jetty

Jetty is an open source Web server–implemented in Java–that provides Servlet and JSP support,

Many i5/OS administrators hate system audits the way dental patients hate getting their teeth filled: they despise it with all their might, but realize the process might be somewhat healthy and beneficial for their system. This week, I’m going to look at some common system auditor requests for i5/OS configurations and show you how to retrieve that information from a Power i, System i, iSeries, or AS/400 machine.

Default Passwords

Your auditor may request a list of all users who use default passwords. Default passwords occur when the user’s password is the same as his or her user ID name