In "Duplicate Record WRITE Performance," in TechTalk (MC, January 1995), Blair Hamren explains how to gain performance improvement and a smaller joblog by using a CHAIN to check for duplicate records before writing to a database file instead of using a WRITE with an error indicator specified.
Assuming it is a CHAIN by key, an even more efficient way to accomplish this would be to use the key value with the SETLL op code and an *EQ indicator in the equal column. If the specified indicator is *ON after the SETLL, then the key exists. The benefit is that you find out if the key exists without doing a disk I/O, and you avoid overlaying your original record field values with the values from the "chained" record.
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