|
a data area is actually a type of space, just like a user space is. In MI you set a space pointer to a user space by running two instructions: RSLVSP /* resolve system pointer to user space */ SETSPPFP /* set a space pointer from system pointer */ At a low enough security level ( 30 ), you can set a space pointer to a data area using the same two instructions. The only difference is that the data in the data area space starts at offset 96 ( guessing ). So performance should be the same. -Steve -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Carlos Kozuszko Sent: Saturday, August 30, 2003 7:51 AM To: rpg400 (E-mail) Subject: USRSPC vs. Local data Are there any access speed differences processing data from a user space compared with local data ? D Rcd1 S 82 DIM(300) D Rcd2 S 82 DIM(300) BASED(pRcd2) // Pointer to a userspace Lets say i want to load 300 records in an array and sort it, sorting Rcd2 would be slower than Rcd1 ? Im considering storing the data in a userspace, becouse there are chances that the same dataset (300 records per dataset) need to be reprocessed again, storing a userspace in qtemp by each recordset would avoid to re-read and sort the records. What im really wondering is if the access to the data stored in a user space is a plain memory access just like accesing any other variable, if so, i think my new approach is better that the current one. Any thoughts ? Carlos Kozuszko _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.