There are times when you may wish to run a program that writes records to a file, but for test purposes, you wish to prevent this from happening. You could recompile your test program, commenting out the write or update operations, and changing the file specs so the compiler doesn't give you an error message. However, a much better and easier approach is to use the INHWRT(*YES) parameter on the OVRDBF command. You should execute this command for each file you wish to inhibit at the beginning of your jobstream. Be careful not to misspell the file name. You will not get an error message if you do, but the file will not be overridden. (To check that the override has occurred, use the DSPOVR command.) After the override command is executed successfully, the program will act just as before, but no data will be written.
Jon Vote Medford, Oregon
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