|
My personal favorite to read a user space is to retrieve a pointer to the user space using the QUSPTRUS api. Then I can base a datastructure on that pointer. When I want to read the next group of data, I simply add the number to the pointer. Quite fast. The alternative is reading the user space directly with the QUSRTVUS api. QUSPTRUS is cleaner code, and performs better. If IBM decided to drop the ADD op code or the + sign in an eval statement and decided that you needed to call an api passing it 4 parameters: factor 1, factor 2, result, error data structure; would that make you upset? That's about how pointless QUSRTVUS is once you understand how simple QUSPTRUS is. The only applicable use of QUSRTVUS over QUSPTRUS is if you are a software vendor and your user space is not in QTEMP. Because if your customer modifies system value QALWUSRDMN you cannot retrieve a pointer to a user space that is in a library that is not in the user domain, but is in the system domain. Rob Berendt
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.