Regarding "Duplicate Record WRITE Performance" (TechTalk, MC, January 1995): while using a CHAIN before a WRITE can outperform a conditioned WRITE operation when writing duplicate records to a unique file, I have some information you may find useful. My company tested this and found that, if the number of duplicates is small (specifically less than 12 percent from the primary input file), it is more efficient to do the conditioned WRITE than suffer the overhead of the CHAIN operation. This test was done about a year ago on a B50 under V2R1, but I am sure current results would be comparable.
- Jonathan Frankel
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