I would like to briefly describe some of the PeopleSoft debugging techniques that I have used and found invaluable during development batch and online programs.
SQR Debugging
| Flag | Description |
| -S | Choose Append Option on Parameter List of Process Definition. All of your SQL statements – simple and clear + execution counts |
| –debug(flag) | Choose Append Option on Parameter List of Process Definition. Put the following statements in your code
#debug(flag) show this will allow you to display definitions in your log. What is most useful this allows you to specify different levels of tracing using the flag – which can be letters A-Z. Specifying –debug(A-Z) on process definition it allows you to selectively display your debug statements. |
COBOL Debugging
| Flag | Description |
|
Choose Override Option on Parameter List of Process Definition. Copy and paste Flags and run your process normally. You will see the trace file in the Process Monitor |
App Engine Debugging
| Flag | Description |
| -TRACE 131 | Choose Append Option on Parameter List of Process Definition.
Required to start the app engine trace. Does not display much more than message log |
| -TRACE 131
-TOOLSTRACEPC 2048 |
Choose Append Option on Parameter List of Process Definition.
Adding TOOLSTRACEPC with a number causes detailed PeopleCode code trace – be careful those can get very large and significantly impact performance. |
| -TRACE 131
-TOOLSTRACESQL 31 |
Choose Append Option on Parameter List of Process Definition.
Adding TOOLSTRACESQL with a number causes detailed SQL trace. This option should always be used when tracing – app engine are all about SQL. |
App engine can also be debugged on the client. In order to do this you need to configure trace setting in the configuration manager:
Open App Engine program in the Application Designer, press the Run Program icon and enter the Run Control ID and Process Instance Number (You should have an existing process instance and run control id defined online). Click ‘OK’ to run the App Engine process in two-tier mode.
If you would like to read about debugging in more details here is an excellent overview presentation by Kai Markowitz from CSU:
http://www.scribd.com/doc/15756180/Tracing-Debugging-in-People-Tools-84x-CMS411
Oracle PeopleTools Blog
I think this guy that wrote this article, needs to *debug* HIMSELF.
Sharon,
I appreciate all the comments – can you please elaborate – if you have something to contribute or you have any suggestions I would love to hear them. One thing I really appreciate if someone can do better than me especially contribute to the rest of us please let me know.