|
I'd use an API to search the call stack to see if the RPG program is already there. Then you can take an appropriate action. -----Original Message----- From: Feador, Jerry [mailto:JFeador@xxxxxxxxxx] Sent: Monday, March 03, 2003 3:46 PM To: 'RPG programming on the AS400 / iSeries' Subject: Preventing a recursive call... Hi All, Does anybody have a clue as to how I can prevent a recursive call from a command? The scenario is.... I have a command which calls a CL(1) which calls a CL(2) which calls an RPG... at this point it's allowed, and common, to get to a command line, where everybody forgets that they've called the command once already - calling the command again generates a recursive call error in the RPG program... I've searched the archives and tried every combination of MONMSG's and *PSSR's that I can come up with, yet the error prevails... Any ideas on how I can get the first CL(1) to end if the command is already in effect (or running, or whatever)? TIA, Jerry _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.