|
Peter, As Walden points out, "if you get a pointer to a memory location, you can modify it". I actually use this technique in some of my software. In one (batch NEP) job, I create a user space in that job's QTEMP, retrieve the pointer to that user space (using QUSPTRUS) and put the retrieved pointer into a different 'control' user space in a separate library. Now a program in a separate job can get to the control user space (because it's in a normal non-QTEMP library), retrieve the pointer and thus get at the data in the userspace in the QTEMP of the other job. There's not even any MI - just plain ol' RPGLE... I haven't tried putting a pointer to dynamically allocated memory into a user space, but it would probably work... I'll tinker and see :-) Mind you, I wouldn't recommend it - it's a real pain to debug :-) Rory
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.