Runtime debugging of bshell - logging information
When you run the session, trace output is generated and database information is logged.
The database logging information is stored in the dbs.<pid>.log file. This file is stored in the current working directory. In a multitenant cloud environment, this is the appdata folder of the tenant (%APPDATA%).
Bshell and BDB/SQL tracing
The logging information of the Bshell and the BDB/SQL tracing is stored in
an ASCII file. By default, the logging info is stored in the bshell.<%h>.<%u>.<%p>.<%r>.txt.gz file in the $BSE/tmp directory.
This table shows the variable elements in the file name:
| Element | Description |
|---|---|
| <%h> | The hostname or machine ID in the cloud. |
| <%u> | The LN user name. |
| <%p> | The process ID of the bshell. |
| <%r> | A random number. |
The file is compressed and has a .gz
extension.
On exit of the Bshell, the log file is deleted unless the Keep trace file after exit check box is selected.
To interpret the logging information:
- Uncompress the
bshell.<%h>.<%u>.<%p>.<%r>.txt.gzfile. Thebshell.<%h>.<%u>.<%p>.<%r>.txtis generated. - Open the
bshell.<%h>.<%u>.<%p>.<%r>.txtfile with an ASCII display utility or ASCII editor.
Usually, the trace output is first buffered and compressed, and is then written to the file. In exceptional situations, such as a hard crash of the bshell, the buffered data is not written to the file.
REST API tracing
For REST API tracing, the trace settings are stored in ${BSE}\appdata\api_trace. The name of the trace configuration settings file corresponds with the contents of the Trace ID field and has this format: <user name>_<3 digit sequence number>.
The trace files generated by the trace process are stored in the AWS_S3_admin\tmp\http_traces folder. For details about the folder structure and the trace files, see REST API trace folders and files.