Вы находитесь на странице: 1из 16

Application Engine Tracing

Understand Application Engine
Enable Application Engine Tracing

Different ways to trace an Application

1. Process Scheduler
2. Command Prompt
3. Application Designer (2-Tier mode)

Command Line options

The command line option is available for Microsoft
Windows NT and UNIX, but it is not available when
calling Application Engine programs from
To enable tracing from the command line, specify
the TRACE option within the command line that
you submit to PSAE.EXE. For example,
n:\pt840\bin\client\winx86\psae.exe -CT MICROSFT

Command Line Options

Specify the type of database to which you are
connecting. Values are ORACLE, MICROSFT, SYBASE,
Required for Sybase and Informix. For platforms that
require a server name as part of sign-on, enter the
appropriate server name. This affects Sybase,
Informix, and Microsoft SQL Server. However, for
Microsoft SQL Server, this option is valid but not
Enter the name of the database to which the program
will connect.

Enter the user ID of the person who is
running the program.
Enter the password associated with the
specified user ID.
Enter the run control ID to use for this run of
the program.
Specify the Application Engine program to

Required for restart. Enter the process
instance for the program run. The default is
0, which means PeopleSoft Application
Engine uses the next available process
This parameter controls the Debug utility.
Enter Y to indicate that you want the
program to run in debugging mode, or enter
N to indicate that you do not.
This parameter controls restart disabling.
Enter Y to disable restart, or enter N to

To enable tracing from the command line,
enter this parameter and a specific trace
value. The value you enter is the sum of the
specific traces that you want to enable.
Traces and values are:
0: Disables tracing.
1: Initiates the Application Engine step
2: Initiates the Application Engine SQL trace.
4: Initiates the trace for dedicated
temporary table allocation to an Application
Engine trace (AET) file. You can trace how
the system allocates, locks, and releases
temporary tables during program runs.

128: Initiates the Application Engine timings file trace, which

is similar to the COBOL timings trace.
256: Includes the PeopleCode detail timings in the 128 trace.
1024: Initiates the Application Engine timings table trace,
which stores the results in database tables.
2048: Initiates the database optimizer explain, writing the
results to the trace file. This option is supported only on
Oracle, Informix, and Microsoft SQL Server.
4096: Initiates the database optimizer explain, storing the
results in the Explain Plan table of the current database. This
option is supported only on Oracle, DB2, and Microsoft SQL
For example, to enable the 1, 2, and 128 traces, you would enter
131,the sum of 1, 2, and 128. To indicate that you do not want any
traces, enter 0. If you dont explicitly enter 0,PeopleSoft Application
Engine uses the trace value set in PeopleSoft Configuration Manager.

To disable %UpdateStats meta-SQL
construct, enter 1.
Enable the SQL trace.
Enable the PeopleCode trace.

Through Process Scheduler

People Tools - Process Scheduler - Processes

Select the Application Engine Program. Go To Overrides Tab

Go to the specific Run Control Page and run the App

Engine program

In the process monitor go to Details tab --- View Log/Trace, the trace file generated can be Viewed

Statement Timing Trace

This trace enables you to gather performance
information to determine program bottlenecks.
The statement timings trace can be used for tuning
an Application Engine program.
Can Identify at which areas your App Engine is not
working as efficiently as it has to be. For instance, if
compile counts are high, you can reduce the numbers
by using the PeopleSoft Application Engine reuse
feature. If inserts appear to be running slow and you
have many of them, you can increase the
performance by using the PeopleSoft Application
Engine bulk insert feature. Each value in the trace,
including cumulative totals, appears in a form
rounded to the nearest tenth of a second, but totals
are calculated using nonrounded timings.

You can write this trace to a file, or you can write

the results to tables
The statement timings trace populates the
following tables.

This table stores general information for a

program run.

This table stores details associated with a

program run, such as the execute count, fetch
time, and so on.

This table stores PeopleCode detail timings