- guard_tap.ini option db_ignore_response used to avoid swamping on high-volume DBs
- Consequence is that all Exceptions are also lost, and can't report/alert on Risk-indicative Exceptions
- Probably because S-TAP is too 'dumb' to discern exceptions from results(?)
- Policy Action “Ignore S-TAP Responses per Session” has same effect
Do not place IBM confidential, company confidential, or personal information into any field.