Conference csc32::consolemanager

138.0. "problems with CONSOLE manager on VMS" by BACHUS::WILLEMSG () Mon Nov 29 1993 10:49

    
    
    
  
    	Hello,
    
    	I installed PCM on my test system. At the end of the installation
    	I recieved some information about an input file. Do you know
    	what went wrong ?
    
    
    
    Starting the POLYCENTER Console Manager Post installation tasks.


   Checking for existing database file....

   Creating system default database file....



Copyright (C) 1992,1993 Digital Equipment Corporation. All Rights Reserved

Cannot open input file: CONSOLE$DATA:CONSOLE_CFG.DAT


Action (Broadcast) type not defined, setting to EACH event and EACH userdata

        Installation of CONSOLE V1.1 completed at 11:21


        VMSINSTAL procedure done at 11:21


    
    
    
    
    	I started the console$startup and did a $CONSOLE C3.
    	I got the C3-Edit Mode window. When clicken on commands Console
    	Manager Editor I received :
    $ console c3
    Execute :
    CONSOLE EVENTLIST -
         /NODE=0 -
         /SERVER=0 -
         /SCREEN=0 -
         /TRANSPORT=LOCAL
    C3 Message log file: sys$sysroot:[sysmgr]cm_c3_SYSTEM_output.log
    %DCL-W-MAXPARM, too many parameters - reenter command with fewer
    parameters
    %DCL-W-MAXPARM, too many parameters - reenter command with fewer
    parameters
    BUG: shared memory not returning correct status for disabled line
    
    The last message I recieve when doing Console Manager System Tallies.
    
    
    I must admit that this is the first try with PCM.
    
    B.T.W. Are the new manuals available, because the one I copied
    (2 or 3 weeks ago) did say much about how to setup the PCM.
    
    
    Any feedback is welcome.
    
    Thanks in advance,
    
    Geert Willems {VMS and Polycenter products(VCS,Scheduler,PSW,DCM,...)
    		   customer support}

    Hi,
    sorry we are slow in replying as we are in the US doing the pre EFT
    training.
    
    The first is not a problem as we are loading the template database. I
    shall put something to  either disable the message or note above that
    it is not a problem.
    
    There are still several bugs and debug messgaes enabled in the current
    kit. So these messages may occur. Please bear with us.
    
    Cheers Simon....