|
>> You can't use subprocedures in the default activation group. This is not true - although it is not a bad idea <grin> However it is true that you cannot use subprocedures when you specify DFTACTGRP(*YES) (which is the default). I think the confusion arises from the rather bad choice of name for this particular compiler directive. It should really be named Compatibility Mode since it has little to do with where the program runs. Rather it determines if an "RPG/400 style" program is to be created or not. If *YES, then the program behaves like an RPG/400 program and therefore is not allowed to use subprocedures because they are a bound call which RPG/400 can't do. If *NO then the program can use all the features of RPG IV including subprocedures and can run anywhere. If you want to test this, compile a program which uses subprocedures and specify DFTACTGRP(*NO) together with ACTGRP(*CALLER). Call the program and see where it is running, you'll see it is in the default AG. +--- | 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.