|
Any interested persons, To answer my own question, at least in the case of RPGIV, I now know through trial and error that the program specified in a scope message is called when the procedure or sub-procedure ends. Even when *PGM is specified. NOT when the program ends, as stated in the manual. So *PGM and *CSE are equivalent with the transfer control exception. Whoever wrote that part of the manual gets a star. I guess I will send in the comment card. I would have really liked the scope program to be called when the program entry point procedure ends. Not when a procedure ends. Fortunately I have a work around, it is not what I wanted at all, but it sure beats the CEE register exit APIs. David Morris >>> "David Morris" <dmorris@plumcreek.com> 09/09 3:26 PM >>> One more thought, What about using a scope message? Even though a control boundary is not viable, the program level would probably be OK. If I send a scope message from a sub-procedure bound into a service program when is the scope program called? The manual is very vague. It simply says the program is called when your call stack entry, program, or job ends. It then goes on to talk about the only difference between call stack entry and program is when a transfer control occurs. This is further confused when later it says "when the caller's program ends", implying they are different. If anyone has any experience in this area I would appreciate a summary. Thanks, David Morris * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. 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.