If you are not running Collection Services or your collection
objects are not current, you can start Collection Services in any
of these ways to analyze the IBM® i operating environment.
- Use the Collection Services function that is available
in System i® Navigator.
- Use either the Start Collector (QYPSSTRC) API or the Start Performance
Collection (STRPFRCOL) command. If you do not use the Management Central
function in System
i Navigator,
you can manage your collections with either of the following methods:
- Performance
Management APIs . These
APIs start, end, and cycle collections, and change and retrieve system
parameters for the data collected.
- Performance collection commands: STRPFRCOL, End Performance Collection
(ENDPFRCOL), Configure Performance Collection (CFGPFRCOL), and Check
Performance Collection (CHKPRFCOL). These commands start, end, and
cycle collections for the data collected.
- If you have the Performance Tools licensed program (PT1) installed,
use Option 2 from the Performance Tools main menu. Refer to Performance Tools for iSeries
for additional information
about collecting performance data with this option.
- Activate IBM Performance
Management for IBM System i, which automates the start
of Collection Services and then creates the database files during
collection.
Ensure that Collection Services has been configured
to collect the data you require, and that it runs long enough to
accurately represent your operating environment.
The following
example uses the Collector APIs.
- Run Collection Services for at least one or two days, and
make sure that peak and off-peak workloads are represented. Type this
command:
CALL PGM(QYPSSTRC) PARM('*PFR ' '*STANDARDP' X'00000000')
This
command starts Collection Services and uses the Standard plus protocol for
the collection profile. Once you start Collection Services with this
command, it will collect performance data and store it in the collection
object until you either explicitly stop it or restart the system.
(If collection was run for more than one day, more than one collection
object will be produced.) This profile collects all the data categories
typically needed by the tools in IBM Performance
Tools for i, including communications
protocol data. The default configuration also starts a batch job CRTPFRDTA,
which creates the performance database files.
- Collection Services stores the data in an object type of
*MGTCOL.
You can convert this object into performance
database files for later analysis. To retain the object for future
use, you can save the objects to tape or to a save file (SAVF). Collection
Services can delete collection objects from the system at any time
after the retention period has expired. The default retention period
is 24 hours. If you do not want Collection Services to delete your
collection objects for you, change your retention period to permanent
(set a retention period of *PERM) as shown in the example that follows.
Note: The following command example shows the shipped default values
with the exception of the retention period value. A retention period
of *PERM requires a value of 0. Furthermore, you must make this change
before or during the data collection. The change does not affect any
collection objects that are already cycled.
To change
the retention period by using the Change Collection Services Attributes
API, type the following command:
CALL PGM(QYPSCSCA) PARM('*PFR ' /* collection */
X'00000384' /* interval 900 sec */
'QPFRDATA ' /* library */
X'00000000' /* retention period is permanent */
X'00000000' /* cycle time 00:00:00 */
X'00000018' /* cycle interval 24Hrs */
X'00000001' /* start CRTPFRDTA */
'*STANDARDP' /* default profile */
X'00000000') /* return code */
- If you want to explicitly stop the collector after the
data that you want is obtained, type this command:
CALL PGM(QYPSENDC) PARM('*PFR ' X'00000000')