What skills should an RPG programmer have besides knowledge of basic RPG?
Written by Jim Staton
Recently, I had the opportunity to interview candidates for a programming position at our company. I had just lost an excellent employee due to personal reasons, and I needed an additional person to develop and maintain the code on our iSeries. We have a small group of five iSeries programmers, four of whom spend most of their time developing and maintaining RPG code and are part of our total IT staff. The fifth develops programs for the iSeries as well as Windows and Linux servers, but in PHP and Java. As I looked through resumes and thought about the skills I needed in our company, I reflected on how much has changed in programming for IBM midrange systems since the early days of the AS/400 and what I now expect a programmer to know.
All you need is the User Function Registration APIs.
Written by Bruce Vining
Last month, in "Accessing a Command Line," we looked at how the Retrieve User Information (QSYRUSRI) API could be used to control access to a specific function with an application program. The function we were controlling was access to a command line window, displayed using the Display Command Line Window (QUSCMDLN) API, by way of command key 9. The application determined whether or not command key 9 should be enabled, based on the user class (USRCLS) attribute of the user profile currently running the application program. In this article, we will look at a more flexible approach to managing user access to an application program function. For demonstration purposes, the application function being managed will continue to be the ability to access a command line window (using QUSCMDLN).
A Webcast takes on all challengers, asserting that the technology works elegantly to modernize source-code available applications while saving time and requiring no programming.
Written by Chris Smith
There has been an air of mystery and, thus, skepticism surrounding RPG Open Access since IBM introduced it in April 2010 with the release of IBM i 7.1. The program, officially known as Rational Open Access: RPG Edition, was perceived as exotic and incomplete since it relied upon users or ISVs to write handlers to make it work, rather than providing a complete solution to, what might be called, GUI envy!