|
>> This is OPM behaviour, sometimes called dynamic binding. Which is also available in RPG IV (ILE) >> You use it in RPG via the CALL opcode and parm/plist. The called program uses *entry parm/plist to receive and return variable data. Or in RPG IV you can also use CALLP with a prototype and the called program can either use *Entry PList or a Procedure Interface >> If you re-compile the called program, the caller will use the new version on the next invocation. This is only true if the calling program itself has subsequently terminated with LR on or has been "cleaned up" by a RCLRSC. >> You must keep the parameter lists "in synch." though. Which can be simplified by using external descriptions, or (even better) using prototypes as mentioned earlier. +--- | 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.