CL Command Reference - ADDPEXDFN
CL Command List > ADDPEXDFN Reference
Description:
The Add Performance Explorer Definition (ADDPEXDFN) command adds a new Performance Explorer definition to the system. Each definition is stored as a member in the QAPEXDFN file in library QUSRSYS. A Performance Explorer definition identifies the performance data that is to be collected during a Performance Explorer session. A session can be started using the STRPEX (Start Performance Explorer) command. When starting a new session, a Performance Explorer definition name must be provided.
Restrictions:
1. This command is shipped with public *EXCLUDE authority.
2. You must have *EXECUTE authority to the library of each program specified on the PGM parameter.
3. To use this command you must have *SERVICE special authority, or be authorized to the Service Trace function of i5/OS through iSeries Navigator¡¯s Application Administration support. The Change Function Usage Information (QSYCHFUI) API, with a function ID of QIBM_SERVICE_TRACE, can also be used to change the list of users that are allowed to perform trace operations.
4. The following user profiles have private authorities to use the command:
. QPGMR
. QSRV5
5. Two threads within the same job will not be allowed to run ADDPEXDFN at the same time. The thread that issued ADDPEXDFN first will run the command to completion while the second ADDPEXDFN waits.
Examples:
Example 1: Using TYPE(*TRACE)
ADDPEXDFN DFN(TEST1) TYPE(*TRACE) JOB(*) MAXSTG(5000)
This command adds a new performance definition named TEST1, which will result in a member named TEST1 being added to file QAPEXDFN in library QUSRSYS. When this definition is used to start a performance explorer session (STRPEX command), detailed trace information will be collected for the job that invoked the STRPEX command. A maximum of 5000 kilobytes of trace data will be collected. When the trace record storage area is full no more trace records will be collected.
Example 2: Using TYPE(*PROFILE)
ADDPEXDFN DFN(TEST2) TYPE(*PROFILE)
PGM((MYLIB/MYSRVPGM1 *ALL *ALL *SRVPGM))
This command adds a new performance explorer definition named TEST2. When this definition is used to start a performance explorer session (STRPEX command), performance profile information for service program MYSRVPGM1 in library MYLIB will be collected.
Example 3: Using TYPE(*TRACE)
ADDPEXDFN DFN(TEST3) TYPE(*TRACE) JOB(*ALL)
TRCTYPE(*CALLRTN *DSKIO1)
TEXT(¡¯Trace definition example¡¯)
This command adds a new performance explorer definition named TEST3. When this definition is used to start a performance explorer session (STRPEX command), performance trace information for program call/return and disk input/output operation will be collected.
Example 4: Counting SAR Events
ADDPEXDFN DFN(TEST4) TYPE(*STATS) SLTEVT(*YES)
SAREVT((*ALL 1))
TEXT(¡¯Count all SARs in counter 1¡¯)
This command adds a new performance explorer definition named TEST4. When this definition is used to start a session (STRPEX command), performance statistics for program and procedure call/return operations will be collected. In addition, all segment address register (SAR) events that occur will be counted in counter 1.