1 FMC_COM_VMSPHONE
  
  You want I should phone for a pizza?
1 FMC_COM_VMSMAIL
  
  This utility is sexist and should be re-named
  to VMS PERSON.  
  
2 Footnote
  
  Have you received any electronic persons lately? 
1 FMC_COM_SHOW_TIME
  
  This command procedure has a big financial benefit to
  any organization.  It saves you buying a watch.
1 DAY
  You know... the time when that yellow thing pokes
  through the smog.
1 EVENING
  The time when you can't see the smog anymore 'cause
  it's too dark.
2 Also
  
  Yes well.  It's also the time you can have a lot of fun.  
1 DEMO_SUBPROCESS
  This is a demo program (in Pascal) provided with source
  to show how a program can run as either a sub-process
  or an independant process.  It takes very minor modifications
  to a program to achive this.
  
2 Benefits
  From the tests we conducted (using a TDMS/RDB application program)
  we found that second and subsequent invokes to the sub-process
  via LIB$ATTACH (the program still open/close files databases etc)
  used between 40% & 50% of the CPU as required by a direct chain
  (LIB$RUN_PROGRAM).  Also returning to the menu also requires
  less CPU.  Hence this is a method of firstly trading memory
  usage against CPU usage, and also giving users better response
  for their common applications.
2 Note
  For the menu to effectivly use the sub-process processing without
  locking out choices for users when their sub-process quota is 
  reached, the menu must be operating in FMC_LOG_MENU_SUBPROC =
  "CONTINUE" mode. This is the default.  This means when the menu
  gets an error on the SPAWN, then it will execute the command as
  a LIB$DO_COMMAND instead.
  
  This enables the users to keep their favourite couple of programs
  lying around in sub-processes, depending on their sub-process limit.
1 LOGOUT
  This means say bye bye to the demo menu session.
  
