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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2301.0. "PCSA and DECwindows licensing ?" by NEEPS::NORRIE (Norrie Mackay, Aberdeen) Mon Feb 19 1990 09:54

    Hi
    
    I have a customer who has concerns around the use of windows and
    and whether firing up a window reduces your license count by one.
    This applies to the use of PCSA and DECwindows ie. if I have a 4   
    user license on the VAX with 4 PC's hanging of the server, then are 
    there any limitations to the amount of windows a user can fire up on 
    his PC.  
                                                                         
    I have read note 421.* and related notes and am still a bit confused
    so apologies if I have missed the obvious.
    
    Thanks for your time.
    
    
    Norrie
T.RTitleUserPersonal
Name		DateLines
2301.1I believe the answer is...MACGPX::MOYMike Moy, NJCD SWS=>DTN 323-4466Wed Feb 21 1990 09:2111
    I believe the answer to your question is no, invoking PC
    DECwindows and then running an application thru the PC DECwindows
    application invoker does not reduce the number of interactive logins to
    the client node.  This is because you are not using a login to run the
    application - but a DECnet task to task object.
    
    However, keep in mind that PC DECwindows does require quite a bit of
    resources on the PC side and unless your customer is using a 386 class
    PC, they won't be able to get too many remote applications going.
     
    mike
2301.2PCDW works fine on a 286...SPCTRM::GORCZYCAFri Feb 23 1990 16:2035
>    I believe the answer to your question is no, invoking PC
>    DECwindows and then running an application thru the PC DECwindows
>    application invoker does not reduce the number of interactive logins to
>    the client node.  This is because you are not using a login to run the
>    application - but a DECnet task to task object.
>

I will also try to find someone who can provide the definitive answer to this
question which seems to have been open for months now.  (I fear, however, that
the above answer is correct (for now) which means that you wouldn't need many
VMS user licenses if you had many interactive user's using PC DECwindows.)

>    However, keep in mind that PC DECwindows does require quite a bit of
>    resources on the PC side and unless your customer is using a 386 class
>    PC, they won't be able to get too many remote applications going.
>

PC DECwindows does require a *** 286 *** class machine and also requires about
2-3 megabytes of local memory to be useful.  With 2 megs, I can run LOTS of
CERTAIN kinds of remote applications.  With 2 megs (and color) it is PAINFUL
to run even one copy of DECwrite.  (With 3 megs, its fine, though.)  

The real key to a pleasant PC DECwindows experience is memory.  Most 
applications use only a little or a moderate amount, but a few, like DECwrite,
use LOTS.

Please refer to the MOSAIC::PCDECWINDOWS notes file for more timely info on this
product.  If you want to see what's happenin' in the OS/2 world wrt DECwindows
support, please refer to the MOSAIC::PMX notes file.  

John