× 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,

I've *often* seen

begsr *pssr;
return;
endsr;

thus *completely* masking to the caller the fact that anything went wrong!

Ahhh - good times :-)

That's why I write *all* my procedures with a return code (0 for success, -1
for failure) - the caller doesn't need to use it, but it's there if you
want.

Rory

On Mon, Jul 28, 2008 at 9:46 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:

Rory Hewitt wrote:
So what does this teach us? To include the DUMP opcode in our *PSSR
subroutine, thus avoiding all this hassle. <grin>

What? You mean ...

*INLR = *ON;
RETURN;

... isn't sufficient?

david

p.s. And, yes, I've seen programs where that was the extent of the *PSSR
subroutine.

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.