HP OpenVMS Systems

HP Advanced Server for OpenVMS
Commands Reference Manual

Removes a user account mapping between an Advanced Server user account and an OpenVMS user account.

Format

REMOVE HOSTMAP [domain-name\]user-name [/qualifiers]

restrictions

This command is valid only to HP OpenVMS servers. Use of this command requires membership in the Administrators local group.

Related Commands

ADD HOSTMAP
SHOW HOSTMAP

Parameters

[domain-name\]user-name

Specifies the Advanced Server or OpenVMS user account name whose mapping is to be removed. To remove the mapping of a network user in a trusted domain, specify the domain-qualified user name in the format domain-name\user-name, such as KANSAS\DOLE, where KANSAS is the trusted domain, and DOLE is the user name of the user account defined in the trusted domain. If you omit the domain name, the user account is assumed to be defined in the domain of the server currently being administered.

Qualifiers

/CONFIRM

/NOCONFIRM

Controls whether you are prompted for a confirmation before the operation is performed. The default is /CONFIRM if running in interactive mode. When the prompt is issued, the default response is shown, and you may accept the default by pressing Return or Enter. If you type YES, TRUE, or 1, the operation is performed. If you type NO, FALSE, 0, or enter Ctrl/Z, no action is performed. If you type anything else, the prompt is repeated until you type an acceptable response. No prompt for confirmation is issued if running in batch mode.

/HOSTUSER

Indicates that the specified user name is an OpenVMS user name. All Advanced Server user account mappings to the specified OpenVMS user name will be removed.

Note that more than one Advanced Server user name may be mapped to a single OpenVMS user name. Use the SHOW HOSTMAP command to check. Removing the mappings for an OpenVMS user name may result in the removal of more than one Advanced Server user name mapping.

Do not specify both /HOSTUSER and /NETUSER on the same command line.

/NETUSER

Indicates that the specified user name is an Advanced Server user name. The account mapping for the specified Advanced Server user name will be removed. This is the default if you specify neither /NETUSER nor /HOSTUSER. Do not specify both /HOSTUSER and /NETUSER on the same command line.

/SERVER=server-name

Specifies the name of the server on which to remove the host account mapping. The default is the server currently being administered.

Examples

 LANDOFOZ\\TINMAN> REMOVE HOSTMAP WITCH/NETUSER
 Do you really want to remove host mapping for "WITCH" [YES or NO]
 (YES) :
 %PWRK-S-HOSTMAPREM, mapping for user "WITCH" removed
      

This example removes the user account mapping for the Advanced Server user name WITCH on the server currently being administered (TINMAN). A confirmation is required.

 LANDOFOZ\\TINMAN> REMOVE HOSTMAP STRAWMAN/HOSTUSER/NOCONFIRM
%PWRK-S-HOSTMAPSREM, mappings to user "STRAWMAN" removed
      

This example removes all Advanced Server user account mappings to the OpenVMS user name STRAWMAN on the server currently being administered (TINMAN). A confirmation is not required.

Removes an existing OpenVMS Advanced Server print queue.

Before deleting a printer queue (one that points directly to an OpenVMS execution queue), execute the following commands, in the order shown:

1. PAUSE PRINT QUEUE --- to pause the print queue. You do not have to pause a routing queue before deleting it. (When you use the REMOVE PRINT QUEUE command to delete a print queue, the queue is not deleted until all jobs in that queue complete.)
2. REMOVE PRINT QUEUE --- to delete any routing queues that point to the printer queue.

Then, use the REMOVE PRINT QUEUE command to delete the printer queue.

To delete a print queue and all pending jobs in that queue except the job currently printing, first use the SET PRINT QUEUE/PURGE command to delete the pending print jobs, then use the REMOVE PRINT QUEUE command.

To remove a print queue and all jobs in its queue, including the one currently printing, use the following commands, in the order shown:

1. SET PRINT QUEUE/PURGE --- to delete all pending print jobs.
2. SET PRINT JOB/DELETE --- to delete the currently printing job.
3. REMOVE PRINT QUEUE --- to delete the queue.

Format

REMOVE PRINT QUEUE queue-name [/qualifiers]

restrictions

This command is valid only to HP OpenVMS servers. Use of this command requires membership in the Administrators, Server Operators, or Print Operators local group.

You can delete only those queues created by the Advanced Server. You cannot use ADMINISTER commands to delete a queue created by DECprint Supervisor for OpenVMS or OpenVMS software.

Related Commands

ADD PRINT QUEUE
CONTINUE PRINT QUEUE
PAUSE PRINT QUEUE
SET PRINT QUEUE
SHOW PRINT QUEUES

Parameters

queue-name

Specifies the name of the print queue to remove.

Qualifiers

/CONFIRM

/NOCONFIRM

Controls whether you are prompted for a confirmation before the operation is performed. The default is /CONFIRM if running in interactive mode. When the prompt is issued, the default response is shown, and you may accept the default by pressing Return or Enter. If you type YES, TRUE, or 1, the operation is performed. If you type NO, FALSE, 0, or enter Ctrl/Z, no action is performed. If you type anything else, the prompt is repeated until you type an acceptable response. No prompt for confirmation is issued if running in batch mode.

/SERVER=server-name

Specifies the name of the server from which to remove the print queue. The default is the server currently being administered.

Example

LANDOFOZ\\TINMAN> REMOVE PRINT QUEUE TOTO
Do you really want to remove print queue "TOTO" [YES or NO] (YES) : YES
%PWRK-S-QUEREM, queue "TOTO" removed from server "TINMAN"
      

This example removes the print queue TOTO from the server currently being administered (TINMAN). A confirmation is required.

Removes an existing directory or print share from a server's share database. The resource will no longer be available to the network.

Format

REMOVE SHARE share-name [/qualifiers]

restrictions

Membership in the Administrators, Account Operators, or Server Operators local group is required to administer directory shares. Members of the Print Operators local group may administer print shares.

Related Commands

ADD SHARE/DIRECTORY
ADD SHARE/PRINT
MODIFY SHARE
SHOW SHARES

Parameters

share-name

Specifies the name of the share to remove.

Qualifiers

/CONFIRM

/NOCONFIRM

Controls whether you are prompted for a confirmation before the operation is performed. The default is /CONFIRM if running in interactive mode. When the prompt is issued, the default response is shown, and you may accept the default by pressing Return or Enter. If you type YES, TRUE, or 1, the operation is performed. If you type NO, FALSE, 0, or enter Ctrl/Z, no action is performed. If you type anything else, the prompt is repeated until you type an acceptable response. No prompt for confirmation is issued if running in batch mode.

/SERVER=server-name

Specifies the name of the server from which to remove the share. The default is the server currently being administered.

Example

LANDOFOZ\\TINMAN> REMOVE SHARE RAINBOW
Do you really want to remove share "RAINBOW" [YES or NO] (YES) : YES
%PWRK-S-SHAREREM, share "RAINBOW" removed from server "TINMAN"
      

This example removes the share named RAINBOW from the server currently being administered (TINMAN). A confirmation is required.

Removes the specified domain from the list of domains this domain trusts, or the list of domains that are allowed to trust this domain.

Removing a trust relationship requires two steps on each of the two domains: one domain must stop trusting a second domain, and the second domain must stop permitting the first domain to trust it. Never remove a trust relationship by performing just one of the steps.

When removing a trust relationship, always administer both domains. Once a trust relationship is established, the password used to establish the trust is changed by the system. Because of this, you cannot remove one side of an established trust relationship, and then later reestablish that trust using the original password. You must always remove both sides of a trust relationship, and then completely reestablish it.

Format

REMOVE TRUST trust-domain [/qualifiers]

restrictions

Use of this command requires membership in the Administrators local group.

Related Commands

ADD TRUST
SHOW TRUSTS

Parameters

trust-domain

Specifies the name of the domain for which to remove a trust relationship.

Qualifiers

/CONFIRM

/NOCONFIRM

Controls whether you are prompted for a confirmation before the operation is performed. The default is /CONFIRM if running in interactive mode. When the prompt is issued, the default response is shown, and you may accept the default by pressing Return or Enter. If you type YES, TRUE, or 1, the operation is performed. If you type NO, FALSE, 0, or enter Ctrl/Z, no action is performed. If you type anything else, the prompt is repeated until you type an acceptable response. No prompt for confirmation is issued if running in batch mode.

/DOMAIN=domain-name

Specifies the name of the domain from which to remove the trust relationship. The default is the domain currently being administered. Do not specify both /DOMAIN and /SERVER on the same command line.

/PERMITTED

Specifies that the domain should be removed from the list of domains that are permitted to trust this domain. Be sure to administer the specified domain and remove this domain from its list of trusted domains. You must specify either the /PERMITTED or /TRUSTED qualifier, but not both.

/SERVER=server-name

Specifies the name of a server that is a member of the domain from which to remove the trust relationship. Do not specify the /SERVER qualifier with the /DOMAIN qualifier.

/TRUSTED

Specifies that the domain should be removed from the list of domains that this domain trusts. Be sure to administer the specified domain and remove this domain from its list of permitted-to-trust domains. You must specify either the /PERMITTED or /TRUSTED qualifier, but not both.

Examples

The following two examples together show how to remove a one-way trust relationship between the domain currently being administered (LANDOFOZ) and the domain called KANSAS. After this trust relationship has been removed, users in the KANSAS domain will no longer have access to resources in the LANDOFOZ domain.

 LANDOFOZ\\TINMAN> REMOVE TRUST KANSAS/TRUSTED
 Removing domain "KANSAS" from the Trusted Domains List will prevent
 users in domain "KANSAS" from accessing resources in domain
 "LANDOFOZ". If you choose to continue, you must also administer
 domain "KANSAS" and remove "LANDOFOZ" from its list of Permitted
 Domains.

 Do you want to continue with the removal [YES or NO] (YES) : YES
 %PWRK-S-TRUSTREM, trust between domains "LANDOFOZ" and "KANSAS"
 removed
      

This example removes the domain KANSAS from the list of trusted domains on the domain currently being administered (LANDOFOZ). A confirmation is required.

 LANDOFOZ\\TINMAN> REMOVE TRUST LANDOFOZ/DOMAIN=KANSAS/PERMITTED

 Removing domain "LANDOFOZ" from the Permitted Domains List will
 prevent users in domain "KANSAS" from accessing resources in domain
 "LANDOFOZ". If you choose to continue, you must also administer
 domain "LANDOFOZ" and remove "KANSAS" from its list of Trusted
 Domains.

 Do you want to continue with the removal [YES or NO] (YES) : YES
 %PWRK-S-TRUSTREM, trust between domains "KANSAS" and "LANDOFOZ"
 removed
      

This example removes the domain LANDOFOZ from the list of permitted-to-trust domains on the domain called KANSAS. This completes the removal of the trust relationship between domains LANDOFOZ and KANSAS initiated in the first example. A confirmation is required.

Permanently removes a user from a domain's security database.

Be sure you want to remove a user before you do so, because you cannot recover a deleted user account. The server knows every user account by its security identifier (SID), a unique number that identifies it. If you delete a user account and then create another user account with the same name, the new user account will not have any of the permissions that were previously granted to the old user account, because the user accounts have different SID numbers.

Format

REMOVE USER user-name [/qualifiers]

restrictions

Use of this command requires membership in the Administrators or Account Operators local group. Only members of the Administrators local group can remove an Administrators privilege account.

Related Commands

ADD USER
COPY USER
MODIFY USER
SHOW USERS

Parameters

user-name

Specifies the name of the user account that you wish to remove.

Qualifiers

/CONFIRM

/NOCONFIRM

Controls whether you are prompted for a confirmation before the operation is performed. The default is /CONFIRM if running in interactive mode. When the prompt is issued, the default response is shown, and you may accept the default by pressing Return or Enter. If you type YES, TRUE, or 1, the operation is performed. If you type NO, FALSE, 0, or enter Ctrl/Z, no action is performed. If you type anything else, the prompt is repeated until you type an acceptable response. No prompt for confirmation is issued if running in batch mode.

/DOMAIN=domain-name

Specifies the name of the domain from which to remove the user account. The default is the domain currently being administered. Do not specify both /DOMAIN and /SERVER on the same command line.

/SERVER=server-name

Specifies the name of a server that is a member of the domain from which to remove the user. Do not specify both /DOMAIN and /SERVER on the same command line.

Example

LANDOFOZ\\TINMAN> REMOVE USER SCARECROW

Each user account is represented by a unique identifier that is
independent of the user name. Once this user account is deleted,
even creating an identically named user account in the future will
not restore access to resources that currently name this user
account in the access control list.

Remove user "SCARECROW" [YES or NO] (YES) : YES
%PWRK-S-USERREM, user "SCARECROW" removed from domain "LANDOFOZ"
      

This example removes the user named SCARECROW from the domain currently being administered (LANDOFOZ). A confirmation is required.

Saves an event log file to a specified archive file on the server being administered. A saved event log file can later be reopened for display by the SHOW EVENTS command.

Format

SAVE EVENTS log-file-spec [/qualifiers]

restrictions

Use of this command requires membership in the Administrators local group. The server to be administered must be a HP OpenVMS server.

Related Commands

CLEAR EVENTS
SHOW EVENTS

Parameters

log-file-spec

A file specification for the archived event log file of the server being administered (which, if the /SERVER qualifier is used, is the server specified with that qualifier). The file specification is local to the server being administered. On a PATHWORKS or Advanced Server for OpenVMS server, if no device or directory is specified, the archived event log is saved to the path pointed to by the logical name PWRK$LMLOGS:.

Qualifiers

/SERVER=server-name

Specifies the name of the server to be administered. For saving event log files, the specified server must be a HP OpenVMS server. The event log file of the specified server is saved on that server. The default is the server currently being administered.

/TYPE=log-type

Specifies the log file to be saved. The log-type keyword can be one of the following:

Log-type	Log File
APPLICATION	The application log file
SECURITY	The security log file
SYSTEM	The system log file (the default)

Example

LANDOFOZ\\TINMAN> SAVE EVENTS SYSTEM.BKP/TYPE=SYSTEM/SERVER=DOROTHY
%PWRK-S-ELFSAVE, System Event Log from server "DOROTHY" saved
      

This example saves the system event log file of server DOROTHY to the file PWRK$LMLOGS:SYSTEM.BKP on server DOROTHY.

Sends a message to one or more computers on the network, or to all or specific users connected to a server. The message appears in a pop-up window on the workstation.

Format

SEND computer-name[,...] [/qualifiers] [message]

SEND/USERS [/qualifiers] [message]

restrictions

The Alerter service must be running on the computer sending the message. Messages can only be received by client computers running the Messenger service. The Messenger service is not supported on the Advanced Server: OpenVMS users on the Advanced Server will not receive messages sent with the SEND command.

Parameters

computer-name

Specifies the computers that are to receive the message --- either a single computer name or a comma-separated list of computer names.

message

Specifies the text of the message to send. The message text must follow all other parameters and qualifiers. To preserve the case of a message, enclose the message in quotation marks. If message is not specified, you are prompted for a multi-line message. When you have finished entering the message, enter Ctrl/Z to terminate the message text.

Qualifiers

/NAME=user-name

Use with the /USERS qualifier to send the message to a specific user. user-name is the name of the user to whom to send the message.

/SERVER=server-name

Specifies the name of the server from which to send the message. If you use the /USERS qualifier, the value of server-name is also used to select the users to which the message is sent. The default is the server currently being administered.

/SHARENAME=share-name

Use with the /USERS qualifier to restrict sending the message to only users connected to the specified share name.

/USERS

If included, the /USERS qualifier must immediately follow the SEND verb and is used to send the message to users connected to a server rather than to specific computers. The default is to send the message to all users connected to the server. However, you can use the /NAME and /SHARENAME qualifiers with the /USERS qualifier to send a message to specific users.

Examples

 LANDOFOZ\\TINMAN> SEND OZ1,OZ2 "Meeting changed to 3 pm."
      

This example sends the message "Meeting changed to 3 pm." to computers OZ1 and OZ2.

 LANDOFOZ\\TINMAN> SEND/USERS/SERVER=DOROTHY -
 _LANDOFOZ\\TINMAN> "Server DOROTHY will be going down at 21:00 hours"
      

This example sends the message "Server DOROTHY will be going down at 21:00 hours" to all users connected to the server DOROTHY.

 LANDOFOZ\\TINMAN> SEND/USERS/SERVER=DOROTHY/SHARENAME=WIZARD -
 _LANDOFOZ\\TINMAN> "The WIZARD share will be deleted at 6 pm."
      

This example sends the message "The WIZARD share will be deleted at 6 pm." to all users connected to the share named WIZARD on server DOROTHY.

 LANDOFOZ\\TINMAN> SEND/USERS/NAME=TOTO "Follow the yellow brick road"
      

This example sends the message "Follow the yellow brick road" to user TOTO connected to the server currently being administered (TINMAN).