Article View: vmsnet.sysmgt
Article #64Re: System Tuning
From: Richard Wiseman - VAX/VMS Crafts...
Date: Sat, 07 Nov 1992 00:26
Date: Sat, 07 Nov 1992 00:26
103 lines
4682 bytes
4682 bytes
In article <1992Oct28.174438.266@logica.co.uk>, system@logica.co.uk writes: > OPEN QUESTIONS TO ALL NEWS READERS > > 3. > Does anyone know the full table of classes for OPC$OPA0_CLASSES as the > manual is not available. Here is the standard listing out of sylogicals.template $! $! The state of the operator on OPA0:, and the state of the operator logfile, $! can be controlled by defining logical names here in SYLOGICALS.COM. Any $! commands to enable or disable operator classes in other system startup $! procedures should be removed, and the appropriate logical names defined here. $! $! By default, the operator states are: $! $! For all systems except workstations in a VAXcluster: $! $! OPA0: is enabled for all classes. $! The log file SYS$MANAGER:OPERATOR.LOG is opened for all classes. $! $! For workstations in a VAXcluster: $! $! OPA0: is not enabled.* $! No log file is opened. $! $! * OPA0: will be also be SET TERMINAL/PERMANENT/NOBROADCAST $! $! To override the default enabled classes, define the following /SYSTEM $! logical names. $! $! OPC$OPA0_ENABLE $! $! If defined to be true, then OPA0: is enabled as an operator. If $! defined to be false, then OPA0: is not enabled as an operator. $! $! OPC$OPA0_CLASSES $! $! This logical defines the operator classes to be enabled on $! OPA0:. The logical can be a search list of the allowed $! classes, a list of classes, or a combination of the two, for $! example: $! $! $ DEFINE /SYSTEM OPC$OPA0_CLASSES CENTRAL,DISKS,TAPE $! $ DEFINE /SYSTEM OPC$OPA0_CLASSES "CENTRAL,DISKS,TAPE" $! $ DEFINE /SYSTEM OPC$OPA0_CLASSES "CENTRAL,DISKS",TAPE $! $! Note that OPC$OPA0_CLASSES can be defined even if OPC$OPA0_ENABLE is $! not defined. In that case, the classes are used for any operators $! that are enabled, but the default is used to determine whether or not $! to enable the operator. $! $! OPC$LOGFILE_ENABLE $! $! If defined to be true, then an operator log file is opened. $! If defined to be false, then no log file is opened. $! $! OPC$LOGFILE_CLASSES $! $! This logical defines the operator classes to be enabled for $! the log file. The logical can be a search list of the allowed $! classes, a comma-separated list, or a combination of the two. $! OPC$LOGFILE_CLASSES can be defined even if OPC$LOGFILE_ENABLE $! is not defined. $! $! OPC$LOGFILE_NAME $! $! This logical supplies information to be used in conjunction $! with the default name SYS$MANAGER:OPERATOR.LOG to define the $! name of the log file. If the log file is directed to a disk $! other than the system disk, commands to mount that disk should $! be included in the command procedure SYLOGICALS.COM. This $! logfile name will be used whenever a logfile is recreated. $! $! Note that only OPC$LOGFILE_NAME is used for more than the initial $! startup of OPCOM. For example, issuing the command REPLY/LOG will $! open a new file with the specified name and with all classes enabled $! (OPC$LOGFILE_ENABLE and OPC$LOGFILE_CLASSES are ignored). $! $! The list of all operator classes is: $! $! CENTRAL,PRINTER,TAPES,DISKS,DEVICES,CARDS,NETWORK,CLUSTER, $! SECURITY,LICENSE,OPER1,OPER2,OPER3,OPER4,OPER5,OPER6, $! OPER7,OPER8,OPER9,OPER10,OPER11,OPER12 $! $! Operator classes can be redefined via logical names. For example, a site $! could decide that the site-specific operator OPER1 should be known as $! operator class SYSTEM_MANAGER. This would be done via: $! $! $ DEFINE /SYSTEM SYSTEM_MANAGER OPER1 $! $! Thereafter, the system manager could do a REPLY/ENABLE=SYSTEM_MANAGER, $! users could do REQUEST /TO=SYSTEM_MANAGER, etc. $! $! ...rew -- -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Richard Wiseman VAX-VMS Crafts Person MONSANTO Internet: Rewise@musctn.monsanto.com RR #5 Wiggins Rd. Yellnet: +1 (319)262-7528 or 262-7339 BOX 473 FAX: +1 (319)262-5626 Muscatine, Ia 52761 Disclaimer: All opinions are my own, I think -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Technical Details
Message-ID:
<1992Nov7.002658.1@musctn.monsanto.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!wupost!monsanto.com!bb1t.monsanto.com!musctn.monsanto.com!rewiseReferences:
<1992Oct28.174438.266@logica.co.uk>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!wupost!monsanto.com!bb1t.monsanto.com!musctn.monsanto.com!rewise Newsgroups: vmsnet.sysmgt Subject: Re: System Tuning Message-ID: <1992Nov7.002658.1@musctn.monsanto.com> From: rewise@musctn.monsanto.com (Richard Wiseman - VAX/VMS CraftsPerson) Date: 7 Nov 92 00:26:58 GMT References: <1992Oct28.174438.266@logica.co.uk> Nntp-Posting-Host: llg013 Nntp-Posting-User: drboll Lines: 103