This document covers the following topics:
No security checks are performed when Predict is accessed from Adabas Native SQL.
The same security checks are performed as in Predict maintenance functions.
- DDMs
DDMs are protected using Natural Security. No additional measures are necessary in Natural to protect DDMs.
- LIST XREF
For function Report programs with XRef data, Predict Security checks whether the user has READ access to the program.
- Natural Development Server (NDV)
Base and compound applications are protected.
- Natural Editor
- .F and .V Commands in Natural Editor
If the user has no READ access to the file object in Predict, the Predict information is not displayed.
- Edit Free Rule in Natural Map Editor
If the user has no READ access to the verification object in Predict, the Predict information is not displayed.
The only security checks are performed by the Predict Coordinator.
A check is performed in Super Natural as to whether the user can use a particular DDM. If this is the case, the user can read the corresponding data in Predict.
No security checks are performed.
The same checks are performed for incorporation functions called from SYSDB2 as are performed in Predict.
A user must have READ access to the respective program object in order to read the entry points of a DBRM.
With function Bind plan, SYSDB2 checks whether the user has READ access to the corresponding System object. As in Predict generation functions, only the main object is tested.
The SYSHELP utility does not need to be protected. In a production environment it is only possible to access programmed objects, and each user will have access to these objects. It would not make sense to restrict SYSHELP access in a development environment.