I have been gradually converting RPG II programs to RPG/400 programs and running them in the S/36 Environment using OCL procedures. During this step-by- step conversion process, one of my RPG/400 programs crashed due to a missing file. The missing file, which was a program-described file, should have been built according to the method traditionally used on the S/36, which places the // FILE NAME-xxx,RECORDS-xxx statement between the LOAD and RUN statements. It seems that this method will not work after // LOADing an RPG/400 program. After removing the RECORDS parameter from the // FILE statement and using the BLDFILE procedure to create the file beforehand, the RPG/400 program ran successfully.
Using //FILE to Build Files
Typography
- Smaller Small Medium Big Bigger
- Default Helvetica Segoe Georgia Times
- Reading Mode
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