Using Siebel Tools > Using Siebel Script Editors > Using the Siebel Debugger >

Tracing a Script

You can run a trace on an allocation, event, or SQL command. You can start a trace for a user account, such as your development team. The Siebel Server saves the trace information to a log file. Tracing a script is not the same as tracing a file. For more information about tracing a file, see the information that describe the Trace, TraceOn, and TraceOff methods in Siebel Object Interfaces Reference.

To trace a script

1. Log in to the Siebel client, navigate to the Administration - Server Management screen, and then the Components view.
2. Choose the component that you want to trace.
3. Navigate to the Component Event Configuration view.
4. Locate the Object Manager Extension Language Log event.

   If this event does not exist, then the component you chose in Step 2 does not support logging. Most components support logging, but some do not. If necessary, repeat Step 2 but choose another component.

5. Set the Log Level to 1.

   To disable logging when you are done, you can set the Log Level to 0 (zero).

6. Navigate to the Component Parameters view.
7. (Optional) To display only the script tracing parameters, enter a query using the values from the following table.

   Field	Value
   Parameter Alias	Trace*
   Subsystem	Object Manager

8. Set one or more tracing parameters using the values from the following table.

   Object to Trace	Alias	Description
   Allocations	TraceAlloc	Enter 0 (zero) to disable logging. Enter 1 to enable logging.
   Events	TraceEvents
   SQL Commands	TraceSql
   Users	TraceUser	Enter a comma-separated list of user names. Do not use spaces. For example, you can enter the following: sadmin,mmasters,hkim,cconnors

   To set tracing parameters, enter a value depending on when the modification must take affect:

   • Immediately. You modify values in the Current Value column.
   • After a restart. You modify values in the Value on Restart column.

Example of a Trace

The following code is an example of a trace that Siebel Tools creates after the Business Service Simulator runs:

ObjMgrExtLangLog ObjMgrExtLangLog 0 00000080475f1578:0 2007-12-12 07:33:45 [User: ] SQLBIND, 90, 1, Y. ObjMgrExtLangLog ObjMgrExtLangLog 0 00000080475f1578:0 2007-12-12 07:33:45 [User: ] COMPILE, END, <unknown>. ObjMgrExtLangLog ObjMgrExtLangLog 0 00000080475f1578:0 2007-12-12 07:33:45 [User: ] EVENT, BEGIN, Service [sam], Service_PreInvokeMethod. ObjMgrExtLangLog ObjMgrExtLangLog 0 00000080475f1578:0 2007-12-12 07:33:45 [User: ] EVENT, END, Service [sam], Service_PreInvokeMethod. ObjMgrExtLangLog ObjMgrExtLangLog 0 00000080475f1578:0 2007-12-12 07:34:39 [User: ] SQLSTMT, 91,

Example of a Detailed Trace

The following code is an example of a trace that Siebel Tools creates if the log level is set to high. For brevity, only part of this log file is included:

2021 2007-12-12 07:46:29 2007-12-12 07:56:46 -0700 000003fd 001 003f 0001 09 SCCObjMgr_enu 11534365 5452 780 d:\21022\ses\siebsrvr\log\SCCObjMgr_enu_0011_11534365.log 8.1 [21022] ENU

ObjMgrLog Info 3 000000b9475f1578:0 2007-12-12 07:46:29 (modpref.cpp (949)) SBL-DAT-50803: SharedFileReader: D:\fs\userpref\SADMIN&Siebel Universal Agent.spf_SDCHS21N625_5452_780: File succesfully opened.

ObjMgrLog Info 3 000000b9475f1578:0 2007-12-12 07:46:29 (modpref.cpp (949)) SBL-DAT-50804: LoadPreferences: D:\fs\userpref\SADMIN&Siebel Universal Agent.spf: Preferences succesfully loaded.

ObjMgrExtLangLog ObjMgrExtLangLog 0 000000b9475f1578:0 2007-12-12 07:46:29 [User: ] SQLSTMT, 1, SELECT, SELECT

T1.CONFLICT_ID,
T1.DB_LAST_UPD_SRC,
CONVERT (VARCHAR (10),T1.DB_LAST_UPD, 101) + ' ' + CONVERT (VARCHAR (10),T1.DB_LAST_UPD, 8),
CONVERT (VARCHAR (10),T1.LAST_UPD, 101) + ' ' + CONVERT (VARCHAR (10),T1.LAST_UPD, 8),
CONVERT (VARCHAR (10),T1.CREATED, 101) + ' ' + CONVERT (VARCHAR (10),T1.CREATED, 8),
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.BUILD_NUMBER,
T1.CURR_WEBFILE_VER,
T1.ENTERPRISE_NAME,
T1.PREV_WEBFILE_VER,
T1.RECORD_INFO_TEXT,
T1.REC_IDENTIFIER
FROM
dbo.S_UIF_WEB_FILE T1
WHERE
(T1.REC_IDENTIFIER = ?).

ObjMgrExtLangLog ObjMgrExtLangLog 0 000000b9475f1578:0 2007-12-12 07:46:29 [User: ] SQLBIND, 1, 1, 16:sdchs21n625:4330siebel.

Declaring Functions and Procedures in Siebel VB

The Siebel Compiler compiles Siebel VB functions and procedures in alphabetical order for each object definition. If a function or procedure calls another function or procedure that is not defined, then the compiler creates an error message that is similar to the following:

function_name Is An Unknown Function

To avoid this error, you must use the Declare statement to declare the function or procedure in the general declarations section. Siebel eScript does not require you to declare these functions. For more information, see Siebel VB Language Reference.