iSecurity:
View
  Prevention Pack
  Compliance Pack
  Applications
View FAQ

    Answer:
    View will work on the logical files level. To define additional selections - a filter can be added to an existing logical file or a new logical file will be created by View.
    Each Group Type in View creates a new library to keep the View created definitions. View created definitions are actually a new logical file per selection.
    When adding a new selection to the existing logical file or create a new one - the overhead will be the same in both cases. View will keep only one definition per selection.
    The decision to create a new logical file or use the existing ones should be made by the customer, depending on the requirements.
    Answer:
    The level of protection provided by View is... 100%! Anyone intentionally or unintentionally who is trying to by-pass View's security mechanism will be denied access by the security features of OS/400.
    Answer:
    Your system's performance will not be affected, as View uses minimal CPU.
    Answer:
    View acts like a standard file in the system and therefore doesn't add any I/O overhead.
    Answer:
    Yes
    Answer:
    The installation process is standard and simple, and can be done during regular work hours.
    Answer:
    Usually there will be no need to make any changes. Applications continue to work exactly as before, except that the fields and records that were chosen to be masked will not appear.
    Answer:
    Changes will be required if the application uses a pointer to the file instead of *LIBL, not including the OVRDBF command.
    If you are using a CL program to maintain files, i.e. creating or deleting files, Raz-Lee Technical Support team will instruct you on how to adjust the relevant CL programs.
    Answer:
    View can work with OS/400 4.5 and higher.
FAQ
iSecurity Datasheet
View
Datasheet

View
Presentation

Download View