[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

211.0. "Changing generic icons after upgrade from VCS." by THEFT::DAVE (Dave Lunn.) Fri Mar 11 1994 17:05

I have just upgraded from VCS 1.4 to the latest version of PCM and on the whole
I'd like to say well done - I like the feel and look of the new interface and
it's been very easy to get into it!

However, I seem to have encountered my first problem. On the issue of generic
icons - discussed in a previous topic - I have got to the stage where I am
trying to reset them and I don't seem to be able to do this.

I have made the changes in $CONSOLE EDIT/INTER=DECW and verified that the
changes have been stored in the database - but the C3 still displays generic
icons for the systems picked up from the VCS conversion... I have added two
new systems which are displaying the correct icons just fine.

I have tried $CONSOLE RECONFIG and a complete restart (in fact the whole system
was rebooted.)

Any ideas?

Thanks and regards,

Dave.
T.RTitleUserPersonal
Name		DateLines
211.1OPG::PHILIPAnd through the square window...Fri Mar 11 1994 18:0118
Dave,

  Thanks for the praise.

  Did you by any chance "save" your C3 configuration using
  "Save" on the "Options" menu? If so, this could be your
  problem, what you need to do is delete your C3 data file
  in your SYS$LOGIN: directory. Alternatively if you dont
  want to lose your customizations, you can edit this file
  and change the names of your Icons, the file layout should
  be fairly self explanatory.

  If this doesnt fix it, then I dont know whats wrong, maybe
  the guy who wrote the C3 does (Dave are you listening?).

Cheers,
Phil
211.2TO be fixedZENDIA::DBIGELOWInnovate, Integrate, EvaporateFri Mar 11 1994 18:336
    It's a bit of a bug which I'm going to fix straight away when I get
    back to work on Monday.
    
    Cheers,
    
       Dave
211.3Login files were the problem...THEFT::DAVEDave Lunn.Mon Mar 14 1994 10:4317
Thanks for the help - the login files were the cause of the problem...

While you're looking at fixing this, do I need to be explicit in saving my
configuration changes centrally or is it a once off problem that I'll never
see again?

Regards,

Dave.

PS:

>    It's a bit of a bug which I'm going to fix straight away when I get
>    back to work on Monday.

Impressive stuff!
211.4Light dawns...THEFT::DAVEDave Lunn.Mon Mar 14 1994 10:598
Ah... just realised that the files concerned are not configuration data files
but rather the text files you Import/Export - so I guess one of these in your
login area acts like a startup customization?

Time to read the documentation... 8?)

Dave.
211.5OPG::PHILIPAnd through the square window...Mon Mar 14 1994 12:0816
Dave,

  Something that you wont find in your current copy of
  the documentation...

  If you define the logical name CONSOLE$USER_DEFAULTS (environment
  variable CONSOLE_USER_DEFAULTS on the U*ix platforms) so that it
  points to a directory, then that directory will be used as the
  source for the reading of the C3 defaults and the destination of
  saves. This is the only way you are going to be able to define a
  common C3 for multiple users. As you have seen, if this logical is
  not defined the C3 files end up in SYS$LOGIN:

Cheers,
Phil