If you use the Programming Development Manager (PDM) but still use the traditional source file names, QRPGSRC, QDDSSRC and QCLSRC, you may find yourself jumping from source file to source file as you work on an RPG program, then its display file or printer file, then back to the RPG program again.
With a good naming convention, you can put all of your source members for a given application in one source file. For example, an accounts receivable application can have an RPG program called AR001R with a display file called AR001D and a printer file called AR001O. This program might be called by a control language program called AR001C, and may use a physical file called AR001P and a logical file called AR001L1.
In PDM, option 3, "Work with members," enter the generic AR001* and you will be able to work with the source members for all the components of the application from one screen.
Christopher Andrle Lake View, New York
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