Before you reorganize a physical file, consider which access path is most important to you. Taking the default of reorganizing by the key specified in the physical file DDS may not always produce the best performance for your particular applications. Let's use the example of a customer master file that is indexed by customer number, but must be scanned quickly by your phone order-entry users in company name order. The reorganization default is to physically order the records by customer number. The best performance can be achieved by sequencing the file in the same order as the customer name access path used by the order-entry program. This is easy to do with the RGZPFM command. The following command will reorganize file CUSTMAST by customer name by using the existing logical file member CUSTMAST01 in logical file
CUSTMAST01: RGZPFM FILE(CUSTLIB/CUSTMAST) + MBR(*FIRST) KEYFILE(CUSTLIB/CUSTMAST01 + CUSTMAST01)
Midrange Computing
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