Using External Security for CA Datacom › CA Datacom Datadictionary and External Security › Internal Overrides

Internal Overrides

There are CA Datacom Datadictionary rules that cannot be overridden by external security.

• A history (HIST) status entity-occurrence can be displayed, copied from, obsoleted, and deleted only. Therefore, any attempt to update any entity-occurrence in HIST status is rejected by DSF regardless of the information provided by the call to CAISSF. (This is true for CA Datacom Datadictionary product security profiles also.)
• CA Datacom Datadictionary entity-occurrence definitions that are defined with password or lock level protection cannot be updated without supplying the assigned password or code. For more information about assigning, using, and deleting passwords and lock levels, see the CA Datacom Datadictionary documentation.
• Field definitions using the DDUPDATE 4099 Field Access transaction maintain attribute-level security.

If the user is identified as an internal CA product such as CA Dataquery or CA Ideal, DSF bypasses security checks (except CA Datacom Datadictionary entity-occurrence passwords and locks). For example, USERA is not authorized to use CA Datacom Datadictionary. When USERA uses CA Ideal, CA Ideal is still able to make the DSF calls needed to accomplish its work on behalf of USERA because CA Ideal signs on as an internal CA product. However, if USERA tries to execute a user program through CA Ideal that makes DSF calls, USERA is denied access to CA Datacom Datadictionary.

If external security is not in effect, CA Datacom Datadictionary uses any security information, including user profiles and System Resource Table (SRT) security options, that are defined through internal CA Datacom Datadictionary security.