How to interpret JOBLOG to analyze the problem?
Dear AS/400 Lovers!
I frequently have compilation & execution errors & need to analyze the JOBLOGS.
How to interpret JOBLOG to analyze the problem? More than that, I have issue in getting to the roots of the problem(i.e. I find difficulty in zeroing-in on the root cause) through analyzing the JOBLOG.
Most of the time it is not understandable. for e.g. it gives some error messages like the following ....
--------------------------------------------------------------------------------
Function check. CPF9897 unmonitored by RCEID043 at statement 5200,
instruction X'005B'.
CPF9897 received by RCEID043 at 5200. (C D I R)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Application error. RNX1216 unmonitored by RCEID003 at statement 0001000001, instruction X'0000'.
-------------------------------------------------------------------------------
I go really mad at these messages; get really pissed-off.
Is there any clean & clear way to interpret/Understand error messages like these.
I always use to neglect this kind of messges, but would struggle to resolve the problem.
I think if we can clearly interpret/analyze & Understand these kind of messages, we can solve the problems/issues more easily.
Do you guys agree with me? Let me know.
Thank You guys for your help,
Svanky
Software/Hardware used:
AS/400, OS/400, RPGILE
Software/Hardware used:
AS/400, OS/400, RPGILE
ASKED:
May 26, 2010 2:19 PM
UPDATED:
May 27, 2010 12:02 PM
Answer Wiki:
To start with, the problem isn't that the messages are not understandable. The problem is that the programs aren't handling errors and aren't reporting their errors properly.
<i>Application error. RNX1216 unmonitored by RCEID003 at statement 0001000001, instruction X'0000'.</i>
Program RCEID003 received error message RNX1216 and didn't really do anything about it. Apparently, all that it did was send another error message -- CPF9897. It apparently then chose to end, most likely because it sent the CPF9897 message as an *ESCAPE message. Now, you don't show the CPF9897 message, so I can't say anything about it. Maybe it explained what happened and maybe it didn't.
You also don't show the RNX1216 message. I don't know if it was in the joblog or if your RCEID003 program removed it from the joblog. The RNX1216 message should have some detailed information about what happened. If it was removed by your program, it's the fault of the programmer that important information about the error was removed.
<i>Function check. CPF9897 unmonitored by RCEID043 at statement 5200,
instruction X'005B'.
CPF9897 received by RCEID043 at 5200. (C D I R)</i>
That simply says that program RCEID043 received a CPF9897 *ESCAPE message at statement 5200 and didn't do anything it. Find the programmer and ask him/her why errors were just ignored.
The description of the RNX1216 message that apparently signalled the start of the sequence is probably found where all RNX messages should be found -- in message file QRNXMSG. If the text of the message isn't in the joblog, you'll have to figure it out yourself by looking at the message description and the program. You should be able to figure some of it out by looking at a compile listing of RCEID003 to see what file is being defined at statement 0001000001. I'd guess that it will be the first file in the program since the statement number indicates the first statement of the first file.
The problems are in the programming, not in the messages that you showed. I can make a lot of sense just from the small pieces that you posted. A little better error handling in the programs is probably all that's needed.
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
Thanks a lot Tom for your inputs