|
Gene, Not 100 % sure since I haven't tested it, but this might work: Use good old TRCJOB *ON within system service tools. The resulting trace will amongst others show open and close. I believe the trace goes down on module level - therefore check which module is opening the file name in question. Since the trace listing can get enormous you may want to let the trace job write the results to and *OUTFILE and use queries or a small program to locate what you want. Regards, Kaare -------------------------------------------------------------- Kaare Plesner Optimizing OS/400 Applications iPerformance ApS with "No cure - no pay" guarantee Skraenten 6B Dk-4220 Korsoer Visit our new performance product <mailto:iPerformance@xxxxxxx> iPerformance@xxxxxxx introduction at <http://www.giapa.com/> www.giapa.com ! Tel +45 5835 3305 Fax +45 5835 3308 Get detailed performance data for <http://www.iPerformance.dk> www.iPerformance.dk all jobs using only 0.2 pct. CPU ============================================================== -----Original Message----- From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx] On Behalf Of Gene_Gaunt@xxxxxxxxxxxxxxx Sent: Thursday, May 26, 2005 7:05 PM To: mi400@xxxxxxxxxxxx Subject: [MI400] OIR reference *FILE in *PGM? Hey there MI/OIR gurus: With only the program object (no source), how can I tell *which* module in a multi-module bound ILE program used a particular file? _______________________________________________ This is the MI Programming on the AS400 / iSeries (MI400) mailing list To post a message email: MI400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mi400 or email: MI400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/mi400.
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.