[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

82.0. "Licensing as a Client?" by DWOVAX::LICAUSE (Al Licause) Thu Mar 22 1990 16:43

    This note is addressed at either product managment or product marketing
    management, unless of course, anyone else would care to take a wack at
    it.
    
    What I'd like to know is, if DECmcc is run in a client/server mode,
    such that it is run on a 6xxx system and accessed via workstation
    servers, then are there any implications around licensing of the
    product other than the size of the client system?
    
    Will the licensing vary or is it capable of being varied using LMF
    or anyother mechanism, such that the license price may vary based
    on the number of servers that may use same concurrently?
    
    Thanks in advance,
    Al

T.R Title User Personal
Name Date Lines

82.1 MCC not a Client/Server CUSPID::MCCABE If Murphy's Law can go wrong .. Tue Mar 27 1990 10:36 8

T.R	Title	User	Personal Name	Date	Lines
82.1	MCC not a Client/Server	CUSPID::MCCABE	If Murphy's Law can go wrong ..	`Tue Mar 27 1990 10:36`	8
	MCC is not build in accordance with a client/server model. Each MCC invocation creates a process image into which all needed components are mapped. No network objects, IPC mechnisms etc exist. In the case you describe the remote user would access MCC via a RTEM (sethost).

    MCC is not build in accordance with a client/server model.  Each
    MCC invocation creates a process image into which all needed components
    are mapped.  No network objects, IPC mechnisms etc exist.
    
    In the case you describe the remote user would access MCC via a
    RTEM (sethost).