The CA Endevor/DB Security System enhances IDD-level security enforcement. All CA Endevor/DB users and the Change Monitor run under control of the CA Endevor/DB Security System. Conceptually, the CA Endevor/DB Security System resides between the CA IDMS compilers and the dictionary. At execution time, all requests to modify entities in the CCDB or the IDD are cleared through CA Endevor/DB security. After passing CA Endevor/DB security edits, a dictionary update request is then passed to the IDD to be handled in the usual manner. If the user has already established IDD-level security, CA Endevor/DB adds a layer of additional capability on top of that already set up. If no IDD security is in effect, CA Endevor/DB security can be used exclusively to control updates to IDD entities. The security administrator can establish any combination of CA Endevor/DB security, as well as IDD options.
Please note: No security is enforced when dictionary entities are retrieved immediately prior to update. CA Endevor/DB security is enforced when the update actually occurs. If you fail IDD security, the system generates an IDD error message indicating that you cannot perform that action. If you fail CA Endevor/DB security, the system generates an CA Endevor/DB error message indicating that you cannot perform that action. Immediately after that message, the system displays an IDD error message telling you that the update has failed.
Figure 2.1 illustrates the conceptual flow of requests through the CA Endevor/DB Security System. Both the CA Endevor/DB Online System and the CA IDMS compilers gain authorization to update entities through CA Endevor/DB.
The CA Endevor/DB Security System determines overall processing options through procedure enforcement, entity attributes, and discrete function masks. These concepts are explained in more detail below.
|
Copyright © 2013 CA.
All rights reserved.
|
|