ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Why Is RESOURCE DB2(DSNR..) Bypassing Being Reported As OK+A In The TSSUTIL Report?

book

Article ID: 50368

calendar_today

Updated On:

Products

Cleanup Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Top Secret Top Secret - LDAP Top Secret - VSE

Issue/Introduction

Description:

Why was the security check for the resource DB2(DSNR...), which was granted access through the NORESCHK bypass attribute being reported as OK+A instead of OK+B in the TSSUTIL report?

Solution:

The 'DSNR.' resources need special code to be handled correctly. The security call comes in as a class of DSNR and CA Top Secret converts it to a class of DB2 with 'DSNR.' being appended to the beginning of the original resource name.

Because of the way the special code was implemented, the normal mechanisms CA Top Secret uses to communicate on internal security calls cannot work properly.

CA Top Secret is able to determine that the security call is supposed to be written to the audit file, but CA Top Secret can't determine whether it is supposed to be an OK+A event or an OK+B event.

The event will be recorded as OK+A even though access was granted through the NORESCHK attribute.

Environment

Release:
Component: AWAGNT