×
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.
David,
Evil? Really? Why?
To my view, a *PSSR allows *you* to control how errors are handled - you can
decide to set error codes etc., or bypass a RETURN within the *PSSR, thus
making OS/400 take control. You can dump the procedure, send error
mesages... the list goes on. Now, a badly-written *PSSR can be evil, but
that's like saying that the RPG Cycle is inherently bad or that guns kill
people...
Do you also think MONITOR-blocks are evil?
Rory
On Mon, Jul 28, 2008 at 10:57 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:
Rory Hewitt wrote:
thus *completely* masking to the caller the fact that anything went
wrong!
Personally, I think the *PSSR subroutine is evil. I only use it in highly
specific situations (like where the failure of a program should not
interfere with the execution of a job ... and the program in question is not
mandatory).
david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.