Menu/1

Description

• MENU/1 is a program that makes it possible to define individual menus with specially selected applications for all users. The menus in their turn may contain an unlimited number of sub-menus.
• When started MENU/1 will optionally grant one or more identifiers to the process that executes applications. When the application has finished the identifiers will be revoked.
• Applications can be started interactively and in batch.
• Applications can be distributed to different nodes on the network. The user don't have to know on what node the chosen application is executed.
• Groups of applications can be created. Users may then be assigned to different groups or roles, thereby automatically getting access to applications.
• MENU/1 can dynamically increase its virtual address space and invoke applications as sub-routines.
• MENU/1 can start privileged applications in a secure environment. The username can be pre-set for each application.
• Dynamic usernames or uic's can be defined per application

 MENU/1 for the end user

A user of MENU/1 will make a normal login into a VMS system with the help of username and password. MENU/1 will thereafter automatically be started by login.com or otherwise. The users main menu, (profile), is displayed. Different sub-menus, (sub-systems), may be linked to the main menu thereby creating a hierarchical tree.

An infoboard, containing messages from the system manager, is displayed in a special window.

Each application has a short name and a descriptive text. An application is selected with the help of arrow keys on the keyboard or just by writing its short name.

Help support is also available for the user if he wants more information about a special application. If the user pushes the Help button a window containing help information will be displayed.

If the application requires parameters, MENU/1 will create a window with prompts and input fields.

These parameters are passed to the selected application when it is started.

When the application has finished the current menu will be displayed and the user can make a new choice.

MENU/1 for the system designer

MENU/1 follows the VAX/VMS command structure and VMS help is available.

MENU/1 supports five different types of applications:

• MENu An unlimited number of menu applications can be defined.

Applications can be connected to one or more menus. Menus can be connected to other menus thereby creating a menu tree.

• COM VMS command files can be defined as applications.
• SYMbol VMS commands can be used as an application.
• EXE Executable images.
• ACMs ACMS application task.

Up to eight parameters can be defined for each application with optional prompt texts and input fields. A parameter can be defined with the "required" input attribute and other options.

MENU/1 collects data for the parameters and starts the application. Command files will have these parameters available in P1 - P8.

In SYMbol applications will parameters be substituted if defined in the command.

Applications connected to a menu are placed in the menu area at the centre of the display. If the applications can't fit in one column two columns will automatically be used. The menu area itself can be scrolled if not enough space is available on the display.

MENU/1 for the system manager

Security

User defined identifiers can be defined for each application.

Identifiers also have to be defined by the system manager in the Rights database. Identifiers do not have to be ‘dynamic‘ and may have the resource attribute. The resource attribute makes it possible to implement project accounting of disk resources.

Individual users don't have to be granted identifiers as MENU/1 automatically will perform this function when the application is executed.

Applications are defined with their identifiers in MENU/1's database. When the user selects an application he is entitled to, MENU/1 will grant the user process needed identifiers to make it possible for the user to access resources like databases. VMS will make all access checks needed to maintain security. Identifiers are revoked when the application has finished its work.

An application can be defined to need enhanced security and user control. The user have to qualify himself with his own password before the application is started. This check means that the person currently using the terminal is the authorised person for the application.

Privileged applications can also be executed using dynamic Uic's, pre-set usernames, elevated Vms-privileges in a completely secure environment. Normally a MENU/1 user has no other privileges beyond TMPMBX and NETMBX and can, with the help of MENU/1, still access databases that are protected.

As a result of this approach it is possible to allow users full access to VMS and still maintain security.

With authorisation, the systems designer or maintainer can even simulate and verify functions of the application system as if being another user, without logging in on that user's account.

Performance

Executable modules, linked shareable, can be invoked in runtime by MENU/1 with no requirements of knowledge beforehand. MENU/1 will map the code and increase the virtual address space. The application is treated like a sub-routine by MENU/1 resulting in very fast activation and termination of applications. A number of user-built applications can be linked together to one or more executable images and MENU/1 will, on demand of the users, execute selected applications in these images.

Code sharing is promoted by this technique. Image activation and termination overhead is minimised. Allocated channels to databases are maintained.

Applications can also be executed in MENU/1 server processes. These processes are created by MENU/1 when needed and repeatedly used for execution. ACMS and DEC Admire applications tasks are supported.

Finally, the users own process can be utilised as environment for applications if the system manager so decides.

Distributed applications

An application can be defined to have one or more clients. A client node is a computer on the network that will execute the application. Applications chosen by the user on the local menu will transparently be started on a remote client computer. The list of clients defined for an application provides failover in the case of computer or network failure.

Documentation

A MENU/1 Installation Manual and a MENU/1 Reference Manual is included in the installation kit.

Hardware requirements

Alpha AXP, VAX, MicroVAX or VAXstation. About 5000 disk block is required for MENU/1

Software requirements

OpenVMS Operating System version 5.x or later.OpenVms AXP version 6.0 or later.

Licensing

MENU/1 is furnished under licensing provisions of Cerit AB's License Agreement and is made operational via a software key connected to the cpu.

Service

A Service Agreement may be signed. For more information on this, please contact Cerit AB or authorised distributors.

Warranty

Warranty for MENU/1 is provided by Cerit AB with the purchase of a license for the product.

Distribution

MENU/1 is available on the following medium:

- TK50 Streaming Tape

- Dat 4 mm tape