Tracing & Debugging in People Tools 8.4x CMS411

Student Administration
Tracing & Debugging in

PeopleTools 8.4x
Kai Markowitz
Technical Lead
** This presentation has notes, don’t just view/print the slides **
April 2007
Agenda
 Introduction
 PeopleTools 8.4x Changes
 Tracing SQL & PeopleCode
 Tracing SQR Programs
 Tracing Cobol Programs
 Tracing App Engine Programs
 PeopleCode Debugging
 Questions
2
Agenda
 Introduction
 Questions
3
Agenda
 Introduction
 Questions
4
PeopleTools 8.4x Changes
 No more pstools.exe on the local client!

– CS 8.9 can’t be run in two-tier mode.
 No tracing/debugging in two-tier mode.
– App Engine programs are the only exception
to this.
 Trace files are on the application server.
– Examining the trace files requires access to
the Unix server.
5
Agenda
 Introduction
 Questions
6
Tracing SQL & PeopleCode
 These are very

good trace
settings to use
in order to get a
very “light” but
useful trace.
– Use a unique
User ID when
tracing to make
the trace file
easier to read.
7
 Trace files are found in the

PS_SERVDIR/LOGS directory of your
application server.
– PS_SERVDIR is a Unix environment variable.
8
9
SQL Error
10
PeopleCode Error
11
 If you find an area

of PeopleCode that
appears to be a
performance issue
or returns
“unexpected”
results, you can
trace the same
area again with an
expanded set of
trace options
12
Expanded PeopleCode Error
13
Agenda
 Introduction
 Questions
14
Tracing SQR Programs
 Append the –s flag to the Process

Definition to see a list of the SQL in the
program and execution counts .
15
16
 Append the –debug flag to the Process

Definition along with the debug flag(s)
you want to see.
17
 The trace file can be accessed

directly within the Process Monitor.
18
Agenda
 Introduction
 Questions
19
Tracing Cobol Programs
 Override the Parameters List in the

Process Definition using the following
template:
– PRCSNAME
ORACLE/%%DBNAME%%/%%OPRID%%/%%O
PRPSWD%%/%%RUNCNTLID%%/%%INSTANCE
%%/255/%%DBFLAG%%
20
 The trace file can be accessed

directly within the Process Monitor.
21
PeopleSoft Cobol
22
Trace (Body)
23
Trace (Timings)
2.
1.
3.
24
SQL Error
25
“DMS” Error: Select Item
26
“DMS” Error: Bind Variable
27
Subscript out of range
28
 Tracing Cobol executed from a

RemoteCall in PeopleCode (e.g.,
pushbutton) is the most complex type
of trace to setup in PeopleTools 8.4x.
 Requires making changes to the
psappsrv.cfg file on the Unix server.
– Located in PS_SERVDIR directory.
 Impacts everyone using the application.
Be sure to turn off the trace as soon as
you are done.
29
 Set TraceSQL=255 in psappsrv.cfg*.

*Note: The associated “Mask” value must
be set higher than this.
30
 Set RCCBL Redirect=1 in psappsrv.cfg.
31
 Cobol trace files can be found in the

PS_SERVDIR/LOGS directory*.
*Note: The .err file is only found if there is a Cobol error.
32
Agenda
 Introduction
 Questions
33
Tracing App Engine Programs
 App Engine programs rule!

 App Engine programs can be traced in
two-tier mode from the Application
Designer.
 The PeopleCode Debugger can be used
with App Engine programs in two-tier
mode from the Application Designer*.
*Note: This is the only case in PeopleTools 8.4x where
the PeopleCode Debugger can be run in two-tier mode
34
 Append the appropriate trace flag(s) to

the Process Definition.
• -TRACE 131 (App Engine trace, required)
• -TOOLSTRACEPC 2048 (PCode trace, optional)
• -TOOLSTRACESQL 31 (SQL trace, optional)
35
 The trace files can be accessed directly in

process monitor.
36
Trace (Body)
37
Trace (SQL Timings)
38
Trace (PeopleCode Timings)
39
Trace (Totals & Environment)
40
SQL Error (Process Monitor)
41
SQL Error (Trace)
42
PeopleCode Error (Process Monitor)
43
PeopleCode Error (Trace)
44
Dynamic Call Error (Trace)
45
 For two-tier tracing, you must run App

Engine processes through the web
browser at least once; you need to do
this in order to have a Run Control ID and
Process Instance Number*.
46
 Turn on your Application Engine Trace flags in

the Configuration Manager.
47
 With the App Engine program open in the

Application Designer, press the Run Program
icon and enter the Run Control ID and Process
Instance Number. Click ‘OK’ to run the App
Engine process in two-tier mode.
Defaults
48
 You can find the log files for the run in

the C:\TEMP\PS\DBName directory*.
*Note: The location of this file can vary depending on the
particular configuration of your workstation.
49
 To debug PeopleCode in an App Engine

program, turn on the PeopleCode
Debugger Mode and set breakpoints
before running.
50
Agenda
 Introduction
 Questions
51
PeopleCode Debugging
 Online PeopleCode Debugging must be

done three-tier from the Citrix desktop.
– Login to App Designer with the name of the
application server.
52
PeopleCode Debugging
 Debugging swaps back and forth between

browser session and App Designer*.
*Note: You must login to both sessions with the same
Userid.
53
Agenda
 Introduction
 Questions
54
55

Tracing & Debugging in People Tools 8.4x CMS411

Uploaded by

Copyright:

Available Formats

Tracing & Debugging in People Tools 8.4x CMS411

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tracing & Debugging in People Tools 8.4x CMS411

Uploaded by

Copyright:

Available Formats

Student Administration

Tracing & Debugging in

 No more pstools.exe on the local client!

 These are very

 Trace files are found in the

 If you find an area

Expanded PeopleCode Error

 Append the –s flag to the Process

 Append the –debug flag to the Process

 The trace file can be accessed

 Override the Parameters List in the

 The trace file can be accessed

“DMS” Error: Select Item

“DMS” Error: Bind Variable

Subscript out of range

 Tracing Cobol executed from a

 Set TraceSQL=255 in psappsrv.cfg*.

 Set RCCBL Redirect=1 in psappsrv.cfg.

 Cobol trace files can be found in the

 App Engine programs rule!

 Append the appropriate trace flag(s) to

 The trace files can be accessed directly in

Trace (SQL Timings)

Trace (PeopleCode Timings)

Trace (Totals & Environment)

SQL Error (Process Monitor)

SQL Error (Trace)

PeopleCode Error (Process Monitor)

PeopleCode Error (Trace)

Dynamic Call Error (Trace)

 For two-tier tracing, you must run App

 Turn on your Application Engine Trace flags in

 With the App Engine program open in the

 You can find the log files for the run in

 To debug PeopleCode in an App Engine

 Online PeopleCode Debugging must be

 Debugging swaps back and forth between

You might also like