× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. October 2017

Re: Program failure analysis

On 10/13/2017 11:11 AM, Joep Beckeringh wrote:
In one of your earlier posts you wrote that you never ever want a
program to go into MSGW. That implies that you need some sort of post
mortem logging.

Right. The pattern of 'dump at the point of failure' sprang up when I
started working with CGI programs, and I continued it with LANGUAGE
RPGLE stored procedures that are called by .NET. It's not a good thing
to have thousands of QSYSOPR messages when you come in after a weekend off.

OTOH, if you do allow a program to go into MSGW in case of an unforeseen
condition, you have a near perfect situation for investigating what went
wrong. That may be the choice (conscious or by default) of many
programmers. So you have to weigh the cost of an occasional MSGW against
the cost of handling every possible condition.

Good point, thanks Joep!
--buck


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.