We are wondering what rules the fact an error message ends up in a database log file or not.
For instance, we have seen the following one:
[2018/04/27@13:01:11.678+0400] P-2816 T-284 I SRV 4: ** Input value: <input> should be <yes/no>. (87)
We know that all errors messages of a db-bound client session do not end up in the DB log file. Are there options to alter the type of messages logged in the DB log file?
/S
> We are wondering what rules the fact an error message ends up in a database log file
when the errors are raised in the server-resolved part of the WHERE clause:
FOR EACH customer NO-LOCK WHERE LOGICAL(customer.NAME): END.
Self-service clients will raise the errors on a screen, remote clients - in db log.
In other words, the messages that do not have the prefixes %B or %L in promsgs file will be written to a database log if a running process does not have a controlling terminal.
> We are wondering what rules the fact an error message ends up in a database log file
when the errors are raised in the server-resolved part of the WHERE clause:
FOR EACH customer NO-LOCK WHERE LOGICAL(customer.NAME): END.
Self-service clients will raise the errors on a screen, remote clients - in db log.
In other words, the messages that do not have the prefixes %B or %L in promsgs file will be written to a database log if a running process does not have a controlling terminal.