You can use the reporting facilities of the DDUTILTY or DDUPDATE utilities to produce reports that display the security structure of CA Datacom Datadictionary. By merging report requests, you can display the PERSON entity-occurrences and determine what access each user has to the CA Datacom Datadictionary.
Note: For more information about producing reports, see the CA Datacom Datadictionary Batch Reference Guide.
The first set of example transactions defines a simple path named SECURITY with the relationships discussed previously in this part of the guide from the PERSON entity-type to the AUTHORIZATION entity-type. This is all that is required to generate a useful security report.
The next set of transactions actually defines the report types that are merged to generate the security report.
Defines the PERSON entity-occurrence that is to be the focus of this report. In the following example, the person is D-B-ANALYST.
Indicates that, for every PERSON entity-occurrence accessed, a line in the Indented Report format is generated. This transaction actually would be used when you do not specify a specific PERSON entity-occurrence.
Requests that for every occurrence of the AUTHORIZATION entity-type access, a Relationship Report is generated showing the relationships between the AUTHORIZATION entity-occurrence and any TABLE or SYSTEM entity-occurrences to which it is related. The override code is required to display the user-defined profiles.
The following are the sample batch transactions used to generate the example report through the DDUPDATE or DDUTILTY utility. Since this is a user-defined profile, the override code is required. The four asterisks in the -RPT RELAT transaction represent the override code defined for the CA Datacom Datadictionary.
-DEF PATH,SECURITY -DEF TRACE,PERSON.AUTHORIZATION,PER-ATZ-AUTH -END -RPT START,PERSON,D-B-ANALYST(PROD),SECURITY -RPT INDEN,PERSON -RPT RELAT,AUTHORIZATION(,****),TABLE,SYSTEM -END
|
Copyright © 2014 CA.
All rights reserved.
|
|