Thanks to everyone that has been sending me information regarding menus and
logon UDCS (and how they are used at their particular sites).

There has a been a lot of commonality (word?) between the various e-mails
I have recieved. I thought I woudl summarize some of the common themes
below:

* It is *very* common for system managers to use some type of logon UDC
  which provides the enduser with a menu of choices. This is done primarily
  as a sort of "security memchanism" -- allowing the system manager to
  have control over what operations a given user can perform (only those
  specified in the menu).
* In nearly every case menus are presented OPTION NOBREAK (to prevent/deny
  access to the : prompt which would defeat the secruity rationale).
* Many customers use the VESOFT menu handler. [I would need to talk to
  someone at VESOFT to get more information on how that menu hanlder
  is implemented.] Also popular is the menu handler from Robelle.
* Many customers have "homegrown" menu handlers (with customer
functionality).
* Some menu handlers are written to "cooperate" with the applications and
  use "acitvate" and "suspend" instead of "create" and "terminate" - to
  "improve performance".
* Many/most customers have multi-level menus (some menu handlers implement
  the multi-level menus with a single process, others create a separate
  process for each menu-level).
* Most of the respondants that mentioned the number of concurrent users
  were well below number of users required to approach/hit the concurrent
  process limit (thus were in no immediate need of reducing the number of
  processes per connection). NOTE: I am not interpreting this to mean that
  reducing processes per connection is unimportant -- I am simply mentioning
  it because it was true amongst the respondants.