|
I feel better - I KNEW there was a way to do this ON the iSeries. There are Management Central APIs, documented on the Performance topic in InfoCenter. These will start, cycle, and stop Colleciton Services. CRTPFRDTA can be used against the data generated. It's not made too easy, however. The thing I'm interested in is the sites that don't have Performance Tools. Of course, I'm not supposed to WANT to work on the green screen anymore, am I? At 04:33 PM 3/18/02 -0500, you wrote: >I think that STRPFRTRC is only for collecting trace data, which was a >component of Performance data. Actual Performance collection is done >through Ops Nav. > > As for why your job runs only 3 seconds, have you run a Convert >performance data since V5R1, if not run CVTPFRDTA (on your performance >data libs - check QMPGDATA & QPFRDATA).. > > As for PM/400, best way to see what's happening is to run GO PM400, >and select option 6. It will tell you if its active, and the release of >the data. > > Pete Massiello > >Vernon Hamberg wrote: > >>At 02:47 PM 3/18/02 -0500, you wrote: >> >>>Reading up for the install of V5R1, I have the following questions: >> >>-snip- >> >>>3) STRPFRMON, ENDPFRMON, STRPFRCOL, ENDPFRCOL, are no longer supported. >>> We are to use the collection services in Operations Navigator >>> instead. What if I have PM400 and it is started automatically in >>> QSTRUP in it's own subsystem? Also, there is an autostart job >>> in subsystem QCTL, job description QPFRCOL. This job description >>> does a CALL QSYS/QPMLWAIT. This job only runs for 3 seconds after >>> an IPL. What exactly is _it_ doing? >> >> >>The command is now STRPFRTRC/ENDPFRTRC >> >>>-- >>>-Jeff >>> >>>The opinions expressed are my own and not necessarily >>>the opinion of my company. Unless I say so. >>> >>>_______________________________________________ >>>This is the Midrange Systems Technical Discussion (MIDRANGE-L) >>>mailing list >>>To post a message email: MIDRANGE-L@midrange.com >>>To subscribe, unsubscribe, or change list options, >>>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >>>or email: MIDRANGE-L-request@midrange.com >>>Before posting, please take a moment to review the archives >>>at http://archive.midrange.com/midrange-l. >> >> >>_______________________________________________ >>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing >>list >>To post a message email: MIDRANGE-L@midrange.com >>To subscribe, unsubscribe, or change list options, >>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >>or email: MIDRANGE-L-request@midrange.com >>Before posting, please take a moment to review the archives >>at http://archive.midrange.com/midrange-l. >> >> >>. > > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-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.
midrange.com
