| United States-English |
|
|
|
![]() |
HP OpenVMS Systems Documentation |
Compaq Advanced Server for OpenVMSCommands Reference ManualOrder Number: AA--R6G5C--TE
March 2001
This manual provides command syntax descriptions for all ADMINISTER commands available with the Advanced Server for OpenVMS. Revision/Update Information: This manual supersedes the Commands Reference Manual, AA--R6G5B--TE.
Operating System Version:
OpenVMS Alpha Version 7.2-1, 7.1-2, 6.2
Software Versions:
Advanced Server V7.3 for OpenVMS
© 2001 Compaq Computer Corporation Compaq, the Compaq logo, VAX, and VMS Registered in U.S. Patent and Trademark Office. AlphaStation, DEC, DECnet, DECwindows, PATHWORKS, OpenVMS, and POLYCENTER are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries.
Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft
Corporation in the United States and other countries.
All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
ZK6544 The Compaq Advanced Server for OpenVMS documentation set is available on CD-ROM.
PrefaceWelcome to the Compaq Advanced Server for OpenVMS Commands Reference Manual. For the purposes of this text, the product is referred to as the Advanced Server. The information presented in this guide is equally applicable to:
Usage of the term "Advanced Server" in this manual refers to either version of the file and print server, except when the text explicitly specifies a version number. The Advanced Server and its associated OpenVMS system platform provide a powerful, reliable, and open operating environment that meets the demands of client/server computing. This manual provides reference material to help you manage and maintain your network using the Advanced Server ADMINISTER command-line interface. Intended AudienceThis manual is for the Advanced Server for OpenVMS server administrator. As the administrator, you must be familiar with the Compaq OpenVMS operating system to support the server and with other operating systems to support clients. It is also expected that you have experience doing network administration, and that you are familiar with OpenVMS DCL command language syntax and the specific network configuration being managed. You are assumed to have read the other documents in the Advanced Server for OpenVMS set and to have access to documentation for any clients running other operating systems. Document StructureThis document contains the following chapters:
Related DocumentsThe following table lists related Advanced Server for OpenVMS documents:
The following table lists related PATHWORKS for OpenVMS (Advanced Server) documents:
The following table lists related Compaq OpenVMS documents:
For additional information about OpenVMS products and services, access the following World Wide Web address:
Reader's CommentsCompaq welcomes your comments on this manual. Please send comments to either of the following addresses:
How To Order Additional DocumentationUse the following World Wide Web address to order additional documentation:
If you need help deciding which documentation best meets your needs, call 800-282-6672. ConventionsThe following conventions are used in the Advanced Server documentation set:
Chapter 1
|
$ ADMINISTER HELP |
You control many aspects of the Advanced Server with the ADMINISTER command-line interface. You can invoke the ADMINISTER user interface in one of two ways:
$ ADMINISTER LANDOFOZ\\TINMAN> |
$ ADMINISTER SHOW SHARES Shared resources on server "TINMAN": Name Type Description ------------ --------- ----------------------------- NETLOGON Directory Logon Scripts Directory HANKP Printer Hank's print share PLOUGH Printer Scarecrow's print share PWLIC Directory PATHWORKS Client License Software PWLICENSE Directory PATHWORKS Client License Software PWUTIL Directory PATHWORKS Client-based Utilities USERS Directory Users Directory Total of 7 shares |
Once you have invoked the command-line interface, you can enter any number of commands. This way of using the command-line interface provides for better system response than entering commands from the OpenVMS prompt.
You can enter commands with parameters and qualifiers on a single line as shown in this example:
$ ADMINISTER ADD COMPUTER DOROTHY/DOMAIN=LANDOFOZ/ROLE=BACKUP |
In some cases, you will be prompted for parameters that you did not enter. For example, if you did not enter the user name with the LOGON command, you will be prompted for it:
LANDOFOZ\\TINMAN> LOGON Username: |
Although the software may prompt for required parameters, do not rely
on the software to prompt you for all required information. Be sure to
enter all required information, except for passwords, on the command
line. For information about entering passwords, see Section 2.1.6, Using Passwords with Commands.
2.1.1 Local and Remote Administration
You can use the ADMINISTER command-line interface to administer the local computer, as well as any other compatible servers on the network to which you have access. By default, you are set up to administer the local server and the domain to which it belongs. You can administer a remote server and domain in one of three ways:
Using ADMINISTER commands on a member server (or directing them to a member server), you can manage the domain-wide security accounts database as you would from any domain controller. Although a member server does not store or maintain the domain-wide database, it still has access to the benefits of the centralized, domain-wide database.
You can also manage a member server's local security accounts database.
You can do so by logging directly into the server's local database, or
setting the default to that database, as explained in Section 2.1.2.1, Administering the Member Server's Local Database.
However, certain ADMINISTER commands will be restricted. Certain
objects, such as global groups and trusts, are manageable only when
logged into a domain controller's domain. Section 2.1.2.2, ADMINISTER Command Variances on Member Servers, lists the
ADMINISTER commands that are not allowed, or that provide restricted
capabilities. The information in both of these sections applies to
workstations as well as member servers.
2.1.2.1 Administering the Member Server's Local Database
Unless you have changed the default to the member server's local database, ADMINISTER commands normally operate domain-wide --- that is, on the domain to which the member server belongs. For example, if you enter the ADMINISTER command on member server WIZARD in domain LANDOFOZ, the ADMINISTER prompt displays domain LANDOFOZ and server WIZARD, as shown:
$ ADMINISTER LANDOFOZ\\WIZARD> |
To manage a member server's local database, you must log in, or change the default domain to the local database. To do so, specify for the domain name the member server's name preceded by two backslashes (\\). The following example shows how to specify the SET ADMINISTRATION command to administer member server WIZARD's local domain database:
LANDOFOZ\\TINMAN> SET ADMINISTRATION/DOMAIN=\\WIZARD %PWRK-S-ADMSET, now administering domain "\\WIZARD", server "WIZARD" \\WIZARD\\WIZARD> |
As shown, when you administer the member server's local domain database, the ADMINISTER prompt displays the domain name preceded by two backslashes, and the domain name is the same as the name of the member server.
In an OpenVMS Cluster in which the Advanced Servers are member servers,
you can optionally specify for the domain name the Advanced Server cluster
alias name, preceded by two backslashes. When administering a clustered
member server's local database, the ADMINISTER prompt displays the
cluster alias name as the domain (preceded by two backslashes). For the
server name, unless you specified a specific server name, the prompt
displays the name of the cluster member that responded first to the
ADMINISTER interface.
2.1.2.2 ADMINISTER Command Variances on Member Servers
As mentioned previously, member servers do not maintain or manage the domain-wide security accounts database and cannot manage or display certain objects, such as global groups, primary groups, and trusts. Table 2-1, Disallowed or Restricted Commands When Administering a Member Server's Local Database, lists the commands that are not allowed, or are restricted when, administering the member server's local domain database. If you attempt to use these commands in such circumstances, the following error message will be displayed:
%PWRK-E-DCONLY, operation is only valid to a Domain Controller |
The affected commands are categorized by each of the following management objects: COMPUTER, GROUP, TRUST, and USER.
| Object | Command | Restriction |
|---|---|---|
| COMPUTER | ADD | Not allowed |
| REMOVE | Not allowed | |
| SET | Not allowed with the /ACCOUNT_SYNCHRONIZE or /ROLE= qualifiers | |
| SHOW | When you do not specify a computer name with the command, it displays information about the member server only (the computer you are managing) rather than about all the computers in the domain; note that the display symbol for a member server is [SV] | |
| GROUP | ADD, COPY, MODIFY, REMOVE, SHOW | Do not use for global groups, or with the /GLOBAL or /PRIMARY_GROUP qualifiers; GROUP commands manage local groups only |
| TRUST | ADD, REMOVE, SHOW | Not allowed |
| USER | ADD, COPY, MODIFY | Do not use with the /PRIMARY_GROUP qualifier; the ADD USER command adds the user to the Users local group; these commands manage memberships in local groups only |
| REMOVE, SHOW | These commands manage memberships in local groups only; the SHOW USERS command does not display the primary group or memberships in global groups |
Some of your network users may be designated as Account Operators, Print Operators, or Server Operators. These users have limited administrative or operator privileges that enable them to perform specific tasks. If you have different operators responsible for parts of your network and you do not want to assign them full administrative privileges, then make them members of groups only at the server being administered.
Required privileges are included in the command descriptions in this
manual.
2.1.4 Understanding Command Syntax
In this manual, command syntax for ADMINISTER commands is denoted as follows:
In general, the ADMINISTER command syntax conforms to the OpenVMS DCL
command conventions. Refer to the OpenVMS DCL Dictionary for more information.
2.1.5 Case Sensitivity
Due to the behavior of OpenVMS, all parameters and qualifier values entered on the command line are converted to uppercase characters when they are processed by the user interface. If you wish to preserve case, or you wish to enter any value that contains blanks (spaces) or any nonalphanumeric characters, you must enclose the value in quotation marks. This is not necessary, however, if you are prompted for additional information after entering a command.
For further information, refer to your Server Administrator's Guide.
2.1.6 Using Passwords with Commands
Some commands require you to enter a password. You can provide a
password with a command by typing the password on the same line as the
command. For example, to log on as the user named JIM using the
password KAHUNA, you type:
$ ADMINISTER LANDOFOZ\\TINMAN> LOGON JIM KAHUNA The server \\TINMAN successfully logged you on as JIM. Your privilege level on domain LANDOFOZ is ADMIN. The last time you logged on was 10/08/00 07:48 PM LANDOFOZ\\TINMAN> |
Because passwords are case sensitive in most cases, pay careful attention when entering them on a command line. If they are to contain any lowercase letters, blanks (spaces), or nonalphanumeric characters, be sure to enclose them in quotation marks.
You can also have the user interface prompt you for the password. For example, to log on to the network, type:
$ ADMINISTER LANDOFOZ\\TINMAN> LOGON JIM Password: The server \\TINMAN successfully logged you on as JIM. Your privilege level on domain LANDOFOZ is ADMIN. The last time you logged on was 10/08/00 07:48 PM LANDOFOZ\\TINMAN> |
When you enter a password when prompted, as in the second example, the password does not appear on the screen as you type. This helps you keep your password confidential, providing added security. In addition, you need not use quotation marks if the password contains lowercase letters, blanks (spaces), or nonalphanumeric characters (as you do when entering the password on the command line).
If you forget to enter a password for a command that requires one, the software prompts you for it. Depending on the command that you type, the software may also prompt you for other required information, such as your user name.
Although the software may prompt for required parameters, do not rely on the software to prompt you for all required information. Be sure to enter all required information, except for passwords, on the command line.
| Next | Contents | Index |
|
|||||||||||||||