× 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. September 2003

Re: MONITOR performance

> Curiosity question:  Do you code the *PSSR in _every_
> RPG program you write?

Yes.  No exceptions.  Error handling is not something to be spray painted on
at the end of the design/coding/testing/deployment/maintenance/problem
reporting process.  Sorry; got carried away there.  You may be able to tell
I feel strongly about the subject!  Along with *PSSR, I always use an error
indicator (RPG III), or (e) extender (RPG IV) on every I/O operation.  Disks
fail; records get locked; terminals come unplugged and communications lines
fail (even TCP/IP.)

The one thing you should never EVER do: trap an error and then ignore it
(i.e. don't handle it.)  That is far worse than letting a program message go
through in production.  In my empassioned opinion.
  --buck

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.