|
I wonder if you could get around the binder's problem with a 2-stage method: have your service pgm do an external call to another pgm, passing the same parms, which in turn calls the procedure in the OS/400 service pgm. --Dave On Wednesday 28 January 2004 10:01, Gene_Gaunt@xxxxxxxxxxxxxxx wrote: > We have some sourceless software, and we're trying to determine the > parameters it sends to a particular OS/400 service program procedure API. > > We tried creating a little preemptive C service program with one exportable > procedure of the same name to put high in the library list, and have it > call the real OS/400 service program procedure API. That way we could > inspect the parameter values at run time. > > However the binder gives error "Definition supplied multiple times" when we > create the service program. The same procedure name is both the "callee" > and "caller". Does someone know a way to intercept and inspect the > parameter values to OS/400 service program procedure API?
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.