Table 3-1 FAQs

Questions	Answers
What is the SMTB_USER_FUNCTION_TRACE table? and How are values inserted into the SMTB_USER_FUNCTION_TRACE table?	The SMTB_USER_FUNCTION_TRACE table is a data store for capturing the function IDs related to maintenance for the Performance Diagnostic Plugin functionality which stores Function ID, Action, User ID, and Trace Value. Based on these parameters, Time Lag Report is generated. The data can be captured using the newly designed function ID STDAPPDP.
What is the use of the CSTB_PARAM flag? and When will the CSTB_PARAM be set to Y (Enabled)?	The CSTB_PARAM table have a Performance Diagnostic Plugin (PDP) specific flag called TIME_LOG, which is used to enable or disable the functionality of PDP (that is capturing of any performance lag reports or process timings or even specific application log) in the system. By default, the value is set as N. Currently, the Performance Diagnostic Plugin works for OLTP processes only.
What is the mechanism used to obtain the Application Log?	Existing Infra level functionality is used to capture the application log by retaining any existing logs related to the user and capturing a new log based on a specific naming convention (<USERID>_<FUNCTIONID>_<ACTION>.log) for a particular operation specified during maintenance. Application logs are enabled/disabled automatically at the infra level and generated application log will be written on the server as a file.
Is trace value ALL a combination of other trace values? and If yes, can this combination be achieved by inserting multiple records with the required trace values?	Yes, trace value ALL is a combination of other trace values specified like the capture of process timings, and application log to be obtained in one go. The code is designed to pick only one trace value for a combination of User ID, Function ID, and Action, due to which multiple record maintenance is not allowed. These trace values help to keep the table clean and away from confusion for the Bank IT team during maintenance.
Is this PDP functionality specific to any product?	No, this enhancement is in the Infra Layer and it is supported in all ODT framework-based products processors.
Provide a brief insight on results obtained for each trace value.	For more information on results of the trace values, refer to the below Trace Value Results table.

Table 3-2 Trace Value Results

Trace Value	Process Timing	Application Log	Trace File	HPROF File
Process Timing at Database Level	Y	N	N	N
Process Timing at Application Level	Y	N	N	N
Application Logs	N	Y		N
ALL	Y	Y	Y	N