 |
HP OpenVMS System Management Utilities Reference
Manual
SHOW/DEVICE (VAX Only)
On VAX systems, displays full information about device drivers loaded
into the system, the devices connected to them, and their I/O
databases. All addresses are in hexadecimal and are virtual. On Alpha
and I64 systems, use the SYSMAN command IO SHOW DEVICE.
Use of the SHOW/DEVICE command requires the CMEXEC privilege.
Format
SHOW/DEVICE =device-driver
Parameters
None.
Qualifiers
None.
Description
The SHOW/DEVICE command specifies that the following information be
displayed about the specified device driver:
|
Driver
|
Name of the driver
|
|
Start
|
Starting address of the driver
|
|
End
|
Ending address of the driver
|
|
Dev
|
Name of each device connected to the driver
|
|
DDB
|
Address of the device's device data block
|
|
CRB
|
Address of the device's channel request block
|
|
IDB
|
Address of the device's interrupt dispatch block
|
|
Unit
|
Number of each unit on the device
|
|
UCB
|
Address of each unit's unit control block
|
By default, if you omit the driver name, information is displayed for
all device drivers loaded into the system.
Example
|
SYSGEN> SHOW/DEVICE=DBDRIVER
|
This command displays the following information about the DBDRIVER:
__Driver_____Start____End____Dev___DDB______CRB______IDB_____Unit__UCB___
DBDRIVER 80082390 80082A7E
DBA 80000848 800988C0 80098920
0 8000087C
1 8008A4F0
2 8008A590
5 8008A630
7 8008A6D00
|
SHOW/DRIVER (VAX Only)
On VAX systems, displays the starting and ending address of the
specified device driver loaded into the system.
Format
SHOW/DRIVER =device-driver
Parameters
None.
Qualifiers
None.
Description
If you omit the driver name, SHOW/DRIVER displays the starting and
ending address of all device drivers loaded into the system. All
addresses are in hexadecimal and are virtual.
Use of the SHOW/DRIVER command requires the CMEXEC privilege.
The SHOW/DRIVER command displays the following information about the
specified device driver:
|
Driver
|
Name of the device driver
|
|
Start
|
Starting address of the device driver
|
|
End
|
Ending address of the device driver
|
Example
This command displays the starting and ending addresses of all drivers,
as follows:
__Driver_____Start____End___
RTTDRIVER 800C1060 800C1960
NETDRIVER 800BAFD0 800BD4B0
TMDRIVER 800B3950 800B4BF0
DRDRIVER 800B2950 800B3290
DDDRIVER 800B1740 800B2060
DLDRIVER 800B0D10 800B15A0
DMDRIVER 800B0070 800B0990
LCDRIVER 800AFC50 800AFFB0
YCDRIVER 800AED20 800AF3E0
XGDRIVER 800AC3F0 800AE9E0
XDDRIVER 800AA5A0 800AC380
DZDRIVER 800A4F30 800A59B0
XMDRIVER 800A3E10 800A4A50
DYDRIVER 800A3300 800A3C30
LPDRIVER 800A2E90 800A3300
DBDRIVER 800DE7A0 800DEFB7
TTDRIVER 800DC770 800DE79B
OPERATOR 80001650 80001F8B
NLDRIVER 80001626 80001D20
MBDRIVER 800015FC 80001CBE
|
SHOW/STARTUP
Displays the name of the current site-independent startup command
procedure.
Format
SHOW/STARTUP
Parameters
None.
Qualifiers
None.
Example
|
SYSGEN> SHOW/STARTUP
Startup command file = SYS$SYSTEM:STARTUP.COM
|
This command displays the name of the site-independent startup command
procedure.
SHOW/TURBOCHANNEL (VAX Only)
On VAX systems, displays the nexus number of a device on the
TURBOchannel.
Format
SHOW/TURBOCHANNEL
Parameters
None.
Qualifiers
None.
Example
|
SYSGEN> SHOW/TURBOCHANNEL
|
The following example is a sample display produced by the
SHOW/TURBOCHANNEL command:
TURBOCHANNEL: Device Name Nexus Number TC Slot
PMAQT-AA 00000000 00000001
|
SHOW/UNIBUS (VAX Only)
On VAX systems, displays the addresses in UNIBUS I/O space that can be
addressed.
Use of the SHOW/UNIBUS command requires the CMKRNL privilege.
Format
SHOW/UNIBUS
Parameters
None.
Qualifier
/ADAPTER=nexus
Specifies that the address of the specified UNIBUS adapter is to be
displayed. The nexus value specifies the number of the UNIBUS adapter.
It can be expressed as an integer or as one of the names listed by the
SYSGEN command SHOW/ADAPTER.
Description
The SHOW/UNIBUS command reads all device registers. For some
controllers, the result might be reading a character out of a buffer or
some other undesired action. Therefore, use the SHOW/UNIBUS command
only when you debug a UNIBUS configuration. On a system with more than
one UNIBUS adapter, the command shows only the address of the first
UNIBUS adapter.
Note
Never use the SHOW/UNIBUS command on a running system. Use of this
command is valid only during a conversational bootstrap.
|
Example
|
SYSGEN> SHOW/UNIBUS/ADAPTER=4
|
This command displays the available addresses for nexus 4, as follows:
**UNIBUS map for nexus #4 on 30-JUN-2002 14:19:38.00 **
Address 760070 (8001F838) responds with value 9B6E (hex)
Address 760072 (8001F83A) responds with value 0340 (hex)
Address 760074 (8001F83C) responds with value 403C (hex)
Address 760076 (8001F83E) responds with value 0240 (hex)
Address 760100 (8001F840) responds with value 8000 (hex)
Address 760102 (8001F842) responds with value 0340 (hex)
Address 760104 (8001F844) responds with value 7DAC (hex)
Address 760106 (8001F846) responds with value 000A (hex)
Address 760110 (8001F848) responds with value 8000 (hex)
Address 760112 (8001F84A) responds with value 0340 (hex)
Address 760114 (8001F84C) responds with value AD5C (hex)
Address 760116 (8001F84E) responds with value 000A (hex)
Address 760130 (8001F858) responds with value 9B6E (hex)
Address 760132 (8001F85A) responds with value 030D (hex)
Address 760134 (8001F85C) responds with value FF00 (hex)
Address 760136 (8001F85E) responds with value CECE (hex)
Address 760140 (8001F860) responds with value 4060 (hex)
Address 760142 (8001F862) responds with value 0761 (hex)
Address 760144 (8001F864) responds with value FF00 (hex)
.
.
.
|
TERMINAL
Modifies the Ctrl/C, Ctrl/O, Ctrl/Y, and Ctrl/Z echo strings on a
systemwide basis.
Format
TERMINAL/ECHO
Parameters
None.
Qualifiers
None.
Description
Before entering the TERMINAL command, edit the file SYSGTTSTR.MSG in
SYS$EXAMPLES. The file contains detailed instructions for the editing
procedure.
When you enter the TERMINAL command after editing the file, the
modifications you have specified are carried out.
USE
Initializes the SYSGEN work area with system parameter values and the
name of the site-independent startup command procedure, overwriting
existing values. The initial values of the SYSGEN work area when the
utility is invoked are the active values.
Specify the source for both the parameter values and the procedure
name. They can be retrieved from a parameter file, the current system
parameter file on disk, the active system in memory, or the default
list.
Format
USE file-spec
Parameters
file-spec
The file specification of a system parameter file from which data is to
be retrieved. You can use the SYSGEN command WRITE to create the
parameter file. The default file type is .PAR.
In place of a file specification, you can specify one of the following
keywords:
CURRENT
Specifies that source information is to be retrieved from the current
system parameter file on disk.
On VAX systems, the system parameter file is SYS$SYSTEM:VAXVMSSYS.PAR.
On Alpha systems, the system parameter file is
SYS$SYSTEM:ALPHAVMSSYS.PAR.
On I64 systems, the system parameter file is SYS$SYSTEM:IA64VMSSYS.PAR.
ACTIVE
Specifies that source information is to be retrieved from the active
system in memory.
DEFAULT
Specifies that source information is to be retrieved from the default
list. The USE DEFAULT command initializes the SYSGEN work area with
parameter values that are built into SYSGEN; these values allow the
operating system to boot on any standard configuration.
To avoid starting all layered products on a system that is not tuned
for them, possibly causing the system to hang, set the STARTUP_P1
system parameter as follows:
SYSGEN> SET STARTUP_P1 "MIN"
|
Qualifiers
None.
Examples
| #1 |
SYSGEN> USE SYS$SYSTEM:SPECIAL
|
This command uses the existing parameter file SYS$SYSTEM:SPECIAL.PAR.
| #2 |
SYSGEN> USE DEFAULT
SYSGEN> SET STARTUP_P1 "MIN"
|
The first command initializes the SYSGEN work area with default
parameter values. The second command sets the STARTUP_P1 system
parameter to "minimum."
WRITE
Writes the system parameter values and the name of the site-independent
startup command procedure from the SYSGEN work area to a parameter
file, the current system parameter file on disk, or the active system
in memory.
Format
WRITE file-spec
Parameters
file-spec
The file specification of a new parameter file to be created. The
default file type is .PAR.
In place of a file specification, you can specify one of the following
keywords:
CURRENT
Specifies that source information is to be written to the current
system parameter file on disk.
On VAX systems, the system parameter file is SYS$SYSTEM:VAXVMSSYS.PAR.
On Alpha systems, the system parameter file is
SYS$SYSTEM:ALPHAVMSSYS.PAR.
On I64 systems, the system parameter file is SYS$SYSTEM:IA64VMSSYS.PAR.
Use of the WRITE CURRENT command requires the SYSPRV privilege.
ACTIVE
Specifies that source information is to be written to the active system
in memory. (Only the dynamic parameter values are written to the active
system.)
Use of the WRITE ACTIVE command requires the CMKRNL privilege.
Qualifiers
None.
Description
On VAX systems, the implementation of security auditing within SYSGEN
has altered the reporting of modifications to the system parameter file
VAXVMSSYS.PAR. System managers can receive notification of a change to
the file by setting up an access control list (ACL) on the file to
signal such an event, as in the following example:
$ SET SECURITY/ACL=(ALARM=SECURITY,ACCESS=WRITE+FAILURE+SUCCESS)-
_$ SYS$SYSTEM:VAXVMSSYS.PAR
|
For more information about setting ACLs, refer to the OpenVMS User's Manual and
the HP OpenVMS Guide to System Security.
On Alpha and I64 systems, both the WRITE ACTIVE and WRITE CURRENT
commands send a message to OPCOM and log the event.
Examples
| #1 |
SYSGEN> WRITE SYS$SYSTEM:SPECIAL
|
This command creates a new parameter specification file,
SYS$SYSTEM:SPECIAL.PAR.
On VAX systems, this command modifies the current system parameter file
on disk, VAXVMSSYS.PAR.
On Alpha systems, this command modifies the current system parameter
file on disk, ALPHAVMSSYS.PAR.
On I64 systems, this command modifies the current system parameter file
on disk, IA64VMSSYS.PAR.
Chapter 21
System Management Utility
The System Management utility (SYSMAN) centralizes the management of
nodes and cluster environments. Rather than logging in to individual
nodes and repeating a set of management tasks, SYSMAN enables you to
define your management environment to be a particular node, a group of
nodes, or a cluster environment. With a management environment defined,
you can perform system management tasks from your local node. SYSMAN
executes these tasks on all nodes in the target environment.
Managing a system with SYSMAN is similar to the traditional management
of an individual system because SYSMAN uses many of the same software
tools. It can process most DCL commands, such as MOUNT, DEFINE,
INITIALIZE, SET, and SHOW. It can also execute many OpenVMS system
management utilities and command procedures, such as AUTHORIZE,
AUTOGEN, and INSTALL.
SYSMAN also contains system management tools that let you perform the
following tasks:
- Set disk quotas using DISKQUOTA commands.
- Load and unload licenses using LICENSE commands.
- Associate a terminal or port with a user name using the automatic
login facility (ALF) commands.
- Modify or display System Generation utility (SYSGEN) parameters
using PARAMETERS commands.
- Build site-specific startup procedures using STARTUP commands,
which display or modify startup components of the OpenVMS operating
system, site-specific programs, and layered products.
- Modify or display OpenVMS Cluster parameters using CONFIGURATION
commands.
- Load system services using SYS_LOADABLE commands, which add and
remove executive loaded images from the set of images loaded at boot
time.
- Create and modify scheduling classes, which allow you to limit the
amount of CPU time alloted to users on a system.
- Shut down systems using the SHUTDOWN NODE command.
- On Alpha and I64 systems, detect all previously undiscovered tapes
and media changers.
- On Alpha and I64 systems, connect devices, load device drivers, and
display configuration information using I/O commands.
- On Alpha and I64 systems, set the priority of processes so that
they are dumped early during a selective dump.
21.1.1 Defining Keys to Execute SYSMAN Commands
Instead of having to type lengthy command lines, SYSMAN enables you to
define keys to execute SYSMAN commands. For example, you can define a
key to execute a SET ENVIRONMENT command as follows:
SYSMAN> DEFINE/KEY/TERMINATE
_Key name: KP0
_Translation: "SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23)"
|
Once the key is defined, you can press keypad 0, and SYSMAN executes
the SET ENVIRONMENT command. Note that key definitions are lost each
time that you exit from SYSMAN, unless you define them in the SYSMAN
initialization file. (See Section 21.1.2 for more information about
executing commands from an initialization file.)
You can create an initialization file that SYSMAN will use each time
you invoke the utility. In the SYSMAN initialization file, you can
perform tasks such as defining keys and setting the SYSMAN environment.
The default file specification for the SYSMAN initialization file is
SYS$LOGIN:SYSMANINI.INI. If you want your SYSMAN initialization file to
have a different file specification, you must define the logical name
SYSMANINI to point to the location of the file.
The following example is a sample initialization file in which several
keys are defined:
$ TYPE SYSMANINI.INI
DEFINE/KEY/TERMINATE KP0 "SET ENVIRONMENT/CLUSTER/NODE=(NODE21,NODE22,NODE23,NODE24)"
DEFINE/KEY/TERMINATE KP1 "CONFIGURATION SHOW TIME"
DEFINE/KEY/TERMINATE KP2 "SHOW PROFILE"
.
.
.
|
21.2 SYSMAN Usage Summary
The System Management utility (SYSMAN) centralizes system management,
enabling you to manage nodes or clusters from one location.
Format
RUN SYS$SYSTEM:SYSMAN
Parameters
None.
Description
To invoke SYSMAN, enter the following command at the DCL prompt:
SYSMAN displays the following prompt at which you can enter SYSMAN
commands using the standard rules of DCL syntax:
To exit from SYSMAN and return to the DCL command level, enter the EXIT
command at the SYSMAN> prompt or press Ctrl/Z.
Note
SYSMAN has the following restrictions:
- You must have the OPER privilege on the local node and
authorization for the OPER or SETPRV privilege on any remote nodes in
the management environment.
You must also have the privileges
required by individual commands, as each command in this chapter
describes. To determine which privileges are required for DCL commands
or for system management utilities, refer to the HP OpenVMS DCL Dictionary or the
appropriate utility reference part of this manual.
- You cannot run SYSMAN from a batch job in any environment that
requires a password.
- Some DCL commands, such as SHOW SYSTEM/CLUSTER, SET CLUSTER/QUORUM,
MOUNT/CLUSTER, and some forms of the REPLY command, operate clusterwide
by design. These commands should not be run using SYSMAN, unless the
environment has been set to a single node. Similarly, operations on
clusterwide logical names and tables operate clusterwide by design.
- If a SYSMAN user running with more than 125 total rights attempts
to issue a SYSMAN command to a remote node within a cluster, the
following error message is displayed:
SMI-E-RIGHTSLIM, Rights limit exceeded.
|
Note that this rights limitation includes a minimum of three
identifiers that are granted during login when the process rights list
is created:
- A UIC identifier
- A system identifier
- Depending upon the environment in which the process is operating,
at least one environmental identifier
Users who want to run SYSMAN must have either one of the following
items:
- A separate account with no more than 125 rights
- Enough identifiers removed from their current account so that the
total number of rights falls within the appropriate range
|
|
