|
"An object" - do you mean "any object". All objects has something in common but most secrets depends on object type. Any object is stored in a 'space object' - you can see this via the DMPSYSOBJ command (context = library for normal use). An example of this is my utility-command to find "which qry uses file xyz" (http://hkrebs.dk/fndstrsyso.html). Many program objects still contains the symbol table used when compiling. This is how a source debugger (with help from stand alone or imbedded source) can find the memory location where the named fields content is stored and the attributes of the field. See http://hkrebs.dk/rtvpgmflda.html Henrik Krebs http://hkrebs.dk >Does anybody know if it's possible to view the internals of a program object >via an outfile? For instance, to gain access to the variables used in a >program? Similar to a dspffd to get access to the fields defined in a file? >Is this wizard stuff via MI programming? Or is Rochester about to create a >command to RTVPGMVAR? > It must be a technique used by source debuggers to get access to variable >names. >Thanks >Mike Pantzopoulos +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.