STS logging level (-stslogginglevel)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
| Operating system and syntax | UNIX / Windows |
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| DBS,CC | 5 | 0 | 0 | 0 |
- n
- The logging level:
- 0 — none
- 1 — fatal errors only
- 2 — all errors
- 3 — all errors and warnings
- 4 — all errors, warnings, and informational messages
- 5 — all errors, warnings, informational, and debug messages
- Values less than 0 or greater than 5 generate an error
For use with the OpenEdge Authentication Gateway only, use STS logging
level (-stslogginglevel) to specify the logging level value
for STS client interface logging. This client-side startup parameter can aid you in
debugging authentication problems in an OpenEdge Authentication Gateway deployment.
The STS logging level (-stslogginglevel)
parameter may be modified while your database is online using PROMON or through the
_DbParams VST. This online change will only take effect on new connections to the
database.
Notes
- This is a per database connection setting. If you connect to more than
one database, each database can have a different
-stslogginglevelvalue. - All output generated by
-stslogginglevelis written to the database .lg file. - If the primary broker specifies
-stslogginglevelat startup, the shared default is changed to the broker's value. Automatic servers and secondary brokers can only use the shared default. - Automatic servers and secondary brokers can only use the shared default value.
- Single user connections, self service clients and manual servers use the
default shared value by default, but can override the use of the default by specifying
their own
-stslogginglevelvalue upon connection. - Remote clients use their database servers' setting according to the above rules.