My article "Easy and Powerful Message Presentation" (April 1992) described the usage of message subfiles to present messages in application programs typically written in high-level languages like RPG. Everything was peachy until we came across a bug-not in the message subfile technique, but rather in its implementation in RPG. This is what happens:
You code a CALL operation to execute a CL program that sends messages to the RPG program, including an indicator in columns 56-57 as shown in 2a. This indicator turns on if the CL program ends abnormally, so your RPG program can sense this abnormal termination and take corrective action.
You code a CALL operation to execute a CL program that sends messages to the RPG program, including an indicator in columns 56-57 as shown in Figure 2a. This indicator turns on if the CL program ends abnormally, so your RPG program can sense this abnormal termination and take corrective action.
The problem occurs when you use this technique with the message subfile: the system insists on issuing a function check message (CPF9999, which is *ESCAPE) whenever the CL program ends abnormally, even if you monitor for this condition with the RPG indicator in columns 56-57. So when your message subfile is presented, it will have one message at the very bottom that you didn't send and that looks serious enough to confuse (and scare off) the user.
Fortunately, the solution is rather simple. AS/400 messages are powerful; all you need to do is CALL a new CL program if the RPG indicator is on. The CL program (RMVLMSG) removes the last message from the caller's program message queue (which is the CPF9999 message issued by the system), thus cleaning up the message subfile. The RMVLMSG program is shown in 2b.
Fortunately, the solution is rather simple. AS/400 messages are powerful; all you need to do is CALL a new CL program if the RPG indicator is on. The CL program (RMVLMSG) removes the last message from the caller's program message queue (which is the CPF9999 message issued by the system), thus cleaning up the message subfile. The RMVLMSG program is shown in Figure 2b.
We thought that this problem should be fixed by IBM, but (quoting) "The development at this time has no plan to incorporate such enhancement." Unquote. Hooray for IBM.
TechTalk: Message Subfile Bug
Figure 2A Typical CALL statement
Figure 2a: Typical CALL Statement ... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 C CALL 'CLPGM' 99
TechTalk: Message Subfile Bug
Figure 2B CL program RMVLMSG
RMVLMSG: + PGM RCVMSG PGMQ(*PRV) MSGTYPE(*LAST) RMV(*YES) ENDPGM
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