Trace AE 8.

4X
SUMMARY: PROCEDURE A: On the PIA.......................................................................................................... 1 PROCEDURE B: On the Process Scheduler ................................. Error! Bookmark not defined.

NOTE 1: Tracing activated for one Application Engine or all Application Engines On the PIA, you can activate tracing for a particular Application Engine. When activating tracing on the Client or on the Process Scheduler, any Application Engine run will generate a trace file.

NOTE 2: Push button If you want to trace an Application Engine triggered via a push button, follow procedure B but for the Application Server.

NOTE 3: PSJob The procedures can also be used if the Application Engine you want to trace is run via a PSJob. PROCEDURE A: On the PIA A.1.Sign in the PIA. A.2.Navigate to the Processes component and select the Application Engine that you would like to get a trace on.

A.3.Go to the Override Options tab, set the Parameter List option to Append, and add the tracing flags as explained below. You can turn on tracing for the Application Engine itself, for the SQL statements run or the PeopleCode run by the Application Engine, or a combination of the three. Application Engine tracing: Add the sum of all the options you want to use at the end of the parameter list and precede the number by TRACE + a space. For example: -TRACE 391 UTIL: Cel mai folosit de Zulma este 131 si clientii folosesc 135 Direct in Sever: Se acceseaza fisierul : X:\BLD\GSC\E881\ORA\E881GX1P\appserv\prcs\E881GX1P/ psprcs.cfg Unde se trec valorile pe care le dorim la trace Here is the list of options and associated numbers for each option: 1 2 4 128 256 1024 Initiate the Application Engine Step trace Initiate the Application Engine SQL trace Trace dedicated Temp Table Allocation to AET file Initiate the Statement Timings trace to file, which is similar to the COBOL timings trace to file Initiate the PeopleCode Detail to the file for the Timings trace Initiate 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 Adding this value requests a database optimizer trace file Request a database optimizer to be inserted in the Explain Plan Table of the current database This value sets a trace for Integration Broker transform programs

2048 4096 8192

To turn traces on, sum all the options you want to use and enter the results at the end of the parameter list and precede the number by TRACE + a space as shown above. For example, you should use 391 (1+2+4+128+256) to trace what is shown in bold above.

SQL tracing: Add the sum of all the options you want to use at the end of the parameter list and precede the number by TOOLSTRACESQL + a space. For example:

-TOOLSTRACESQL 135 Here is the list of options and associated numbers for each option: 1 2 4 8 16 32 64 128 256 512 4096 8192 Trace SQL statements Trace SQL statement variables Trace SQL connect, disconnect, commit and rollback Show fetched rows (indicates that it occurred, not data) Show all other API calls except ssb Set Select Buffers (identifies the attributes of columns to be selected). Show database API specific calls Show COBOL statement timings Show Sybase bind information Show Sybase fetch information Show manager information Show Mapcore information

To turn traces on, sum all the options you want to use and enter the results at the end of the parameter list and precede the number by TOOLSTRACESQL + a space as shown above. For example, you should use 135 (1+2+4+128) to trace what is shown in bold above.

PeopleCode tracing: Add the sum of all the options you want to use at the end of the parameter list and precede the number by TOOLSTRACEPC + a space. For example: -TOOLSTRACEPC 2012