2388 lines
88 KiB
HTML
2388 lines
88 KiB
HTML
|
|
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<title>Add PEX Definition (ADDPEXDFN)</title>
|
|
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
|
|
</head>
|
|
<body bgcolor="white">
|
|
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<a name="ADDPEXDFN.Top_Of_Page"></a>
|
|
<h2>Add PEX Definition (ADDPEXDFN)</h2>
|
|
<table width="100%">
|
|
<tr>
|
|
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
|
|
<b>Threadsafe: </b>Conditional
|
|
</td>
|
|
<td valign="top" align="right">
|
|
<a href="#ADDPEXDFN.PARAMETERS.TABLE">Parameters</a><br>
|
|
<a href="#ADDPEXDFN.COMMAND.EXAMPLES">Examples</a><br>
|
|
<a href="#ADDPEXDFN.ERROR.MESSAGES">Error messages</a></td>
|
|
</tr>
|
|
</table>
|
|
|
|
<div> <a name="ADDPEXDFN"></a>
|
|
<p>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.
|
|
</p>
|
|
<p>Additional information about the Performance Explorer tool can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p><b>Restrictions:</b>
|
|
</p>
|
|
<ol>
|
|
<li>This command is shipped with public *EXCLUDE authority.
|
|
</li>
|
|
<li>You must have *EXECUTE authority to the library of each program specified on the PGM parameter.
|
|
</li>
|
|
<li>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.
|
|
</li>
|
|
<li>The following user profiles have private authorities to use the command:
|
|
<ul>
|
|
<li>QPGMR
|
|
</li>
|
|
<li>QSRV
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>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.
|
|
</li>
|
|
</ol>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
|
|
<div>
|
|
<h3><a name="ADDPEXDFN.PARAMETERS.TABLE">Parameters</a></h3>
|
|
<table border="1" cellpadding="4" cellspacing="0">
|
|
<!-- col1="10" col2="15" col3="30" col4="10" -->
|
|
<tr>
|
|
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
|
|
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
|
|
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
|
|
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.DFN"><b>DFN</b></a></td>
|
|
<td valign="top">Definition</td>
|
|
<td valign="top"><i>Name</i></td>
|
|
<td valign="top">Required, Positional 1</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.TYPE"><b>TYPE</b></a></td>
|
|
<td valign="top">Type</td>
|
|
<td valign="top"><b><u>*STATS</u></b>, *TRACE, *PROFILE</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.PRFTYPE"><b>PRFTYPE</b></a></td>
|
|
<td valign="top">Profile type</td>
|
|
<td valign="top"><b><u>*PGM</u></b>, *JOB</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="6"><a href="#ADDPEXDFN.JOB"><b>JOB</b></a></td>
|
|
<td valign="top">Jobs</td>
|
|
<td valign="top">Single values: <b><u>*</u></b>, *NONE<br>Other values (up to 8 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="6">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Job name</td>
|
|
<td valign="top">
|
|
<i>Qualified job name</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Qualifier 1: Job name</td>
|
|
<td valign="top"><i>Generic name, name</i>, <b><u>*ALL</u></b></td>
|
|
</tr><tr>
|
|
<td valign="top" style="padding-left:10pt">Qualifier 2: User</td>
|
|
<td valign="top"><i>Generic name, name</i>, <b><u>*ALL</u></b></td>
|
|
</tr><tr>
|
|
<td valign="top" style="padding-left:10pt">Qualifier 3: Number</td>
|
|
<td valign="top">000001-999999, <b><u>*ALL</u></b></td>
|
|
</tr><tr>
|
|
<td valign="top">Element 2: Thread identifier</td>
|
|
<td valign="top">
|
|
Single values: <b><u>*ALL</u></b>, *SELECT<br>Other values (up to 20 repetitions): 00000001-FFFFFFFF, *INITIAL</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.TASK"><b>TASK</b></a></td>
|
|
<td valign="top">Task name</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b>, *ALL<br>Other values (up to 8 repetitions): <i>Generic name, name</i></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="8"><a href="#ADDPEXDFN.PGM"><b>PGM</b></a></td>
|
|
<td valign="top">Program to monitor</td>
|
|
<td valign="top">Values (up to 16 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="8">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Program</td>
|
|
<td valign="top">
|
|
<i>Qualified object name</i></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" style="padding-left:10pt">Qualifier 1: Program</td>
|
|
<td valign="top"><i>Name</i>, *ALL</td>
|
|
</tr><tr>
|
|
<td valign="top" style="padding-left:10pt">Qualifier 2: Library</td>
|
|
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b></td>
|
|
</tr><tr>
|
|
<td valign="top">Element 2: Module</td>
|
|
<td valign="top">
|
|
<i>Name</i>, <b><u>*ALL</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Procedure</td>
|
|
<td valign="top">
|
|
<i>Character value</i>, <b><u>*ALL</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 4: Type</td>
|
|
<td valign="top">
|
|
<b><u>*PGM</u></b>, *SRVPGM</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 5: Pane size</td>
|
|
<td valign="top">
|
|
<b><u>4</u></b>, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.DTAORG"><b>DTAORG</b></a></td>
|
|
<td valign="top">Data organization</td>
|
|
<td valign="top"><b><u>*FLAT</u></b>, *HIER</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.MAXSTG"><b>MAXSTG</b></a></td>
|
|
<td valign="top">Maximum storage to use</td>
|
|
<td valign="top">1024-4000000, <b><u>10000</u></b></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.TRCFULL"><b>TRCFULL</b></a></td>
|
|
<td valign="top">Trace full</td>
|
|
<td valign="top"><b><u>*STOPTRC</u></b>, *WRAP</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.MRGJOB"><b>MRGJOB</b></a></td>
|
|
<td valign="top">Merge job data</td>
|
|
<td valign="top"><b><u>*YES</u></b>, *NO</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.ADDTHDOPT"><b>ADDTHDOPT</b></a></td>
|
|
<td valign="top">Add threads/tasks option</td>
|
|
<td valign="top"><b><u>*ALL</u></b>, *NEW, *CURRENT</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.LSTALLJOB"><b>LSTALLJOB</b></a></td>
|
|
<td valign="top">List all jobs/tasks</td>
|
|
<td valign="top"><b><u>*NO</u></b>, *YES</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="3"><a href="#ADDPEXDFN.INTERVAL"><b>INTERVAL</b></a></td>
|
|
<td valign="top">Sampling interval</td>
|
|
<td valign="top"><i>Element list</i></td>
|
|
<td valign="top" rowspan="3">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Milliseconds</td>
|
|
<td valign="top">
|
|
0.1-200.0, <b><u>*NONE</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Randomize</td>
|
|
<td valign="top">
|
|
<b><u>*FIXED</u></b>, *VARY</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.PGMBKTEVT"><b>PGMBKTEVT</b></a></td>
|
|
<td valign="top">Program bracketing events</td>
|
|
<td valign="top">Single values: <b><u>*DFT</u></b><br>Other values (up to 3 repetitions): *MISTREND, *MIENTRYEXIT, *JVA, *PRC</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.TRCTYPE"><b>TRCTYPE</b></a></td>
|
|
<td valign="top">Trace type</td>
|
|
<td valign="top">Single values: *SLTEVT<br>Other values (up to 12 repetitions): <b><u>*CALLRTN</u></b>, *BASIC, *DSKIO1, *DSKIO2, *DSKSVR, *DSKSTG, *VRTADR, *PGMACT, *FILEOPEN, *PRFDTA, *TASKSWT, *HEAP</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.SLTEVT"><b>SLTEVT</b></a></td>
|
|
<td valign="top">Specific events</td>
|
|
<td valign="top"><b><u>*NO</u></b>, *YES</td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.MCHINST"><b>MCHINST</b></a></td>
|
|
<td valign="top">Machine instructions</td>
|
|
<td valign="top">Single values: <b><u>*ALL</u></b>, *NONE<br>Other values (up to 50 repetitions): <i>Character value</i></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.BASEVT"><b>BASEVT</b></a></td>
|
|
<td valign="top">Base events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 27 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *PRCCRT, *PRCDLT, *TASKCRT, *TASKDLT, *TASKSWTIN, *TASKSWTOUT, *TASKSWTOUTQ, *TASKSWTOUTINT, *TASKAVAIL, *PMCO, *PGMDBG, *ACTGRPACTPGM, *ACTGRPCRT, *ACTGRPDLT, *EXCP, *MIEXCP, *DCRINTSTR, *DCRINTEND, *CPUVRYON, *CPUVRYOFF, *CPUSWTIN, *CPUSWTOUTY, *CPUSWTOUTP, *CPUAVAIL, *SETPRF, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="3"><a href="#ADDPEXDFN.PGMEVT"><b>PGMEVT</b></a></td>
|
|
<td valign="top">Program events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 16 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="3">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *MIENTRY, *MIEXIT, *MISTR, *MIEND, *MIPRECALL, *MIPOSTCALL, *JVAENTRY, *JVAEXIT, *JVAPRECALL, *JVAPOSTCALL, *PRCENTRY, *PRCEXIT, *PASEPRCENTRY, *PASEPRCEXIT</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.STGEVT"><b>STGEVT</b></a></td>
|
|
<td valign="top">Storage events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 13 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *CRTSEG, *DLTSEG, *EXDSEG, *FNDSEGSIZ, *TRUNCSEG, *SYSHEAP, *RESHEAP, *LCLHEAP, *USRHEAP, *ACTGRPHEAP, *HDLHEAP, *CLEHEAP, *STGPTC, *TSADRFALSETRAP, *SPCADRFALSETRAP, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.DSKEVT"><b>DSKEVT</b></a></td>
|
|
<td valign="top">Disk events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 14 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *ALLSTR, *READSTR, *READEND, *WRTSTR, *WRTEND, *PGREADSTR, *PGREADEND, *PGWRTSTR, *PGWRTEND, *RMTWRTSTR, *RMTWRTEND, *RMTPGWRTSTR, *RMTPGWRTEND, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.FAULTEVT"><b>FAULTEVT</b></a></td>
|
|
<td valign="top">Fault events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 4 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *STR, *ENDOK, *ENDERR, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.JOBEVT"><b>JOBEVT</b></a></td>
|
|
<td valign="top">Job events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 10 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *LWSTR, *LWEND, *INELIGIBLE, *ACTIVE, *INTERRUPT, *MPLPOOLCHG, *TOBCHMPLPOOL, *TSLEND, *MPLLEAVE, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.LCKEVT"><b>LCKEVT</b></a></td>
|
|
<td valign="top">Lock events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 2 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *LWEND, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.SAREVT"><b>SAREVT</b></a></td>
|
|
<td valign="top">SAR events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 18 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *ALLSTR, *CLR, *CLRPIN, *EXCHCLR, *READ, *READASYNC, *READASYNCCALL, *READPIN, *EXCHREAD, *EXCHREADASYNC, *WRT, *WRTASYNC, *WRTRMV, *WRTPGOUT, *RMV, *UNPINRMV, *ENDOK, *ENDERR, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.DSKSVREVT"><b>DSKSVREVT</b></a></td>
|
|
<td valign="top">Disk server events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 11 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *CTLEND, *RQSACP, *RQSRJT, *SVRTASKSTR, *SVRTASKEND, *RQSRCV, *RQSENDOK, *RQSENDERR, *TAPSNDCMD, *TAPDONE, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.OSEVT"><b>OSEVT</b></a></td>
|
|
<td valign="top">Operating System events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 54 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *DBIO, *DBOPEN, *DBSVRCNN, *DBSVRREQ, *DIRSRV, *DTAARA, *DTAQ, *HOSTSVRCNN, *IFSCOMP, *IFSIO, *IFSOPEN, *MIEV8, *MGTC, *TRCCOMP, *TRCDTA, *USRTNS, *SAVRST, *ADDTHD1, *MIEV24, *MIEV25, *MIEV26, *MIEV27, *MIEV28, *MIEV29, *MIEV30, *MIEV35, *MIEV36, *MIEV37, *MIEV38, *MIEV39, *MIEV40, *MIEV41, *MIEV42, *MIEV43, *MIEV44, *MIEV45, *MIEV46, *MIEV47, *MIEV48, *MIEV49, *MIEV50, *MIEV51, *MIEV52, *MIEV53, *MIEV54, *MIEV55, *MIEV56, *MIEV57, *MIEV58, *MIEV59, *MIEV60, *MIEV61, *MIEV62</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.JVAEVT"><b>JVAEVT</b></a></td>
|
|
<td valign="top">Java events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 20 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *OBJCRT, *GBGCOL, *GBGCOLSWEEP, *THDCRT, *THDDLT, *THDWAIT, *THDNFY, *THDNFYALL, *CLSLOAD, *CLSUNLOAD, *LIBOPR, *TFMSTR, *LCKSTR, *UNLCK, *JVAEXCP, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.CMNEVT"><b>CMNEVT</b></a></td>
|
|
<td valign="top">Communications events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 6 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *SOCKETSAPI, *SOCKETS, *IP, *TCP, *TCPIN, *TCPOUT, *UDP, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.APPEVT"><b>APPEVT</b></a></td>
|
|
<td valign="top">Application events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 7 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *DOMTRCDTA, *WAS, *CONNECT, *APPEVT1, *APPEVT2, *APPEVT3, *APPEVT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.PASEEVT"><b>PASEEVT</b></a></td>
|
|
<td valign="top">PASE events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 22 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *SYSCALLSTR, *SYSCALLEND, *FORKPARENTSTR, *FORKCHILDSTR, *FORKEND, *PRCINITSTR, *PRCINITEND, *EXECSTR, *EXECEND, *EXIT, *THDINITSTR, *THDINITEND, *THDEND, *LOADSTR, *LOADEND, *UNLOADSTR, *UNLOADEND, *SIGPRCSND, *SIGTHDSND, *SIGRCV, *TRCHOOK, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.SYNCEVT"><b>SYNCEVT</b></a></td>
|
|
<td valign="top">Synchronization events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 13 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *CONDSET, *CONDWAIT, *HDLMTXRLS, *HDLMTXWAIT, *PTRMTXLOCK, *PTRMTXUNLOCK, *PTRSEMPOST, *PTRSEMWAIT, *NAMSEMPOST, *NAMSEMWAIT, *TKNLOCK, *TKNUNLOCK, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.JRNEVT"><b>JRNEVT</b></a></td>
|
|
<td valign="top">Journal events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 10 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *STRCOMMIT, *ENDCOMMIT, *STROBJFORCE, *ENDOBJFORCE, *STRROLLBACK, *ENDROLLBACK, *STRCYCLE, *STREVAL, *ENDEVAL, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.FILSVREVT"><b>FILSVREVT</b></a></td>
|
|
<td valign="top">File server events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 9 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *IFSBSF, *IFSDIR, *IFSLFS, *LIC, *NETSVR, *NFS, *OS, *VNODMGMT, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.EXPCCHEVT"><b>EXPCCHEVT</b></a></td>
|
|
<td valign="top">Expert cache events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 3 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *TUNE, *TUNEDB, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.DBEVT"><b>DBEVT</b></a></td>
|
|
<td valign="top">Database events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 9 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top" rowspan="4"><a href="#ADDPEXDFN.RSCAFNEVT"><b>RSCAFNEVT</b></a></td>
|
|
<td valign="top">Resources affinity events</td>
|
|
<td valign="top">Single values: <b><u>*NONE</u></b><br>Other values (up to 9 repetitions): <i>Element list</i></td>
|
|
<td valign="top" rowspan="4">Optional</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 1: Event identifier</td>
|
|
<td valign="top">
|
|
*ALL, *CHGTASK, *CHGGRP, *CHGCFG, *BALCFG, *CHKBAL, *VFYBAL, *ANZBAL, *CHGBALSTT, *SERVICE</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 2: Event counter</td>
|
|
<td valign="top">
|
|
<b><u>*NONE</u></b>, 1, 2, 3, 4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top">Element 3: Event format</td>
|
|
<td valign="top">
|
|
<b><u>*FORMAT1</u></b>, *FORMAT2, *FORMAT3, *FORMAT4</td>
|
|
</tr>
|
|
<tr>
|
|
<td valign="top"><a href="#ADDPEXDFN.TEXT"><b>TEXT</b></a></td>
|
|
<td valign="top">Text 'description'</td>
|
|
<td valign="top"><i>Character value</i>, <b><u>*BLANK</u></b></td>
|
|
<td valign="top">Optional</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
</div>
|
|
<div> <a name="ADDPEXDFN.DFN"></a>
|
|
<h3>Definition (DFN)</h3>
|
|
<p>Specifies the name of the Performance Explorer definition being added. If the specified definition already exists in the QAPEXDFN file in library QUSRSYS, an error condition will occur. The user can either change the definition name or remove the existing definition using the Remove Performance Explorer Definition (RMVPEXDFN) command, and try this command again.
|
|
</p>
|
|
<p>This is a required parameter.
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>definition-name</i></b></dt>
|
|
<dd>Specify the name of the new Performance Explorer definition.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.TYPE"></a>
|
|
<h3>Type (TYPE)</h3>
|
|
<p>Specifies the type of performance data to be collected.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*STATS</u></b></dt>
|
|
<dd>General performance program statistics are collected to help identify problem areas. This mode is mainly used as a map to help determine if and where more detailed information should be collected and analyzed.
|
|
<p>In addition to collecting the information specified above, TYPE(*STATS) also provides the option of counting the occurrences of specific types of events. These can be counted in any of 4 counters provided.
|
|
</p>
|
|
<p>To count the occurrences of a particular type of event, specify SLTEVT(*YES) and then choose the event-identifier(s) to be counted from the various event categories.
|
|
</p>
|
|
<p>For example, TYPE(*STATS) SLTEVT(*YES) JOBEVT((*ALL 1)) would count all job events in counter 1.
|
|
</p>
|
|
</dd>
|
|
<dt><b>*TRACE</b></dt>
|
|
<dd>Detailed trace information is collected. This is the most detailed type of performance data collection available.
|
|
</dd>
|
|
<dt><b>*PROFILE</b></dt>
|
|
<dd>Specific programs are sampled to identify sections of code that are using larger amounts of resources. This information is very valuable when the user wants to improve the performance of a specific program or application.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.PRFTYPE"></a>
|
|
<h3>Profile type (PRFTYPE)</h3>
|
|
<p>Specifies the type of profile to collect. This parameter is only valid if TYPE(*PROFILE) is specified.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*PGM</u></b></dt>
|
|
<dd>Specific programs are sampled to identify sections of code that are using larger amounts of resources. This information is very valuable when the user wants to improve the performance of a specific program or application.
|
|
</dd>
|
|
<dt><b>*JOB</b></dt>
|
|
<dd>Specific jobs are sampled to identify programs and procedures that are using larger amounts of resources. This mode can provide a view of all the programs and procedures in the entire system, and is equivalent to *TRACE mode of *PMCO events with a specified interval.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.JOB"></a>
|
|
<h3>Job name (JOB)</h3>
|
|
<p>Specifies which jobs are included in the Performance Explorer data collection session.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*</u></b></dt>
|
|
<dd>Only the job that issues the STRPEX (Start Performance Explorer) command is included. All threads for that job are included.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All jobs on the system are included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Job name</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b></b></dt>
|
|
<dd>
|
|
<p><b>Qualifier 1: Job name</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>job-name</i></b></dt>
|
|
<dd>Specify the name of the job to be included in the Performance Explorer data collection session.
|
|
</dd>
|
|
<dt><b><i>generic*-job-name</i></b></dt>
|
|
<dd>Specify the generic name of the job to be included. A generic name is a character string of one or more characters followed by an asterisk (*); for example, ABC*. The asterisk substitutes for any valid characters. A generic name specifies all objects with names that begin with the generic prefix for which the user has authority. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete object name. For more information about generic object names, see the i5/OS objects topic under Programming->CL in the iSeries Information Center at the Web site: http://www.ibm.com/eserver/iseries/infocenter
|
|
</dd>
|
|
</dl>
|
|
</dd>
|
|
<dt><b></b></dt>
|
|
<dd>
|
|
<p><b>Qualifier 2: User</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ALL</u></b></dt>
|
|
<dd>All jobs that match the specified job name are included.
|
|
</dd>
|
|
<dt><b><i>user-name</i></b></dt>
|
|
<dd>Specify the name of the user of the job to be included.
|
|
</dd>
|
|
<dt><b><i>generic*-user-name</i></b></dt>
|
|
<dd>Specify the generic user name of the jobs to be included.
|
|
</dd>
|
|
</dl>
|
|
</dd>
|
|
<dt><b></b></dt>
|
|
<dd>
|
|
<p><b>Qualifier 3: Number</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ALL</u></b></dt>
|
|
<dd>All jobs that match the specified job name and user name are included.
|
|
</dd>
|
|
<dt><b><i>job-number</i></b></dt>
|
|
<dd>Specify the job number to further qualify the job name and user name.
|
|
</dd>
|
|
</dl>
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Thread identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ALL</u></b></dt>
|
|
<dd>All threads of the specified job are included.
|
|
</dd>
|
|
<dt><b>*INITIAL</b></dt>
|
|
<dd>Only the initial thread of the specified job is included.
|
|
</dd>
|
|
<dt><b>*SELECT</b></dt>
|
|
<dd>Select the threads from a list of threads for the specified job. This value is only valid if the command is run in an interactive job.
|
|
</dd>
|
|
<dt><b><i>thread-identifier</i></b></dt>
|
|
<dd>Specify the thread identifier of the job to be included. This is the thread ID as shown by the WRKJOB command.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.TASK"></a>
|
|
<h3>Task name (TASK)</h3>
|
|
<p>Specifies which licensed internal code (LIC) tasks are included in the Performance Explorer data collection session. Up to 8 task names may be specified.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>LIC tasks can be obtained from the Performance Tools reports and WRKSYSACT command. There is no guarantee that LIC task names will remain the same or exist from system to system or release to release.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No LIC tasks on the system are included.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All LIC tasks on the system are included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Other values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>task-name</i></b></dt>
|
|
<dd>Specify the name of the task to be included in the Performance Explorer data collection session.
|
|
</dd>
|
|
<dt><b><i>generic*-task-name</i></b></dt>
|
|
<dd>Specify the generic name of the task to be included. A generic name is a character string of one or more characters followed by an asterisk (*); for example, ABC*. The asterisk substitutes for any valid characters. A generic name specifies all objects with names that begin with the generic prefix for which the user has authority. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete object name.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.PGM"></a>
|
|
<h3>Program to monitor (PGM)</h3>
|
|
<p>Specifies the program whose performance profile data is collected. This parameter is only valid if TYPE(*PROFILE) is specified. Up to 16 programs may be specified.
|
|
</p>
|
|
<p><b>Element 1: Program</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b></b></dt>
|
|
<dd>
|
|
<p><b>Qualifier 1: Program</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>program-name</i></b></dt>
|
|
<dd>Specify the name of the program to be sampled.
|
|
</dd>
|
|
</dl>
|
|
</dd>
|
|
<dt><b></b></dt>
|
|
<dd>
|
|
<p><b>Qualifier 2: Library</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*LIBL</u></b></dt>
|
|
<dd>The library list of the job that issues the STRPEX command is searched to find the specified program or service program.
|
|
</dd>
|
|
<dt><b><i>library-name</i></b></dt>
|
|
<dd>Specify the library which contains the program or service program.
|
|
</dd>
|
|
</dl>
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Module</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ALL</u></b></dt>
|
|
<dd>All modules in the program or service program will be sampled. If sampling an OPM (Original Program Model) program, specify *ALL for this element.
|
|
</dd>
|
|
<dt><b><i>module-name</i></b></dt>
|
|
<dd>Specify the name of the module within the program or service program that is to be sampled.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Procedure</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ALL</u></b></dt>
|
|
<dd>All procedures in the specified module are sampled.
|
|
</dd>
|
|
<dt><b><i>'procedure-name'</i></b></dt>
|
|
<dd>Specify the name of a procedure within the specified module that is to be sampled. Specify the procedure name within single quotes if the procedure name contains lower case characters.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 4: Type</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*PGM</u></b></dt>
|
|
<dd>The program being specified is a program (*PGM) object.
|
|
</dd>
|
|
<dt><b>*SRVPGM</b></dt>
|
|
<dd>The program being specified is a service program (*SRVPGM) object.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 5: Pane size</b>
|
|
</p>
|
|
<p>The pane size is the number of consecutive program instruction addresses assigned to each counter. The smaller the pane size, the more fine-grained the program profile information will be.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>4</u></b></dt>
|
|
<dd>The default pane size is 4.
|
|
</dd>
|
|
<dt><b><i>number</i></b></dt>
|
|
<dd>Specify the pane size to use for the program. Valid values are 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.DTAORG"></a>
|
|
<h3>Data organization (DTAORG)</h3>
|
|
<p>Specifies how the data is organized.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if TYPE(*STATS) is specified.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FLAT</u></b></dt>
|
|
<dd>The Performance Explorer tool will not collect data for a parent-child relationship.
|
|
</dd>
|
|
<dt><b>*HIER</b></dt>
|
|
<dd>The Performance Explorer tool will collect data for a parent-child relationship.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.MAXSTG"></a>
|
|
<h3>Maximum storage to use (MAXSTG)</h3>
|
|
<p>Specifies the maximum amount of storage, in kilobytes (K), that the Performance Explorer tool uses for collecting trace data.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if TYPE(*TRACE) is specified.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>10000</u></b></dt>
|
|
<dd>Up to 10000 kilobytes of storage is used.
|
|
</dd>
|
|
<dt><b><i>maximum-K-bytes</i></b></dt>
|
|
<dd>Specifies the requested maximum amount of storage, in kilobytes (K), to use for the collected trace records. The system calculates the minimum amount of storage that is necessary for the trace. This minimum storage size calculation depends on the system's processor configuration. The minimum amount of storage may be significantly larger than the size specified on the MAXSTG parameter. The system uses the larger of the two values.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.TRCFULL"></a>
|
|
<h3>Trace full (TRCFULL)</h3>
|
|
<p>Specifies whether the trace records wrap (replace oldest records with new records) or whether the trace stops when all of the storage specified by the MAXSTG parameter has been used.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if TYPE(*TRACE) is specified.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*STOPTRC</u></b></dt>
|
|
<dd>Tracing stops when the trace file is full of trace records.
|
|
</dd>
|
|
<dt><b>*WRAP</b></dt>
|
|
<dd>When the trace file is full, the trace wraps to the beginning. The oldest trace records are written over by new ones as they are collected.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.MRGJOB"></a>
|
|
<h3>Merge job data (MRGJOB)</h3>
|
|
<p>Specifies whether the data from different jobs should be merged together or kept separate.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if DTAORG(*FLAT) is specified.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*YES</u></b></dt>
|
|
<dd>The data from individual jobs is merged.
|
|
</dd>
|
|
<dt><b>*NO</b></dt>
|
|
<dd>The data from individual jobs is kept separate.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.ADDTHDOPT"></a>
|
|
<h3>Add threads/tasks option (ADDTHDOPT)</h3>
|
|
<p>Specifies what types of threads and tasks should be included in the Performance Explorer session based on the creation time of the threads and tasks relative to the start time of the Performance Explorer session.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ALL</u></b></dt>
|
|
<dd>The collection will include all threads and tasks that satisfy the criteria specified by the JOB and TASK parameters.
|
|
</dd>
|
|
<dt><b>*NEW</b></dt>
|
|
<dd>The collection will include only new threads and tasks that satisfy the criteria specified by the JOB and TASK parameters and are created after the Performance Explorer session is started. Any threads or tasks that are active at the time the Performance Explorer session is started will not be included.
|
|
</dd>
|
|
<dt><b>*CURRENT</b></dt>
|
|
<dd>The collection will include only threads and tasks that satisfy the criteria specified by the JOB and TASK parameters and are active at the time the Performance Explorer session is started. Any threads or tasks created after the start of the Performance Explorer session will not be included.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.LSTALLJOB"></a>
|
|
<h3>List all jobs/tasks (LSTALLJOB)</h3>
|
|
<p>Specifies whether summary data should be listed for all jobs and tasks in the system, or only those jobs and tasks specified on the JOB or TASK parameter.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NO</u></b></dt>
|
|
<dd>Data for a job or task is listed in the task information file only if that job or task is specified on the JOB or TASK parameter.
|
|
</dd>
|
|
<dt><b>*YES</b></dt>
|
|
<dd>Data for all jobs and tasks is listed in the task information file, even if the job or task is not specified on the JOB or TASK parameter.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.INTERVAL"></a>
|
|
<h3>Sampling interval (INTERVAL)</h3>
|
|
<p>Specifies the interval at which samples are taken of the program. A small interval will cause a high number of samples to be taken, and will also cause higher overhead. The smaller the sampling interval, the larger the amount of trace data collected.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is valid only when TYPE(*PROFILE) or TYPE(*TRACE) is specified.
|
|
</p>
|
|
<p><b>Element 1: Milliseconds</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>Interval is not used.
|
|
</dd>
|
|
<dt><b><i>0.1-200.0</i></b></dt>
|
|
<dd>Specify the interval at which samples of the program are taken. Valid values range from 0.1 to 200.0 milliseconds.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Randomize</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FIXED</u></b></dt>
|
|
<dd>The sampling interval will always be the value specified for element 1 of this parameter.
|
|
</dd>
|
|
<dt><b>*VARY</b></dt>
|
|
<dd>The sampling interval will be approximately the value specified for element 1 of this parameter. The specified interval will be changed each time by adding or subtracting a small random percentage of the interval. This may be necessary to eliminate harmonics when the set of threads/tasks in a collection have settled into a steady state sequence of machine cycles that do not vary in order or length during the collection.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.PGMBKTEVT"></a>
|
|
<h3>Program bracketing events (PGMBKTEVT)</h3>
|
|
<p>Specifies which program call flow events are included in the TYPE(*STATS) definition.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if TYPE(*STATS) is specified.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*DFT</u></b></dt>
|
|
<dd>Statistics are to be collected on *MISTREND events, and *MIENTRYEXIT events for programs and service programs created or changed to enable performance collection, and *JVA events for Java programs created or changed to enable performance collection.
|
|
</dd>
|
|
<dt><b>*MISTREND</b></dt>
|
|
<dd>Statistics are to be collected on all machine instructions.
|
|
</dd>
|
|
<dt><b>*MIENTRYEXIT</b></dt>
|
|
<dd>Statistics are to be collected on programs and procedures that have been explicitly enabled with the ENBPFRCOL parameter on the various compile and change program commands. For example, CRTCMOD ENBPFRCOL(*FULL *ALLPRC).
|
|
</dd>
|
|
<dt><b>*JVA</b></dt>
|
|
<dd>Statistics are to be collected on Java methods that have been explicitly enabled with the ENBPFRCOL parameter (or its equivalent) on the Java and JIT compile commands. For example, CRTJVAPGM ENBPFRCOL(*FULL).
|
|
</dd>
|
|
<dt><b>*PRC</b></dt>
|
|
<dd>Statistics are to be collected on programs and procedures that have been implicitly enabled. This includes any program that has been compiled at optimization level 30 or below. Optimization level 40 programs require explicit compiler options which activate the Trace Job (TRCJOB) style hooks. For example, CHGPGM LICOPT('CallTracingAtHighOpt'). Note that this works only for procedures that stack a frame on the invocation stack when called (non-leaf procedures). *MIENTRYEXIT and *PRC are mutually exclusive.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.TRCTYPE"></a>
|
|
<h3>Trace type (TRCTYPE)</h3>
|
|
<p>Specifies what type of trace performance data to be collected. Additional information about the TRCTYPE options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if TYPE(*TRACE) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b>*SLTEVT</b></dt>
|
|
<dd>Only selected individual events (xxxEVT parameters) and machine instructions (MCHINST parameter) are included in the trace definition.
|
|
<p>
|
|
<b>Note: </b>If TRCTYPE(*SLTEVT) is specified, SLTEVT(*YES) must also be specified.
|
|
</p>
|
|
</dd>
|
|
</dl>
|
|
<p><b>Other values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*CALLRTN</u></b></dt>
|
|
<dd>Specifies that call return events are included in the trace definition. Call return events occur when a program is entered and exited as well as when certain machine instructions are started and completed.
|
|
</dd>
|
|
<dt><b>*BASIC</b></dt>
|
|
<dd>Specifies that events relative to general performance analysis are included in the trace definition. This option should be used when it is unclear as to what type of performance problem determination is necessary.
|
|
</dd>
|
|
<dt><b>*DSKIO1</b></dt>
|
|
<dd>Specifies that events associated with disk input/output operations are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*DSKIO2</b></dt>
|
|
<dd>Specifies that events associated with disk input/output operations plus higher level requests to do input/output operations are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*DSKSVR</b></dt>
|
|
<dd>Specifies that events associated with disk server operations are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*DSKSTG</b></dt>
|
|
<dd>Specifies that events associated with disk storage consumption are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*VRTADR</b></dt>
|
|
<dd>Specifies that events associated with virtual address assignment are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*PGMACT</b></dt>
|
|
<dd>Specifies that events associated with program activations and deactivations are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*FILEOPEN</b></dt>
|
|
<dd>Specifies that events associated with file (*FILE) opens are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*PRFDTA</b></dt>
|
|
<dd>Specifies that events associated CPU instruction profiling are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*TASKSWT</b></dt>
|
|
<dd>Specifies that events associated with tasking are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*HEAP</b></dt>
|
|
<dd>Specifies that events associated with heap storage are included in the trace definition.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.SLTEVT"></a>
|
|
<h3>Specific events (SLTEVT)</h3>
|
|
<p>For trace mode (TYPE(*TRACE)) collections, SLTEVT allows individual machine instructions and events to be specified in addition to the categories of events available with the TRCTYPE parameter. For statistics mode (TYPE(*STATS)) collections, SLTEVT allows individual events to be counted.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if TYPE(*TRACE) or TYPE(*STATS) is specified.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NO</u></b></dt>
|
|
<dd>Do not allow selection of specific events.
|
|
</dd>
|
|
<dt><b>*YES</b></dt>
|
|
<dd>Allow selection of specific events.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.MCHINST"></a>
|
|
<h3>Machine instructions (MCHINST)</h3>
|
|
<p>Specifies which machine instructions are included in the Performance Explorer data collection session. Use this parameter in conjunction with the PGMEVT parameter. MCHINST controls which of the possible machine instructions are to be included in the collection. PGMEVT(*MISTR and *MIEND) controls whether any machine instructions are included in the collection.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if TYPE(*TRACE) and SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*ALL</u></b></dt>
|
|
<dd>All machine instructions that are available for collection are included.
|
|
</dd>
|
|
<dt><b>*NONE</b></dt>
|
|
<dd>No machine instructions available for collection are included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Other values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>machine-instruction-name</i></b></dt>
|
|
<dd>Specify the name of the machine instruction to be included in the Performance Explorer data collection session.
|
|
<p>
|
|
<b>Note: </b>Specifying machine instructions should be done only under the direction of your iSeries service representative.
|
|
</p>
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.BASEVT"></a>
|
|
<h3>Base events (BASEVT)</h3>
|
|
<p>Specifies which base events are included in the definition. Additional information about the BASEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No base events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All base events are included in the trace mode definition, or counted in the statistics mode definition. If TYPE(*STATS), you can specify which event-identifiers are to be counted. Some of the base event event-identifiers cannot be counted. An informational message will be shown if a definition attempts to count all base events.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the base event identifier to be traced or counted.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No base events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events. Values other than *FORMAT1 are valid for only the *PMCO and *SWOQ events. For all other events, *FORMAT1 will be used regardless of what format is specified.
|
|
</p>
|
|
<p>*FORMAT2 for the *PMCO event will collect the same data as *FORMAT1 plus an additional 16 levels of the call stack. *FORMAT3 for the *PMCO event will collect the same data as *FORMAT1 plus 4 additional PMC registers.
|
|
</p>
|
|
<p>*FORMAT2 for the *SWOQ event will collect the same data as *FORMAT1 plus an additional 16 levels of the call stack.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.PGMEVT"></a>
|
|
<h3>Program events (PGMEVT)</h3>
|
|
<p>Specifies which program call flow events are included in the trace definition. Additional information about the PGMEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if TYPE(*TRACE) and SLTEVT(*YES) are specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No program call flow events are included in the trace definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All program call flow events are included in the trace definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the call flow event identifier to be included in the trace definition.
|
|
<p>For the *MIENTRY and *MIEXIT events, programs and procedures must be explicitly enabled with the ENBPFRCOL parameter on the various compile and change program commands. For example, CRTCMOD ENBPFRCOL(*FULL *ALLPRC).
|
|
</p>
|
|
<p>For the *JVAxxx events, the Java methods must be explicitly enabled via the ENBPFRCOL parameter (or its equivalents) on the Java and JIT compile commands. For example, CRTJVAPGM ENBPFRCOL(*FULL).
|
|
</p>
|
|
<p>For the *PRCENTRY and *PRCEXIT events, procedures are implicitly enabled in programs that have been compiled at optimization level 30 or below. Optimization level 40 programs require explicit compiler options which activate these trace job (trcjob) style hooks. For example, CHGPGM LICOPT('CallTracingAtHighOpt'). Note that this works only for procedures that stack a frame on the invocation stack when called (non-leaf procedures).
|
|
</p>
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.STGEVT"></a>
|
|
<h3>Storage events (STGEVT)</h3>
|
|
<p>Specifies which auxiliary storage management events are included in the definition. Additional information about the STGEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No auxiliary storage management events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All auxiliary storage management events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the auxiliary storage management event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No auxiliary storage management events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.DSKEVT"></a>
|
|
<h3>Disk events (DSKEVT)</h3>
|
|
<p>Specifies which disk events are included in the definition. Additional information about the DSKEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No disk events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All disk events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b>*ALLSTR</b></dt>
|
|
<dd>All disk start events are traced, if TYPE(*TRACE), or counted, if TYPE(*STATS).
|
|
</dd>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the disk event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No disk events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.FAULTEVT"></a>
|
|
<h3>Fault events (FAULTEVT)</h3>
|
|
<p>Specifies which page fault events are included in the definition. Additional information about the FAULTEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No page fault events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All page fault events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the page fault event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No page fault events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.JOBEVT"></a>
|
|
<h3>Job events (JOBEVT)</h3>
|
|
<p>Specifies which job or process related events are included in the definition. Additional information about the JOBEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No job or process related events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All job or process related events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the job or process related event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No job or process related events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.LCKEVT"></a>
|
|
<h3>Lock events (LCKEVT)</h3>
|
|
<p>Specifies which lock or seize events are included in the definition. Additional information about the LCKEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No lock or seize events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All lock or seize events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the lock or seize event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No lock or seize events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.SAREVT"></a>
|
|
<h3>SAR events (SAREVT)</h3>
|
|
<p>Specifies which segment address register events are included in the definition. Additional information about the SAREVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No segment address register events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All segment address register events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the segment address register event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No segment address register events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.DSKSVREVT"></a>
|
|
<h3>Disk server events (DSKSVREVT)</h3>
|
|
<p>Specifies which disk server events are included in the definition. Additional information about the DSKSVREVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No disk server events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All disk server events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the disk server event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No disk server events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.OSEVT"></a>
|
|
<h3>Operating System events (OSEVT)</h3>
|
|
<p>Specifies which operating system events are included in the definition. Additional information about the OSEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No operating system events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All operating system events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the operating system event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No operating system events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.JVAEVT"></a>
|
|
<h3>Java events (JVAEVT)</h3>
|
|
<p>Specifies which Java events are included in the definition. Additional information about the JVAEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No Java events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All Java events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the Java event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No Java events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<p>*FORMAT2 for the *OBJCRT, *LCKSTR, and *UNLCK events will collect the same data as *FORMAT1 plus an additional 16 levels of the call stack.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.CMNEVT"></a>
|
|
<h3>Communications events (CMNEVT)</h3>
|
|
<p>Specifies which communications events are included in the definition. Additional information about the CMNEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No communications events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All communications events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the communications event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No communications events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events. Values other than *FORMAT1 are valid for only the *SOCKETS events. For all other events, *FORMAT1 will be used regardless of what format is specified.
|
|
</p>
|
|
<p>*FORMAT2 for the *SOCKETS event will collect the same data as *FORMAT1 except the application data contains 128 bytes of data instead of 64.
|
|
</p>
|
|
<p>*FORMAT3 for the *SOCKETS event will collect the same data as *FORMAT1 except the application data contains 256 bytes of data instead of 64.
|
|
</p>
|
|
<p>*FORMAT4 for the *SOCKETS event will collect the same data as *FORMAT1 except the application data contains 500 bytes of data instead of 64.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.APPEVT"></a>
|
|
<h3>Application events (APPEVT)</h3>
|
|
<p>Specifies which application events are included in the definition. Additional information about the APPEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No application events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All application events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the application event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No application events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.PASEEVT"></a>
|
|
<h3>PASE events (PASEEVT)</h3>
|
|
<p>Specifies which Portable Application Solution Environment (PASE) events are included in the definition. Additional information about the PASEEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No PASE events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All PASE events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the PASE event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No PASE events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.SYNCEVT"></a>
|
|
<h3>Synchronization events (SYNCEVT)</h3>
|
|
<p>Specifies which synchronization events are included in the definition. Additional information about the SYNCEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No synchronization events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All synchronization events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the synchronization event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No synchronization events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.JRNEVT"></a>
|
|
<h3>Journal events (JRNEVT)</h3>
|
|
<p>Specifies which journal events are included in the definition. Additional information about the JRNEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No journal events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All journal events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the journal event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No journal events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.FILSVREVT"></a>
|
|
<h3>File server events (FILSVREVT)</h3>
|
|
<p>Specifies which iSeries NetServer, File Server and Network File System Server and Client events are included in the definition. Additional information about the FILSVREVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No iSeries NetServer, File Server and Network File System Server and Client events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All iSeries NetServer, File Server and Network File System Server and Client events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the iSeries NetServer, File Server and Network File System Server and Client event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No iSeries NetServer, File Server and Network File System Server and Client events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.EXPCCHEVT"></a>
|
|
<h3>Expert cache events (EXPCCHEVT)</h3>
|
|
<p>Specifies which expert cache events are included in the definition. Additional information about the EXPCCHEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No expert cache events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All expert cache events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the expert cache event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No expert cache events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.DBEVT"></a>
|
|
<h3>Database events (DBEVT)</h3>
|
|
<p>Specifies which database events are included in the definition. Additional information about the DBEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No database events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All database events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the affinity event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No affinity events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.RSCAFNEVT"></a>
|
|
<h3>Resources affinity events (RSCAFNEVT)</h3>
|
|
<p>Specifies which resources affinity events are included in the definition. Additional information about the RSCAFNEVT options can be found in the Performance Management information at http://www.ibm.com/servers/eserver/iseries/perfmgmt/resource.htm.
|
|
</p>
|
|
<p>
|
|
<b>Note: </b>This parameter is only valid if SLTEVT(*YES) is specified.
|
|
</p>
|
|
<p><b>Single values</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No resources affinity events are included in the definition.
|
|
</dd>
|
|
<dt><b>*ALL</b></dt>
|
|
<dd>All affinity events are included in the trace mode definition, or counted in the statistics mode definition.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 1: Event identifier</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><i>event-identifier</i></b></dt>
|
|
<dd>Specify the affinity event identifier to be included.
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 2: Event counter</b>
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*NONE</u></b></dt>
|
|
<dd>No affinity events are counted.
|
|
</dd>
|
|
<dt><b><i>event-counter</i></b></dt>
|
|
<dd>If TYPE(*STATS), events can be counted in one of four counters (1,2,3 or 4). The event counter value is ignored if TYPE(*TRACE).
|
|
</dd>
|
|
</dl>
|
|
<p><b>Element 3: Event format</b>
|
|
</p>
|
|
<p>The event format describes what data is collected for this event. *FORMAT1 provides the data used for most data analysis. The other formats allow for collection of other data related to these events.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*FORMAT1</u></b></dt>
|
|
<dd>The first event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT2</b></dt>
|
|
<dd>The second event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT3</b></dt>
|
|
<dd>The third event format is used to collect data for this event.
|
|
</dd>
|
|
<dt><b>*FORMAT4</b></dt>
|
|
<dd>The fourth event format is used to collect data for this event.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<div> <a name="ADDPEXDFN.TEXT"></a>
|
|
<h3>Text 'description' (TEXT)</h3>
|
|
<p>Specifies the text that briefly describes the Performance Explorer definition.
|
|
</p>
|
|
<dl>
|
|
<dt><b><u>*BLANK</u></b></dt>
|
|
<dd>Text is not specified.
|
|
</dd>
|
|
<dt><b><i>'description'</i></b></dt>
|
|
<dd>Specify no more than 50 characters of text, enclosed in apostrophes.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
<div><h3><a name="ADDPEXDFN.COMMAND.EXAMPLES">Examples</a> </h3>
|
|
<p><b>Example 1: Using TYPE(*TRACE)</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPEXDFN DFN(TEST1) TYPE(*TRACE) JOB(*) MAXSTG(5000)
|
|
</pre>
|
|
</p>
|
|
<p>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.
|
|
</p>
|
|
<p><b>Example 2: Using TYPE(*PROFILE)</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPEXDFN DFN(TEST2) TYPE(*PROFILE)
|
|
PGM((MYLIB/MYSRVPGM1 *ALL *ALL *SRVPGM))
|
|
</pre>
|
|
</p>
|
|
<p>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.
|
|
</p>
|
|
<p><b>Example 3: Using TYPE(*TRACE)</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPEXDFN DFN(TEST3) TYPE(*TRACE) JOB(*ALL)
|
|
TRCTYPE(*CALLRTN *DSKIO1)
|
|
TEXT('Trace definition example')
|
|
</pre>
|
|
</p>
|
|
<p>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.
|
|
</p>
|
|
<p><b>Example 4: Counting SAR Events</b>
|
|
</p>
|
|
<p>
|
|
<pre>
|
|
ADDPEXDFN DFN(TEST4) TYPE(*STATS) SLTEVT(*YES)
|
|
SAREVT((*ALL 1))
|
|
TEXT('Count all SARs in counter 1')
|
|
</pre>
|
|
</p>
|
|
<p>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.
|
|
</p>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
<hr size="2" width="100%">
|
|
<div><h3><a name="ADDPEXDFN.ERROR.MESSAGES">Error messages</a> </h3>
|
|
<p><b><u>*ESCAPE Messages</u></b>
|
|
</p>
|
|
<dl>
|
|
<dt><b>CPFAF10</b></dt>
|
|
<dd>Definition or filter already exists.
|
|
</dd>
|
|
</dl>
|
|
</div>
|
|
<table width="100%">
|
|
<tr><td align="right"><a href="#ADDPEXDFN.Top_Of_Page">Top</a></td></tr>
|
|
</table>
|
|
</body>
|
|
</html>
|