In this post I will show you how to trace an application engine process using the Process Definitions without setting the trace in the Process Scheduler’s psprcs.cfg configuration file.
Navigate to the process definition of the application engine that you would like to trace (PeopleTools > Process Scheduler > Processes). Go to the Overrride Options tab, and from the Parameter List drop down select Append, and in the edit box next to it add the following line:
This will trace SQLs inside of your application engine as well as peoplecode. Save the process definition and go ahead and run your program. To examine the trace files, just navigate to the process monitor, click details on your process, then View Log/Trace.
-TRACE output goes into Application Engine Trace (.AET)
-TOOLSTRACEPC output goes into the PeopleTools trace file (.trc)
Title | Under | Posted on |
---|---|---|
Component interface Error: no rows exist for the specified keys | PeopleSoft Technical | 03/15/2019 - 3:54am |
ADD 24 months starting from current month.(peoplesoft) | PeopleSoft Functional | 07/29/2018 - 8:44pm |
TRC values dropdown | PeopleSoft Technical | 04/04/2018 - 12:54am |
how to find missing sequence in GRID and print the mising sequence number while saving through peoplecode | PeopleSoft Technical | 09/11/2017 - 4:49am |
Comments
Hello Compshack! It is very helpful. what is -TOOLSTRACEPC and 4044 in trace options?
-TOOLSTRACEPC is to trace the PeopleCode inside of your application engine. The 4044 is a bit number and you set that depending on what you want to trace. PeopleSoft recommends setting this to 4044.
The following is a list of the Trace values and what they do and 4044 is combination of set of values from below.
1 Initiates the Application Engine step trace.
2 Initiates the Application Engine SQL trace.
4 Initiates the trace for dedicated Temp Table Allocation to AET file.
8 not yet allocated
16 not yet allocated
32 not yet allocated
64 not yet allocated
128 Initiates the statement timings trace to file, which is similar to the COBOL timings trace to file.
256 Initiates the PeopleCode Detail to the file for the Timings trace.
512 not yet allocated
1024 Initiates the statement timings trace, but, instead of writing to the trace file, this trace stores the results in the following tables: PS_BAT_TIMINGS_LOG and PS_BAT_TIMINGS_DTL.
2048 Adding this value requests a database optimizer trace file.
4096 Requests a database optimizer to be inserted in the Explain Plan Table of the current database.
8192 This value sets a trace for Integration Broker transform programs.
Give back to the community and help it grow!
* Help with unanswered forum questions and issues
* Register or login to share your knowledge at your own blog
Hi, just curious if you know what would create the .trc file if tracing is NOT turned on by psprcs.cfg or by adding to the parameters field. We are running an AE, and it's creating a .trc file with "PeopleTools(8.44.06) AE SQL/PeopleCode Trace" heading. Regards.
Hi there,
Did you check trace flags on the psappsrv.cfg file? That might be what is triggering your online trace!
Give back to the community and help it grow!
* Help with unanswered forum questions and issues
* Register or login to share your knowledge at your own blog
Is there any reason why the trace won't get generated if I schedule the process but it gets generated when I run it manually?
it shouldn't - is the scheduled process has the same process definition?
Give back to the community and help it grow!
* Help with unanswered forum questions and issues
* Register or login to share your knowledge at your own blog
Can some attached the document how to run application engine throught frontend...............
Beautiful article..
Thanks a lot..
Regards,
Vikas Bhardwaj
thanks a lot
Hi,
Please share the above doc,
Anyone knows how to apply this to a PS TASK ?
I have a task with 3 app engines and I dont know which is at fault ?
You mean PS Job? Anywho, you need to apply it to each AE. You can't trace a task or PS Job.
Give back to the community and help it grow!
* Help with unanswered forum questions and issues
* Register or login to share your knowledge at your own blog
Thanks for all the above comments it looks so nice....
I am having a issue... when i run a process with admin id like security admin it shows me three out put file View Log/Trace
as for example .AET, .stdout and .trc but when i am trying to run the same process with another id, i am not getting the .trc file. i have changed as per the article
PeopleTools > Process Scheduler > Processes). Go to the Overrride Options tab, and from the Parameter List drop down select Append, and in the edit box next to it add the following line:
-TRACE 7 -TOOLSTRACEPC 4044. But still i cant find the .trc file. I would like to know if there is any setting missing from permission list or any where. Thanks in advance for your help
i tried
-Trace 0 -TOOLSTRACEPC 0 -TOOLSTRACESQL 0
put it still generate thae trace, how can i disable it?
yo utilizo este:
-TRACE 7 -TOOLSTRACEPC 3596 -TOOLSTRACESQL 31
not bad