|
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 Behalf Of Neeraj.Verma@smed.com Sent: Tuesday, July 31, 2001 9:31 AM To: RPG400-L@midrange.com Subject: Delete Interactive Call Hi, I have a very strange requirement and am not sure if there is any solution. Problem is as follows: I have a call tree like PGMA-->PGMB-->PGMC. These programs can be a mixture of OPM and ILE. I have created a menu and an interactive call to PGMA is attached as a menu option. PGMA can be called either from Menu or Command line. During my call to PGMA, suppose PGMC has some error. I want to trap the error, show user a relevant message, kill all the call stack programs(PGMA, PGMB & PGMC) with no further processing and come back to same starting place(Menu or Command line). Is this possible? Is there a command or API to kill the call within the job and return to same starting place? ENDRQS kills the call level but does not return to same starting place. Please let me know your suggestions. Thanks Neeraj ---------------------------------------------------------------------------- --- This message and any included attachments are from Siemens Medical Solutions Health Services Corporation and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to CSOffice@smed.com. Thank you +--- | 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 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.