There is a bug in the V2R2M0 SUBR23R3 message-retrieving subroutine. When you override QUSERMSG to another message file and try to retrieve a message ID that exists, the subroutine works properly and the message text from the overridden file is retrieved. When you try to retrieve a message ID that doesn't exist, the subroutine returns code 5 (Message file QUSERMSG in *LIBL not found) which appears in your job log. If you create an empty QUSERMSG in your library (IBM recommends QGPL), the subroutine returns code 2 (Message ID not found) and no entries are made in your job log. The command would be:
CRTMSGF QGPL/QUSERMSG.
Editor's Note: This bug has been fixed in V2R3.
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