Conference ulysse::rdb_vms_competition

791.0. "FYI - Mixed Licenses on Clusters" by NOVA::HORN (Steve Horn, Database Systems) Fri Nov 09 1990 15:48

    
    
                <<< NOVA::DVD12:[NOTES$LIBRARY]RDB_31.NOTE;1 >>>
                    -< Rdb/VMS V3.1 - first in the 1990's >-
================================================================================
Note 1262.7                full and rto lic on cluster                   7 of 20
NOVA::HORN "Steve Horn, Database Systems"            60 lines   6-NOV-1990 16:04
                            -< The SUPPORTED way: >-
--------------------------------------------------------------------------------
    
    
    As promised here is the 'official' supported way to install Rdb/VMS
    to support both Development nodes and RTO nodes on a cluster with a
    common system disk.
    
    -Steve
    
    =====================================================================
+---------------------------+TM
|   |   |   |   |   |   |   |
| d | i | g | i | t | a | l |              TIME DEPENDENT CASE	
|   |   |   |   |   |   |   |
+---------------------------+


 
      TITLE: How To Use Rdb/VMS Development and Run Time Only In A VAXcluster

            					DATE:  2-NOV-1990

      AUTHOR: Chris Davis   	                TD #:
      DTN: 523-2886
      ENET: COOKIE::C_DAVIS                     CROSS REFERENCE #'s:
      DEPARTMENT:  CSSE TP/IM                   (PRISM/TIME/CLD#'s)  

      INTENDED AUDIENCE: ALL                    PRIORITY LEVEL: 2
      (U.S./EUROPE/GIA)                         (1=TIME CRITICAL,
                                                 2=NON-TIME CRITICAL)
      =====================================================================

 
It is possible to mix licenses for Rdb/VMS Development (DEV) and 
Rdb/VMS Run Time Only (RTO) in a VAXcluster. The procedure is not
obvious for Rdb/VMS V3.1 or T4.0 but further investigative work is being 
done in this area.  

For now you can do the following if you have the Rdb/VMS DEV kit. 

    1.  Install the Development PAK (RDB) on the VAXcluster using LMF commands.

    2.  Install the Development kit on the common system disk using
        SYS$UPDATE:VMSINSTAL.COM (default installation action for Rdb/VMS).
   
    3.  Pull the image RTORDO.EXE from saveset B using VMS BACKUP.

    4.  Copy the RTORDO.EXE image as RDO.EXE in SYS$SPECIFIC on the
        Runtime Only nodes.

    5.  Do a LICENSE/MODIFY/EXCLUDE=node_name RDB  where node_name is the
        name(s) of a node which will run RTO.

The major side effect of the above procedure is that installing new versions
of the software will not consider the above scheme.  If you do the above on
Rdb/VMS V3.1B and some time later install Rdb/VMS V4.0, the installation
procedure will not put a new RDO.EXE in SYS$SPECIFIC on the RTO nodes.  Also the
above does not account for any changes in Rdb/VMS after V4.0.  In both cases,
some effort should be made to document the above changes so that future
installations or future system managers are aware of the above.