RE: Multi Occurrence Data Structure returned from a procedure

>> The best I've seen to date are Scott Klement's naming conventions (for
>> example, his error structure is dsEC).  I've co-opted them in some of my
>> stuff with a couple of minor changes.

You might want to look at my trigger mediator. I don't use error structures at 
all. I used to do something like that but stopped developing that way and went 
back and rewrote my functions to use my current system because if it comes back 
and the programmer is expected to do something, they will absolutely not do it. 
Now if they make the call, put a monitor around it, there is nothing I can do 
about that but that is on there shoulders. If they don't monitor, which most 
time programmers don't, then they are going to get a detailed message stating 
the problem when the program blows. Over and over again I got calls from 
programmers. "Your stuff is not working" and then find out the program returned 
an error status but they never checked it so created a system that does not 
expect them to do it.  

-----Original Message-----
From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, July 06, 2005 4:44 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Multi Occurrence Data Structure returned from a procedure


Alan, this is an interesting idea.  Typically, open source iSeries
projects like this tend to fizzle, but I'd like to see if maybe we can't
get one to work.  David is already doing a Wiki, so maybe a repository
of code is also an idea whose time has finally come.

I'm absolutely buried until August, but once I come up for air, I'd like
to try to get a project like this started.  In the meantime, perhaps we
can start coming up with things we'd like to see.  For one, I'd love to
see a set of standard calls to the various system APIs.  This is
actually a bit more complicated than at first blush, because one of the
first things you need is a standard error structure, which in turns
means some sort of standard naming convention.

The best I've seen to date are Scott Klement's naming conventions (for
example, his error structure is dsEC).  I've co-opted them in some of my
stuff with a couple of minor changes.

A big issue here is whether we should try to keep at least one version
available for the folks who are still at back versions like V4R5.  It
might not be complete, but I'd hate to leave those folks out (and
according to polls, there are a lot of them out there) just because they
haven't had the opportunity to get to the latest release.

Joe

> From: Alan Campin
> 
> There was talk at one time of developing standard class libraries
> (Standard service programs) at one place but with all out ego's (Mine
> especially), nothing has come of it. I would especially like to see
> libraries with standard error handling models like I do in mine. Seems
> like that is the piece I see missing in other stuff I see.
> 
> Jon, I wonder if this is something you might consider for the new
version
> of "I Didn't Know You Could Do That?". Standard class libraries
available
> for download and all examples using the standard class libraries and
> discussion of how the class libraries were developed. Just a thought.