|
>> What I'm saying is that I am using protos but not specifying EXTPROC. That way I can define which parms go it. I'm still confused Brad - maybe we should take this off line. The code sample you pointed to uses CALLB not a CALLP. Besides, there is no connection between specifying ExtProc and whether or not parms have to be passed. I frequently use subprocedures to "wrap" APIs because IBM's idea of a sensible parameter sequence rarely matches mine <g>, that plus Option(*NoPass) gives me more than enough flexibility. Certainly more than CALLB can offer. What am I missing ? +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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-2025 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
