The SPS/Menu system organizes applications into concise, professional and user friendly interfaces. Creating menus is a simple procedure; it takes minutes to complete thereby saving time and money and helping meet development deadlines. SPS/Menu requires no FMS work and no programming and therefore does not require any Stratus expertise.
The system greatly enhances system security by adjusting and generating menus on a per-user basis according to the individual's security profile.
The SPS/Menu System provides complete audit trail logs of all system and operator activities including security violation attempts detailing commands executed, user names and the time of execution.
SPS- Security Diagram
Example of a Menu-ed structure
|Automatically generates box-type menus with unlimited chains of sub-menus|
|Requires no programming or technical skills|
|Integrates existing applications into professional looking, uniform and consistent interfaces|
|Supports single-key transfers between applications|
|Features the Security Layer and offers additional facilities such as: Browser, Calendar and Disk Space|
|Supports user programmable function keys for frequently used commands|
|Produces a comprehensive audit log of all commands executed, users' identity, date and time of each event|
|Features the IDG layer (Intelligent Document Generator) that translates menu configurations into full-length documents|
|Provides a configurable on-line help facility linking menu items to existing documentation files|
|Reduces dramatically risk of human error, cost of documentation and training expenses|
SPS Menus vs. Command Macros
There is a lot of added value in using the SPS solution compared with command macros. With minor effort (yes, we can help!) you can convert your macros into easy-to-maintain tables. SPS menus are all table driven, easy to maintain and generated dynamically ("on the fly") based on user's security profile. In comparison, command macros are fixed for all users, require development and testing time, and lack many other features such as detailed audit trail reporting, on-line help and documentation.
|Command Macros||SPS Menus|
|Require development and testing||All table driven, easy to maintain. Menus are generated dynamically ("on the fly")|
|Menus are fixed for everyone, no "on-the-fly" adjustments and no built-in security||Adjustments of menus/sub-menus is based on user-id, time-of-day, terminal-name|
|Limited, difficult to follow traces. In many cases logging may be turned off by the operator||Robust, complete and easy to follow activity audit trail reports outlining date/time, user-name, command executed and any security violation|
|Slow interface, may provide inconsistent presentation; no external or add-on tools||Consistent, user-friendly interface including, the powerful SPS/File Browser, SPS/Calendar, "Hot Menus" and more|
|Function-keys are disabled||Programmable function keys|
|No on-line documentation||Allows on-line help/documentation for each item or sub-menu|
|Command macro processing require system resources||Extremely fast, has no performance overhead|
Frequently asked questions
Can I enforce menu-driven access only on certain operators or users?
My application has a built-in menu. Can I still use the SPS menuing solution? What would be the advantage?
We already provide our operators with menus. Our menus are driven by a set of home-grown command macros. This approach seems to work for us, how would we benefit from SPS?
Can I protect the SPS audit trail reports? How can I monitor what the System Administrator is doing?