[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

960.0. "After upgrade to V1.4, EDIT CONFIG still shows V1.3" by 42441::SUMNERC (UK OpenVMS counter intelligence) Fri Sep 01 1995 06:02

    
    
    	     After upgrade to V1.4, EDIT CONFIG still shows V1.3
             ===================================================
    
    Hi I have a customer who has recently upgraded from V1.3 to V1.4
    of VCS.
    
    He has a VAX 4000-300 running VMS V5.5-2.
    
    
    This is what my customer reports...
    
    VCS starts okay and connection can be made to the serviced vaxes.  However 
    when you issue the command vcs edit configuration and then issue the 
    command show char you received the following output:-
    
    
    VCS EDIT> show char
    
    VAXcluster Console System  V1.3-000
    
    Input: SYS$COMMON:[SYSMGR]VCS$CONFIGURATION.DAT;113
    Output: SYS$COMMON:[SYSMGR]VCS$CONFIGURATION.DAT;
    
    Creator name         = SYSTEM
    Creation date        =  5-NOV-1990 12:45:36.04
    Last modified by     = KZ8XCG
    Last modified date   = 29-AUG-1995 15:53:18.25
    Logging:
       Archive procedure = SYS$MANAGER:VCS$ARCHIVE.COM
       Warning percent   = 2%
       Delete percent    = 1%
       Directory search list:
          OPPSMG_VCSLOGS
    Security:
       User              = Yes
       Display           = No
    Verify               = Yes
    
    
    Troubleshooting
    ===============
    o When we try that here at the support centre it shows as V1.4-000
    o He has restarted VCS.
    o He has rebooted (more then once).
    o He create a new edit file, by exiting.
    o We checked VCS images, all are V1.4-000 and these are the only
      revisions in his directory.  There modification date corresponds
      to the date of the upgrade.
    
    I'm know very little about VCS, but these seem the logical steps.  
    
    Is there a known issue ?  What else should we check.
    
    
    Thanks in advance,
    
    Chris Sumner
    OpenVMS Group
    UK CSC, Basingstoke 7833 3667
    
T.RTitleUserPersonal
Name
DateLines
960.142441::SUMNERCUK OpenVMS counter intelligenceTue Sep 05 1995 07:5111
    The customer has informed me that the problem has gone.
    
    After editing a scan file and reconfiguring the verison now
    shows up as V1.4.
    
    I'm not sure if that's the correct terminology but maybe it will
    help someone.
    
    Regards,
    
    Chris
960.2CSC32::BUTTERWORTHGun Control is a steady hand.Wed Sep 06 1995 16:368
    Thats because you wrote out a new version of the VCS$CONFIGURATION.DAT
    file. The version you were seeing was what was stored in the config file
    and not the version of the software. Lastly, does your customer realize
    how down-rev they are? I assume that they will be upgrading to PCM
    soon?
    
    Regs,
      Dan