An application engine program can be traced by simply changing the trace parameters in the process scheduler configuration file, however, that requires the process scheduler to be brought down and it will trace every application engine ran through the process scheduler. However, you can append those trace parameters to the process definition and it will trace the individual process. Navigate to the process definition (Home>PeopleTools>Process Scheduler>Processes –> Override Options) in the parameter list select append and enter in -TRACE xxx -TOOLSTRACEPC xxx -TOOLSTRACESQL xxx, where xxx is the bit reference based on the needs of the trace. So for example if you wanted options 1, 2, and 128 for trace, you add 1+2+128 = 131, and you enter 131 as the trace parameter: -TRACE 131.
|Initiates the Application Engine step trace.
|Initiates the Application Engine SQL trace.
|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.
|Initiates the statement timings trace to a file, which is similar to the COBOL timings trace to a file.
|Initiates the PeopleCode detail to the file for the timings trace.
|Initiates the statement timings trace, but stores the results in the PS_BAT_TIMINGS_LOG and PS_BAT_TIMINGS_DTL tables.
|Requests a database optimizer trace file.
|Requests a database optimizer to be inserted in the Explain Plan table of the current database.
|Sets a trace for PeopleSoft Integration Broker transform programs.
|Trace Evaluator instructions
|List Evaluator program
|Show assignments to variables
|Show fetched values
|Trace start of programs
|Trace external function calls
|Trace internal function calls
|Show parameter values
|Show function return value
|Trace each statement in program
|SQL statement variables
|SQL connect, disconnect, commit and rollback
|Row Fetch (indicates that it occurred, not data)
|All other API calls except ssb
|Set Select Buffers (identifies the attributes of columns to be selected)
|Database API specific calls
|COBOL statement timings
|Sybase Bind information
|Sybase Fetch information
|SQL Informational Trace
Note that output from the -TRACE flag goes to the application engine trace (.AET) file. Output from the -TOOLSTRACEPC and -TOOLSTRACESQL output goes to the PeopleTools trace file (.TRC).