I would like to illustrate an alternative to Kenneth Fordham's suggestion in
"Forcing Records to Disk" (TechTalk, MC, December 1994) and Rick Brandl's
suggestion in "Forcing Records to Disk, Part II" (TechTalk, MC, March 1995).
Instead of using the FRCRATIO parameter of the Create Physical File (CRTPF),
Change Physical File (CHGPF), or Override Database File (OVRDBF) commands to
force records to disk, use the RPG force-end-of-data (FEOD) operation as
illustrated in 1.
illustrated in Figure 1.
The FEOD operation allows you to force to disk all changes your program makes
to a file. Normally, the system determines when to force changes to disk; use
the FEOD operation in an RPG program to ensure that changes are forced to disk.
--Helmut Salzer
Forcing Records to Disk, Part III
Figure 1Forcing Records to Disk with the FEOD Operation
*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 C WRITERECORD C FEOD FILEX
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