experiencing an issue with a SERVAUTH call for EZB.NETACCESS.xxx.xxx.xxx not being issued with DB2.  The same setup is working on our RACF system without any issues. 

Release : 16.0

Component : CA Top Secret for z/OS

OPTIONS(90)

The new expected security checks issued by Top Secret will occur if:
  1) The NETACCESS statement is set up in the TCPIP PROFILE file
  2) Applications pass the SERVAUTH= parameter on the RACROUTE
     REQUEST=VERIFY security signon call

Note that OPTIONS(90) will have no effect on the issuance of SERVAUTH
 NETACCESS checks issued by other products such as FTP.  If the NETACCESS
 statement is inserted into the TCPIP PROFILE file then security checks
 will begin to be issued from products such as FTP regardless of the
 setting of this new OPTIONS(90) control option.