|
Rohn, In pre ile rpg this is doable by an mi pgm. Walk the pgm call stack, find your pgm, get the ptr to static storage of the pgm, ... In ile, you could read the compiled pgm spooled file, get the names of each pgm variable, put the pgm in debug, then use the QTERTVPV api to rtv the value of each variable. Steve Richter ---------- Original Message ---------------------------------- From: Rohn.Blake@helpsystems.com Reply-To: MI400@midrange.com Date: Wed, 8 Aug 2001 16:49:11 -0500 > >...for what seems like (believe it or not) a simpler design approach, I >want to save all the values of all the variables in my RPG to a user >space/index. And later... on future calls to the program I want to retrieve >those values and repopulate all the variables (including variables which >are field names from database files - repositioning the files for READE is >not necessary, unless equally simple). *INLR will likely not be set on >between calls, if it makes a difference. > > >It seems to me like this should be quite doable and quite simply done... >just grab that portion of "memory" and stash it away. > > >Any thoughts or advice on direction? > >Thanks! >Rohn > >+--- >| This is the MI Programmers Mailing List! >| To submit a new message, send your mail to MI400@midrange.com. >| To subscribe to this list send email to MI400-SUB@midrange.com. >| To unsubscribe from this list send email to MI400-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: dr2@cssas400.com >+--- > +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.com +---
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.