Recently, I had to use an RPG program to write records from one file to another. The file I was writing to didn't allow duplicate records, but the file I was reading from did. I wrote my program, coding the error indicator on the WRITE op code to handle the duplicate record errors. My program failed because it wrote too many messages to the joblog.
I've learned a better way. Instead of using the WRITE with the error indicator, CHAIN to the file first. You may think it's a toss up as to which is the better method to use to see if the record exists, but I can tell you from experience it isn't. Numbers indicate a 33 percent performance improvement when using CHAIN. And you won't get a 3,000 page joblog.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online