|
I have a few times used a small MI pgm accepting from 1 to 50 parms - I am not sure whether that will do what you want. If I want to look at program QABCDEF then I would rename that to QABCDEFX, rename my little MI program to QABCDEF, and see what happened. You can use STRDBG to look at the number of parms and each parm value. Obviously you might have to be careful with renaming some critical programs in QSYS, and you must also remember to rename it back again... If you want I shal be happy to share this simple MI source with you. 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 iPerformance@xxxxxxx introduction at www.giapa.com ! Tel +45 5835 3305 Fax +45 5835 3308 Get detailed performance data for www.iPerformance.dk all jobs using only 0.2 pct. CPU ============================================================== -----Original Message----- From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx] On Behalf Of Bobby Hicks Sent: Thursday, October 14, 2004 1:47 PM To: mi400@xxxxxxxxxxxx Subject: [MI400] (no subject) Is there an easy way to determine the parameters on a system state program? Or monitor the program as it gets called to see w hat gets passed? Thanks in advance for any help that you can give me. Bobby. _______________________________________________ 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.