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


  • Subject: Re: Delete Interactive Call
  • From: Gary Guthrie <garyguthrie@xxxxxxxx>
  • Date: Tue, 31 Jul 2001 12:29:37 -0500

Why go to all that trouble if the other programs need do nothing else?
Just send the escape directly to PGMA and be done with it.

Gary Guthrie
Senior Technical Editor, NEWS/400


JIM LANGSTON wrote:
> 
> The way this should be done, IMO, is to have PGMC and PGMB return a result
> indicator or some other method of communicating with PGMA (LDA, Return
> Value, whatever).
> 
> After PGMA calls PGMB it should look at the result indicator, and if an
> error is indicated it should RETURN.  PGMB should do the same thing when
> calling PGMC, look at the result, and if an error RETURN.  PGMC should
> handle any errors and any critical errors (can't be resumed) should set on
> the error indicator and return.  Then you at least get a semi-graceful exit.
> 
> Actually, this is not really a strange requirement but is used a lot in
> programs.
> 
> Regards,
> 
> Jim Langston
> 
> -----Original Message-----
> From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.