|
From: <Gene_Gaunt@xxxxxxxxxxxxxxx> > So I conclude the internal QTEMP libraries are still same object > architecture in machine context on V5R2 as before; however, IBM has now > blocked MATCTX and RSLVSP from coughing up QTEMP pointers. > > Why? If I can use simple CL break message handling programs to peak into > another job's QTEMP library, then what is so blazingly bad with using QTEMP > pointers in MI? > As I said, a botched attempt to increase security. It doesn't really, but just adds grief.
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.