With LOGLEVEL value set to ELEVATE, not ALLTAMID, will there be any exposure to this issue?
Release : 16.0
With LOGLEVEL set to ELEVATE, the exposure is still there.
Any logging for TAMz that adds TAMz information to the SMF record can have this problem. It includes any access allowed due to the user elevation and/or LOGLEVEL(ALLTAMID), as that will add the TAMID to SMF record.