|
Try using a validity checking program on the command which checks the call stack. If it finds the CPP in the call stack, return an error. There are a couple of different methods for checking the stack including using APIs. A simple way to check the stack without having to use an API is simply to send a message to the program message queue and monitor for an error. If no error occurs, the program is in the stack. 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... Mike Richardson Merchandise Accounting Analyst Costco - IS Department (425) 427-7435 MRichardsonx@xxxxxxxxxx
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.
midrange.com
