This guide provides reference information for DIGITAL Distributed Computing Environment (DCE) for OpenVMS VAX and OpenVMS Alpha.
Revision/Update Information: This guide supersedes the Digital DCE for OpenVMS VAX and OpenVMS Alpha Reference Guide Version 1.3.
Software Version: Digital DCE for OpenVMS Version 1.5
Compaq Computer Corporation
Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor.
Compaq conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community.
© Compaq Computer Corporation 1999. All rights reserved.
The following are trademarks of Compaq Computer Corporation: Alpha, Compaq, DECnet, DECthreads, DIGITAL, OpenVMS, VAX, VMS, and the Compaq logo.
The following are third-party trademarks:
Kerberos is a trademark of the Massachusetts Institute of Technology.
Microsoft, MS, and MS--DOS are registered trademarks of Microsoft Corporation.
MultiNet is a registered trademark of the Open Software Foundation, Inc.
NetView is a registered trademark of International Business Machines Corporation.
All other trademarks and registered trademarks are the property of their respective holders.
The OpenVMS documentation set is available on CD-ROM.
The Digital DCE for OpenVMS VAX and OpenVMS Alpha Reference Guide provides users of the DIGITAL Distributed Computing Environment (DCE) Kit with reference information necessary to use DIGITAL DCE Version 1.5 on OpenVMS VAX and OpenVMS Alpha systems. This guide should be used with the documents listed under Associated Documents.
Information on Microsoft's NT LAN Manager is provided as a preview of functionality that will be available in a future version of Digital DCE for OpenVMS (Alpha only). This advanced documentation will help you in future planning.
This guide contains the following parts and chapters:
For additional information on the Open Systems Software Group (OSSG) products and services, access the following OpenVMS World Wide Web address:
Compaq welcomes your comments on this manual.
Print or edit the online form SYS$HELP:OPENVMSDOC_COMMENTS.TXT and send us your comments by:
|Fax||603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08|
Compaq Computer Corporation
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698
Use the following World Wide Web address to order additional documentation:
If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825).
VMScluster systems are now referred to as OpenVMS Cluster systems. Unless otherwise specified, references in this document to OpenVMS Clusters or clusters are synonymous with VMSclusters.
The following conventions are also used in this guide:
|Ctrl/ x||A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.|
|italic text||Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where device-name contains up to five alphanumeric characters).|
|UPPERCASE TEXT||Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.|
Monospace type indicates code examples and interactive screen displays.
In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.
|Case-sensitivity||OpenVMS operating system commands do not differentiate between uppercase and lowercase. However, many DCE commands do make this distinction. In particular, the system configuration utility interprets names in a case-sensitive manner.|
This chapter contains reference information on the Integrated Login UAF
commands discussed in the Digital DCE for OpenVMS VAX and OpenVMS
Alpha Product Guide.
1.1 Running the DCE$UAF Utility
Integrated Login provides two methods of running the DCE$UAF utility:
$ DCE$UAF DCEUAF>
$ DCE$UAF command $
$ DCE$UAF :== $SYS$SYSTEM:DCE$UAF
$ RUN SYS$SYSTEM:DCE$UAF DCEUAF>
The Integrated Login DCE$UAF utility has the capability to execute an initialization file. By default, the file is called DCE$UAF_INIT.COM.
The DCE$UAF initialization file is a command procedure that the DCE$UAF utility automatically executes at startup. Every time you start the DCE$UAF utility, the commands contained in the file are automatically executed.
An initialization file contains any command lines you might always enter when you start the DCE$UAF utility. For example, you might include DEFINE/KEY commands in the initialization file.
If you use a file other than DCE$UAF_INIT.COM as your DCE$UAF utility initialization file (for example, START.COM), define it with the following command:
$ DEFINE DCE$UAF_INIT WORK:[SMITH]START.COM
If you include your startup commands in DCE$UAF_INIT.COM, there is no need to separately define it.
Executes a DCE$UAF utility command procedure.
@ FILE-SPEC /OUTPUT=file-spec
FILE-SPECSpecifies the command procedure to be executed. A command procedure is a file containing a sequence of DCE$UAF commands. When the command procedure is executed, the commands in the file are processed in order as if each command had been entered individually from the terminal or workstation.
If you do not specify a file type, the system uses the default file type of .COM.
No wildcard characters are allowed in the file specification.
/OUTPUT=file-specRequests that all output directed to the logical device SYS$OUTPUT be written to the file or device specified. System responses and error messages are written to SYS$COMMAND as well as to the specified file.
The default output file type is .LIS.
No wildcard characters are allowed in the output file specification.
The @ command directs the DCE$UAF utility to read commands from the specified command file.
Adds new records to the DCE authorization file (DCE$UAF).
ADD [USERNAME] [DCE-NAME] / [NO]ALL /FLAGS=flags /[NO]LOG
USERNAMEOpenVMS username for the DCE authorization record to be added. This argument is not required if /ALL is specified. In all other cases it is required.
DCE-NAMEDCE principal name to be associated with the OpenVMS account USERNAME. If the principal exists in a different DCE cell from the current DCE cell, specify the DCE name in the format principal@cell. If the DCE name contains lowercase characters, spaces, or other special characters, enclose the entire string in quotes.
This argument is not required if /ALL is specified. This argument is optional if /ALL is not specified. If it is not specified, then USERNAME, converted to lowercase, is the default.
/NOALL (default)If present, specifies that a DCE authorization record be created for all accounts in the system authorization file (SYSUAF) that do not currently have an authorization record. In this case the USERNAME and DCE-NAME arguments should not be specified as the DCE name is derived from the OpenVMS username. (Refer to the description of DCE-NAME for more information.) If not present, the record to be added is specified by the USERNAME argument.
/FLAGS=([NO]keyword[,...])Specifies special attributes that are to be stored with the DCE$UAF record. The keyword you can specify is as follows:
The OpenVMS account defined has a corresponding DCE account. The default is /FLAGS=DCE.
The OpenVMS account defined does not have a corresponding DCE account. In this case DCE-NAME is ignored.
/NOLOGControls whether or not a message is displayed after a record has been added.
The ADD command adds new records to the DCE authorization file (DCE$UAF).
DCE$UAF> ADD SMITH %DCE-S-UAF_ADDED, created entry SMITH, principal is "smith" DCE$UAF> ADD SMITH "John Smith" %DCE-S-UAF_ADDED, created entry SMITH, principal is "John Smith" DCE$UAF> ADD SMITH "smith@othercell" %DCE-S-UAF_ADDED, created entry SMITH, principal is "smith@othercell"
Checks the continuity between the OpenVMS system authorization file (SYSUAF) and the DCE Authorization file (DCE$UAF).
ANALYZE /[NO]DCE$UAF /OUTPUT=output /[NO]SYSUAF /[NO]VERBOSE
/NODCE$UAFSpecifies that the DCE authorization file (DCE$UAF) be read record by record and any record found that does not have a matching account in the OpenVMS authorization file (SYSUAF) be reported.
Any discrepancies found can be corrected using the /PURGE command.
/OUTPUT=(output)Determines where the output is written. The default is SYS$OUTPUT:.
/NOSYSUAFSpecifies that the OpenVMS system authorization file (SYSUAF) be read account by account and any account found that does not have a matching record in the DCE Authorization file (DCE$UAF) be reported.
Any discrepancies found can be corrected using the ADD command.
/NOVERBOSE (default)Specifies that all accounts/records be displayed. By default only those without matching records/accounts are displayed.
The ANALYZE command checks the continuity between the OpenVMS authorization file (SYSUAF) and the DCE Authorization file (DCE$UAF).
DCEUAF> ANALYZE %DCE-I-UAF_SYSCHKBEG, starting scan of SYSUAF file SYSUAF entry ALAN does not exist in DCE$UAF SYSUAF entry BILL does not exist in DCE$UAF SYSUAF entry DCE$SERVER does not exist in DCE$UAF SYSUAF entry DEFAULT does not exist in DCE$UAF SYSUAF entry FAL$SERVER does not exist in DCE$UAF SYSUAF entry JAMES does not exist in DCE$UAF SYSUAF entry MAIL$SERVER does not exist in DCE$UAF SYSUAF entry NML$SERVER does not exist in DCE$UAF SYSUAF entry OPERATOR does not exist in DCE$UAF SYSUAF entry PHONE$SERVER does not exist in DCE$UAF SYSUAF entry SYSTEM does not exist in DCE$UAF SYSUAF entry WALLY does not exist in DCE$UAF 12 out of 97 records do not have a DCE$UAF entry %DCE-I-UAF_SYSCHKEND, completed scan of SYSUAF file %DCE-I-UAF_DCECHKBEG, starting scan of DCE$UAF file 0 out of 24 records do not have a SYSUAF entry %DCE-I-UAF_DCECHKEND, completed scan of DCE$UAF file DCEUAF>
Switches control of your terminal from your current process to another process.
ATTACH [PROCESS-NAME] /IDENTIFICATION=pid
PROCESS-NAMESpecifies the name of a parent process or spawned subprocess to which control passes. The process must already exist, be part of your current job, and share the same input stream as your current process. However, the process cannot be your current process or a subprocess created with the /NOWAIT qualifier.
Process names can contain from 1 to 15 alphanumeric characters. If a connection to the specified process cannot be made, an error message is displayed.
The PROCESS-NAME argument is incompatible with the /IDENTIFICATION qualifier.
Specifies the process identification (PID) of the process to which terminal control will be transferred. Leading zeros can be omitted. The /IDENTIFICATION qualifier is incompatible with the PROCESS-NAME argument.
If you omit the /IDENTIFICATION qualifier, you must specify a process name.
The ATTACH command switches control of your terminal from your current process to another process. This command allows you to move between processes that you create with the SPAWN command. For example, while you are editing a file, use the SPAWN command to move to a subprocess such as the DCE$UAF utility. Then enter ATTACH to move back to the editing session. If you want to return to the DCE$UAF utility, enter the ATTACH command to move back to the DCE$UAF subprocess you already created.
DCE$UAF> ATTACH JONES_2
Transfers the terminal's control to the subprocess JONES_2.
The ATTACH command switches control from the current process to a process having the PID 30019. Notice that because the /IDENTIFICATION qualifier is specified, the PROCESS-NAME argument is omitted.
Associates an equivalence string and a set of attributes with a key on the terminal keyboard.
DEFINE/KEY KEY-NAME EQUIVALENCE-STRING /[NO]ECHO /[NO]ERASE /[NO]IF-STATE /[NO]LOCK-STATE /[NO]LOG /[NO]SET-STATE /[NO]TERMINATE
KEY-NAMESpecifies the name of the key that you are defining. All definable keys on VT52 terminals are located on the numeric keypad. On VT100-series terminals, you can define the left and right arrow keys as well as all the keys on the numeric keypad. On terminals with LK201 keyboards, the following types of keys can be defined:
- Keys on the numeric keypad
- Keys on the editing keypad (except the up and down arrow keys)
- Keys on the function key row across the top of the keyboard. (Note that you cannot define function keys F1 to F5.)
Some definable keys are enabled for definition all the time. Others, including KP0 to KP9, Period, Comma, and Minus, must be enabled for definition purposes. Before using these keys, enter either the SET TERMINAL/APPLICATION command or the SET TERMINAL/NONUMERIC command.
On LK201 keyboards, you cannot define the up and down arrow keys or function keys F1 to F5. The left and right arrow keys and the F6 to F14 keys are reserved for command line editing. You must enter the SET TERMINAL/NOLINE_EDITING command before defining these keys. You can also press Ctrl/V to enable keys F7 to F14. Note that Ctrl/V will not enable the F6 key.
EQUIVALENCE-STRINGSpecifies the character string to be processed when you press the key. Enclose the string in quotation marks (" ") to preserve spaces and lowercase characters.
/NOECHODisplays the equivalence string on your screen after the key has been pressed. You cannot use the /NOECHO qualifier with the /NOTERMINATE qualifier.
/NOERASE (default)Determines whether the current line is erased before the key translation is inserted.
/NOIF_STATESpecifies a list of one or more states, one of which must be in effect for the key definition to work. The /NOIF_STATE qualifier has the same meaning as /IF_STATE=current_state. The state name is an alphanumeric string. States are established with the /SET_STATE qualifier or the SET KEY command. If you specify only one state name, you can omit the parentheses. By including several state names, you can define a key to have the same function in all the specified states.
/NOLOCK_STATE (default)Specifies that the state set by the /SET_STATE qualifier remain in effect until explicitly changed. (By default, the /SET_STATE qualifier is in effect only for the next definable key you press or the next read-terminating character that you type.) Can only be specified with the /SET_STATE qualifier.
/NOLOGDisplays a message indicating that the key definition has been successfully created.
/NOSET_STATE (default)Causes the specified state name to be set when the key is pressed. (By default, the current locked state is reset when the key is pressed.) If you have not included this qualifier with a key definition, you can use the SET KEY command to change the current state. The state name can be any alphanumeric string; specify the state as a character string enclosed in quotation marks.
/NOTERMINATE (default)Specifies whether the current equivalence string is to be processed immediately when the key is pressed (equivalent to entering the string and pressing the Return key). By default, you can press other keys before the definition is processed. This allows you to create key definitions that insert text into command lines, after prompts, or into other text that you are entering.
The DEFINE/KEY command associates an equivalence string and a set of attributes with a key on the terminal keyboard. The /KEY qualifier is required.