DUMP in RPG (was: RPG enhancement suggestion)

>>You mean most applications dont include a DUMP as a standard part of
their error processing! How do you fix errors in a client system?<<

A lot of interesting comments of how and why and when to use DUMP.  I've been
following this thread with interest.  In most all the environments I've been in,
specifying debug(*yes) or an H-spec with '1' in column 15 is done only in a
development/testing environment.  It is removed once it goes into production.
But, then, like others have suggested here (Hans?), these have always been
in-house situations where we can pick up the dump by responding to messages with
a 'D'.  Obviously it's a different thing altogether when you're a software house
with customers all over the place using software that you have to support.

On the basis of a suggestion (I think) I heard a while back in this list, I
searched for a "dump" API and found QPDLOGER.  The API is defined in "System API
Reference - OS/400 Problem Management APIs" (Document Number SC41-5869-01).
Examples using this program are found in "System API Programming" (Document
Number SC41-5800-00).  FWIW, we're running V4R2.

Has anyone used this API?  If so, how?

- Dan Bale





* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *