This chapter contains information to aid in diagnosing problems that you might encounter while running your EGL applications.
EGL applications are implemented on iSeries just like other third-generation language (3GL) applications or programs. This is important to remember, should you or the IBM(R) Support Center need to collect extra ordinary problem diagnostic information in the course of investigating a run-time error.
iSeries standard diagnostic commands are available to you when diagnosing problems with a EGL application. These include such commands as the following:
In most error diagnostic cases, you need to have the following information available when you contact the IBM Support Center:
To ensure that second-level text is included, change the job before starting the failed scenario using the command CHGJOB LOG(4 00 *SECLVL). When the job ends, the job log is spooled to the assigned output queue. Usually, the most important information in the job log is the escape messages that initiates the abnormal condition, which caused the EGL application to end. The program sending the message, the program receiving the message, and the instructions being sent to the program are the key pieces of diagnostic information. The other messages are also important. Be sure to inspect and report the entire job log of information.
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.