Josef,
The NOxxxCHK attributes is one of the first things checked when a security check occurs. If the user has the appropriate, NOxxxCHK no further security checking occurs. Since the full security check is not done, this saves on CPU.
But there is the cost of an OK+B record being written to the audit file.
You could make use of the TSSINSTX exit in CA Top Secret to suppress the OK+B audit records. You would have to add your own user written code to the TSSINSTX installation exit to do this.
The following sample user code for the TSS installation exit has been given to a number of clients who want to suppress OK+B records from being logged to
the audit file:
If Acid = *BYPASS*
or if Pgm = IKJEFT01 and running as batch job.
VIOLATN DS 0H
ICM R5,15,TXA#FLOG R5 = Addr Fast Logging Buffer
USING FLOG,R5 Map Buffer
TM FLIND1,$FLBYPSS Bypass Security ?
BZ LOGIT no, log this event
ICM R3,15,TXA#ACID R3 = Addr Acid
CLC 0(8,R3),=CL8'*BYPASS*' Acid *BYPASS* ?
BE NOLOG Y, don't log
CLC FLPGM,=CL8'IKJEFT01' TMP ?
BNE LOGIT N, log this event
CLI FLTYPNUM,C'J' TMP Batch ?
BE NOLOG Y, don't log
B LOGIT N, log it
NOLOG B EXIT4 Bypass logging
LOGIT B EXIT0 log this event
If TXA#ACID is *BYPASS*, it is an OK+B event. This code can be modified to suppress OK+B records from whatever circumstances you choose.
This is sample code and not supported or maintained by CA. It is the users responsibility to support, customize and maintain this sample code.
Regards,
Joseph Porto - CA Level 1 Support