Locating Trace Files
Locating a generated trace file depends on how you invoked the program and the operating system on which the program runs. This table describes trace file locations based on where the program initiated:
|
Location Where the Program Was Initiated |
Trace File Location |
|---|---|
|
Microsoft Windows workstation |
Look for the trace file in %TEMP%\PS\<db name>. |
|
PeopleCode |
Look for the trace file in %TEMP%\PS\db_name on Microsoft Windows NT and inPS_CFG_HOME/log/\<db name> on UNIX and Linux systems. |
|
Command line |
Look for the trace file in the directory specified in the Log/Output field in the PS_SERVER_CFG file. |
|
PeopleSoft Process Scheduler |
Look for the trace file in a subdirectory of the directory specified in the Log/Output field in the PS_SERVER_CFG file. |
The Application Engine names the trace files according to the following naming convention:
When a program includes a process instance, the trace file name is AE_Program_name_Process_Instance_Date/Time_Stamp.AET. For example, AE_AEMINITEST_99_0506050320.AET.
When a program does not include a process instance, the trace file name is AE_Date/Time_Stamp_OS_PID.AET.
When Application Engine is run online, the trace file name is OprID_Hostname_Date/Time_Stamp.AET. For example, PTDMO_SLC00FCJ_0507230158.AET.
The date and time stamp is in the format <month><day><hour><minute><second>, with two values for each date element and no punctuation between the elements. For example, August 12 at 5:09 p.m. and 30 seconds would be 0812170930.
Note: For an Application Engine program running on a server, PeopleTools writes the generic PeopleTools trace for SQL and PeopleCode trace files to the same directories as the AET traces. The prefix of the trace file name is also the same, and the suffix is trc. On a Windows workstation, the system writes the trace to the file specified in thePeople Tools Trace File field on the Trace tab of PeopleSoft Configuration Manager.