Well, I have been bitten by the IBM Gotcha again. It seems that in the switch from V1R3 to V2R1M0, they forgot to tell us about the record locking problem. On a record lock condition, we get the error message as before: "Cannot allocate record in file: (response options)," so we reply R just like always, and... surprise! "Program compiled at V1R3, Retry option not allowed."
Well, isn't that a friendly little surprise? So, IBM wants me to spend many, many days recompiling all of my RPG programs in this canned software package that I have, just to pay the price of upgrading my operating system release level.
Mom told me I should've picked another career.
Editor's Note: Ideally record locks should be handled by the application program. Sounds like this canned software left it out.
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