Use Limit log file payload (-limitLgPayload) to prevent message payload from being written to the client or database log file. Message payload is defined as the user name, device, tty name, IP address, and connection hostname in a message.

Operating system and syntax UNIX / Windows 
-limitLgPayload n
Use with Maximum value Minimum value Single-user default Multi-user default
Database Server, Client Session 1 0 0 0
n
Specify if payload is included or omitted.
  • 0 — Limit payload is off; the complete contents of messages is written to the client or database log file.
  • 1 — Limit payload is on; payload data within a message is not written to the client or database log file, and is replaced with the string, "<omitted>".

If limit log file payload (-limitLgPayload) is turned on, the lock wait timeout error message in a client log is affected, such that the username and device are omitted. The following example displays the difference in messages written to the client log file when -limitLgPayload is enabled and disabled.

Table 1. Limit payload example for a client log
Error Limit payload enabled Limit payload disabled
Lock wait timeout 
(8812); User: <omitted>, Device: <omitted>, Table: Customer
 
(8812); User: smith, Device: abc-de-F123, Table: Customer

All messages written to the database log file (dbname.lg), and messages that are written to both the log file and the screen, honor the -limitLgPayload setting. Messages only written to the screen, do not check the payload setting. Other log files, such as for SQL or Replication, honor the payload setting when the information written to the log file is obtained from the database connection information.

The following examples displays the difference in messages written to the database log file when -limitLgPayload is enabled and disabled.

Table 2. Limit payload examples for a database log
Command or action Limit payload enabled Limit payload disabled
Server startup 
(4281) Server started by <omitted> on <omitted>.
 
(4281) Server started by jdoe on /dev/pts/17.
Login 
(452) Login by <omitted> on <omitted>.
 
(452) Login by jdoe on /dev/pts/9.
Logout 
(453) Logout by <omitted> on <omitted>.
 
(453) Logout by jdoe on /dev/pts/9.
Remote login 
(742) Login usernum 24, userid <omitted>, on <omitted>.
(7129) Usr 24 set name to <omitted>.
(17961) User 24 set tty to <omitted>.
(7129) Usr 24 set name to <omitted>. 
(742) Login usernum 24, userid jdoe client type ABL , on oesol64 108 using TCP/IP IPV4 address 172.16.18.108.
(7129) Usr 24 set name to jdoe.
(17961) User 24 set tty to oesol64 108.
(7129) Usr 24 set name to jdoe.

The value specified at startup is available via the _DbParams VST. The values can be read and updated.

The value specified can be viewed and modified in PROMON.
  • To view the current setting, select from the Promon Main Menu, R&D > 4 (Administrative Functions) > 7 (Server Options)
  • To change the current setting, select from the Server Options menu, 9 (Limit .lg message payload). The value is toggled between Enabled and Disabled.

To change this parameter while the database is running, use PROMON or the _DbParams VST.

You can use this parameter to support continuous operation of the database. For more information, see Change database parameters while the database is running.