[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

675.0. "How to establish a "common" CONSOLE$C3.DAT?" by CSC32::D_DONOVAN (SummaNulla(The High Point of Nothing)) Wed Apr 12 1995 18:01

	I looked for a previous discussion of this but couldn't find one so...

	The customer I am currently working and others would like to establish
a "common" CONSOLE$C3.DAT for his operators.  I have told him about not being 
able to prevent privileged users to customize their own C3 views but he feels 
that he can control this.  Now, if you place a CONSOLE$C3.DAT in 
"DECW$SYSTEM_DEFAULTS:" would this suffice in providing a "common" C3 display?

Thanks,

Dennis
T.RTitleUserPersonal
Name		DateLines
675.1CSC32::BUTTERWORTHGun Control is a steady hand.Wed Apr 12 1995 19:1117
    >Now, if you place a CONSOLE$C3.DAT in "DECW$SYSTEM_DEFAULTS:" would this 
    >suffice in providing a "common" C3 display?
    
    What you must do is define the logical name CONSOLE$USER_DEFAULTS
    to point to a directory that all the operators have read access too.
    The place the common CONSOLE$C3.DAT in there. Of course you must define
    it in a shareable logical name table that all the operator accounts
    search by default. The point here is that you may not just want to use
    the system table if you want different people to see different things,
    e.g. suppose you had some operators responsible for one set of systems
    and another group handles another, you could define their accounts
    in the UAF with different group UIC's. You would then set the value of
    CONSOLE$LOGICAL_NAMES to point to the correct place for that particular
    group.
    
    Regs,
      Dan
675.2RTFSACSC32::D_DONOVANSummaNulla(The High Point of Nothing)Wed Apr 12 1995 21:2966
re: .1 

	Thanks Dan.  I was pointed to a STARS Article that discusses this also 
(see below).  Seems that it has been discussed before ;-}.

Dennis

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[PLY_CM] How To Setup a Common Console Manager C3 View

     Any party granted access to the following copyrighted information
     (protected under Federal Copyright Laws), pursuant to a duly executed
     Digital Service Agreement may, under the terms of such agreement copy
     all or selected portions of this information for internal use and
     distribution only. No other copying or distribution for any other
     purpose is authorized.

Copyright (c) Digital Equipment Corporation 1994.  All rights reserved.

PRODUCT:    POLYCENTER Console Manager (PCM) Versions 1.1, 1.5

OP/SYS:     OpenVMS VAX
            OpenVMS AXP 

SOURCE:     Digital Equipment Corporation


BACKGROUND:

When a user generates a CONSOLE C3, the file CONSOLE$C3.DAT is created
in the user's default login directory.  This allows each user to have
a customized C3 view based on personal preference.  


QUESTION:

How does PCM allow multiple users to have the same C3 view?

 
ANSWER:

Define the logical CONSOLE$USER_DEFAULTS to point to a directory that
contains the common CONSOLE$C3.DAT resource file.  The logical
definition may be placed in the LOGIN.COM file for each user sharing a
C3 configuration view:

     $ DEFINE CONSOLE$USER_DEFAULTS directory_specification

Several other user interface files will also be redirected to the
location of the resource file.  The CONSOLE commands impacted:

     C3

          CONSOLE$C3.DAT
          CONSOLE$C3_username_MSG.LOG
  
     CONNECT/MONITOR

          CONSOLE$MONITOR_INIT.DAT
          CONSOLE$scriptname.SCRIPT

     EVENTLIST (If $ CONSOLE EVENTLIST /param/param/param issued)

          CONSOLE$EVENTLIST.DAT