Siebel Object Interfaces Reference > Using Siebel Visual Basic and Siebel eScript > Configuring Error Handling >

Tracing a Script

As part of debugging a script you can run a trace on allocations, events, and SQL commands. You can start tracing for a user account, such as your development team. The Siebel Server sends trace information to a log file.

For information about:

• Configuring server components, see Siebel Applications Administration Guide
• Logging events, see Siebel System Monitoring and Diagnostics Guide
• File tracing, see Trace Method for an Application

To enable logging for the local object manager, you can set the SIEBEL_LOG_EVENT environment variable to a value of 2 through 5. For more information, see Siebel Applications Administration Guide.

To trace a script

1. In the Siebel client, navigate to the Administration - Server Configuration screen, and then the Servers view.
2. In the Components list, choose a component to log.
3. In the Events list, locate the Object Manager Extension Language Log event.

   If this record does not exist, then you cannot use the component you chose in Step 2 for logging.

4. Set the Log Level to 1.
5. (Optional) Modify tracing parameters:
   1. Click the Parameters tab.
   2. In the Component Parameters list, click Menu, and then choose the Columns Displayed menu item.
   3. Move the Parameter Alias and Subsystem columns to the Selected Columns window, and then click Save.
   4. In the Component Parameters list, click Query.
   5. Enter the following values, and then click Go.

      Field	Value
      Parameter Alias	Trace*
      Subsystem	Object Manager

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

      Information to Trace	Parameter Alias	Settings for Current Value and Value on Restart
      Allocations	TraceAlloc	Enter 1 to enable logging. Enter 0 to disable logging.
      Events	TraceEvents	Enter 1 to enable logging. Enter 0 to disable logging.
      SQL Commands	TraceSql	Enter 1 to enable logging. Enter 0 to disable logging.
      Users	TraceUser	Enter a list of user names. Use a comma to separate each user name. For example: sadmin,mmasters. Do not use spaces. You cannot enter more than 20 characters in this parameter. CAUTION:  Tracing on the Siebel Server can affect performance. If you simultaneously trace multiple users, then use caution.

      To instruct Siebel CRM to immediately modify these parameters, enter values in the Current Value column.

      To instruct Siebel CRM to modify these parameters only after a restart, enter values in the Value on Restart column.

6. Test your work, and then examine the results.
7. When you are finished logging, set the Log Level that you set in Step 4 to 0.

The following is part of an example of the trace output:

2021 2003-04-09 15:37:20 2003-04-09 16:40:52 -0700 00000022 001 001f 0001 09 SCCObjMgr_enu 47126 1680 1584 C:\sea752\siebsrvr\log\SCCObjMgr_enu_47126.log 7.5.3 [16122] ENU

ObjMgrSessionInfo ObjMgrLogin 3 2003-04-09 15:37:20 Login name : SADMIN

ObjMgrSessionInfo ObjMgrAuth 3 2003-04-09 15:37:20 Authentication name : SADMIN

ObjMgrSessionInfo ObjMgrLogin 3 2003-04-09 15:37:20 Session Type: Regular Session

GenericLog GenericError 1 2003-04-09 15:37:20 Invocation of Applet Menu New Service::NewExpense is not allowed.

GenericLog GenericError 1 2003-04-09 15:37:20 Invocation of Applet Menu New Service::NewTimeSheet is not allowed.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:38:27 [User: SADMIN] EVENT, BEGIN, BusComp [Account], BusComp_Query.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:38:27 [User: SADMIN] EVENT, END, BusComp [Account], BusComp_Query.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:38:58 [User: SADMIN] EVENT, BEGIN, BusComp [Account], BusComp_NewRecord.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:38:58 [User: SADMIN] EVENT, END, BusComp [Account], BusComp_NewRecord.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:39:08 [User: SADMIN] EVENT, BEGIN, BusComp [Account], BusComp_PreSetFieldValue.

ObjMgrExtLangLog ObjMgrExtLangLog 0 2003-04-09 15:39:08 [User: SADMIN] EVENT, END, BusComp [Account], BusComp_PreSetFieldValue.

ObjMgrSessionInfo ObjMgrLogin 3 2003-04-09 16:40:52 Username: SADMIN, Login Status: Attempt, Session Id: !1.690.b816.3e94a0a0, IP Address: 172.20.94.66