| # Logging Parameters (ttaad4153m000) Use this session to define the parameters for the logging of database locking and shared memory usage. Note You can only change parameters when you are logged on to the Master Application Server (MAS). The MAS is registered in the Systems (ttaad0550m000) session. For shared memory logging, you can define a time frame in which the logging of object usage in the bshell takes place. For database locking, you can specify a threshold and a time frame. After you specified the logging parameters, click Convert. You can only run the Convert command on a Master Application Server. For details, refer to the field and form command help. Related topics Generate lock graph html output (ttstplocklog) Shared Memory Object Measurement (ttaad4152m000) Print Shared Memory Object Measurement (ttaad4452m000) Shared Memory Data (ttaad4156m000) Print Shared Memory Data (ttaad4456m000) Allocated Memory Shared Memory (ttaad4155m000) Locking Threshold [ms] The threshold, in milliseconds, for logging database lock actions. Lock actions that last shorter than the specified threshold, are not written to the log file. Example: `10`. Only lock actions that last 10 milliseconds or longer are written to the log file. File Name The path and name of the log file where the locking statistics will be stored. For example: `${BSE_TMP}/log_locking.$$`. At runtime the `$$` extension is replaced by a number. For example: the logging process generates the following file: `log_locking.1048612`. From Use this field to define the time frame in which the logging of database locking takes place. If you do not define a time frame, no logging is done. To Use this field to define the time frame in which the logging of database locking takes place. If you do not define a time frame, no logging is done. Shared Memory From Use this field to define the time frame in which the shared memory logging takes place. If you do not define a time frame, no logging is done. To Use this field to define the time frame in which the shared memory logging takes place. If you do not define a time frame, no logging is done. Convert Stores the entered data in the `$BSE/lib/defaults/logging` file. The date / time ranges are stored in UTC format. The following lines show an example of the content of the `logging` file:
    log_locking_threshold:0
    log_locking_logfile:${BSE_TMP}/log_locking.$$
    log_locking_start:1194220740
    log_locking_end:1194343140
    log_shm_start:1200956400
    log_shm_end:1201006920
You can only run the Convert command on a host defined as Master Application Server (MAS). If the host is not a MAS, all selection fields and the Convert command are disabled. Cleanup Removes the currently stored shared memory measurement data. |