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

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

977.0. "2 databases, same executables, on cluster ?" by 52336::STRATMAN (Peter Stratman @VBO) Thu Sep 14 1995 04:11

    Customer question: Can I have 2 separate PCM databases on my cluster ?
    One node would have the production database, the other would have a test
    database where I can develop scan profiles, actions filtes, etc,
    reconfigure easily without disturbing the operators. Both nodes would
    share executables.

    Will this work ?


    Thank you,
    Peter.
T.RTitleUserPersonal
Name
DateLines
977.1ZENDIA::DBIGELOWInnovate, Integrate, EvaporateThu Sep 14 1995 11:5724
    No. PCM uses this database to define the systems, users, etc and you
    can't have 2 versions of the PCM images running at the same time.
    
    You can develop scan profiles and action routines on the same system if
    you use a pseudo terminal. In the 'Command to run' you can enter
    the editor you most frequently use, such as tpu. You can now connect
    to the editor and type anything you want. PCM will think that you
    are logged into a console. I've done this quite extensively to test
    scan definitions. If you use the pseudo terminal, I've found that I
    had to do a control W to clear the screen when the connection to the 
    pseudo-terminal (editor) is first made. The only down side to this
    is that you will have to do a lot of PCM Reconfigure commands 
    to enable your commands. PCM goes through a lot of code to do a
    reconfigure and, in the long run, may or may not cause problems 
    for other users.
    
       A better solution would be to put PCM on another system and create
    the pseudo terminal there. When you are satisfied with your new
    definitions, you can 'export' these new definitions from within the
    editor. This creates an ascii text file which you can then copy over
    to the PCM productions system and 'Import' the new definitions, make
    any necessary changes (if need be) and then reconfigure. Bingo.
    
    Dave 
977.2CSC32::BUTTERWORTHGun Control is a steady hand.Thu Sep 14 1995 12:2311
    Dave has already given you the best solution. You could do what you
    want but it would require some unsupported modifications to the
    software namely the logical name definitions for CONSOLE$TMP and
    CONSOLE$DATA. You would have to change the CONSOLE$LOGICALS.COM file on
    the development box so that CONSOLE$TMP and CONSOLE$DATA point to
    different directories. This would allow the data and temporary files
    for the devlopment box to be kept separate from the production system.
    To retiterate, this is *totally unsupported*.
    
    Regs,
      Dan
977.3mmm...52336::STRATMANPeter Stratman @VBOFri Sep 15 1995 05:3610
Dave, (.1) I guess that you thought I wanted to run a developement and
production environment on the same CPU. I want to use a cluster to separate the
2 environments, while sharing the already installed exe's.

Dan (.2) you get the idea. I suppose the only problem is shared global sections
etc. if I do this on a cluster. Since PCM is still non-clusterwide (right?) like
VCS this should not be a problem (or will it ?)

Thanks to both of you,
Peter.
977.4CSC32::BUTTERWORTHGun Control is a steady hand.Fri Sep 15 1995 12:066
    PCM is cluster safe. The global sections are node-specific so no
    problem there. The problem with VCS was really the names used for the
    locks for one of the pipes.
    
    REgs,
      Dan