This document covers the following topics:
whether external object can be read
whether documentation object can be written.
It is possible to add several objects one after another in a single incorporation function. When the function is started, it is not possible to know how many objects will be added in total and what the IDs of these objects will be. For reasons of consistency, it is not possible to interrupt an incorporation function once it has started. For this reason, only the object ID entered by the user is checked against security. No checks are performed on IDs of objects not specified by the user.
Database number must be entered for the function Incorporate Adabas File. This database is checked for READ access because attributes of this database are displayed on the following screen.
This function also updates the values for the Vista elements of the file. However, no additional security checks are performed here.
If the function Display Masters is executed from within the functions Incorporate DB2 Tables/Views and Incorporate DB2 Tablespaces, the names of all subordinate DB2 objects are displayed without any additional checks.
When a DDM is incorporated, file relations are also added and the file list of the database object is modified. No additional checks are performed for these modifications. Checks are only performed for objects which can be entered in the function screen.
Only Natural Security is checked in the selection list.
The user needs ADD or MODIFY access to the database in Predict and READ access to the NDB.
Individual files are not checked for security when files of type I and J are added or files of type I are modified.
It does not make sense protecting individual files in an IMS database. We recommend using naming conventions to give all files in an IMS database the same protection.