|
We use a parm to tell when we call program b from another program, say a. We disable the function keys in program b when not called from a menu but from another program using a function key. The users are forced to return to program a. This keeps the users from getting lost... This is much simpler than trying to read/control the program stack. One level of JUMP only. You can also have your parm allow for several levels, each one holding the from program name, say 10 levels with a second parm being an array of 10 element of 10 chars to hold each program name. Christopher K. Bipes mailto:ChrisB@Cross-Check.com Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com CrossCheck, Inc. http://www.cross-check.com 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 -----Original Message----- From: Marc Zylka [mailto:mzylka@netpath.net] Sent: Wednesday, July 07, 1999 8:38 PM Subject: Recursive Calls I'm curious about how most people handle possible recursive calling situations. We're running V4R1 and coding in RPG/ILE. We have a situation where program A is called from a menu. Program A creates a workorder and then calls Program B, the workorder maintenance program. From the workorder maintenance program, one can use F6 to create another workorder, thus calling Program A. So, the questions: When Program A calls Program B, can I remove it from the program stack? Can Program B remove it from the stack when it realizes that Program A needs to be called? If program B can remove Program A from the stack, what happens when Program B ends and Program A is no longer there to go back to? If any of this can be done, which manual outlines how this is done? Thanks in advance, Marc Zylka ( mzylka@netpath.net ) +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.