SCENERIO 1:
-----------

A DMS client user clicks on a device picture on a UOC window 
that is displaying a CIRCUIT ONE LINE display.

1) UOC window (implemented via (DECnetcomB (colormgr) dmscge) and
   started during DMS client startup script) sends equivalent
   terminal cursor x/y coordinates and mouse click/keyboard 
   state to RAPPORT running on the primary HABITAT SERVER.

   Most likely via a corresonding UOC server there. It's
   implementation (the UOC server on the HABITAT machine)
   and even it's existence has yet to be confirmed by me.
   Suspect transport is DECNET.

	a) RAPPORT decodes this UOC event and looks up
           picture corresponding picture definition. 
	   this definition contains a mail command which 
	   rapport then sends.
	b) The mail command content is a DEVICE_ID.  The mail
	   mechansim is DEC QIO to a mailbox pseudo-device.
	   This communication is local to the HABITAT server.
	c) The mailbox is monitored in rap_db_client via
	   rapuser_get (ESCA Programming Utilties Reference).

2) rap_db_client running on HABITAT server sends DEVDET_CMD
   along with a device_id and region to rab_db_server running
   on the INGRES server via RPC calls.  
	
	a) The host that is running the server daemon is
	   defined in an environment varible and is set
           in the RPC initialization code on the client
	   before the client goes resident. 
  	b) the remote call is mapped to tcp short lived
	   ports and that mapping is maintained by
	   lb_admin.  The remote procedure exists on the
           the INGRES server machine and is rap_db_server.

3) rap_db_server gathers device info from related INGRES tables
   in dms_merge using embedded SQL and stores the assembled
   data in a single table 'ing_to_hab'.

4) rap_db_server issues a USEREVENT. 

5) All connected db clients awaken and inspect the database for their
   event.  The target db client pops up a cooresponding DMS application window.