|
>> Thanks Joep - I knew there was something I missed! You are absolutely right that you need to use a named activation group to use subprocedures. That is sorta kinda true. If you keep to using subprocs that are either within the program source itself or are bound by copy you can use them. Compile with DFTACTGRP(*YES) and ACTGRP(*CALLER) and they will work just fine - no OVR problems or anything. Using Service programs in this way (i.e. binding subprocs by reference) is something I would rather do only a named AG. You can run into all sorts of fun problems if you use service programs 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.