Sounds great Nathan. I assume that you open all your files under user
control with the OPEN statement when using RPG. And, before you do, you
check that the person has the proper authority to the files, perhaps with
systableprivileges or some such thing?

And, before each write, you ensure that the file is not approaching being
full? You also keep a close eye on ASP space to ensure you don't overrun
that also, right?

I agree that checking before most common operations may ease the
programming involved in handling the errors. Like checking a logical
variable for true/false before writing it to the table. Versus writing it
to the table and checking the joblog for errors. I'll grant you that.

What I disagree with is that, since programming for errors (such as the
RPG monitor statement) can be a little complex (especially if you care
about a meaningful job log) that it should not be undertaken because the
developer is probably going to just muck it up anyway.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.