Technical data

Using TCP/IP Services Management Commands
1.1 Entering Commands
Table 1–1 (Cont.) Management Command Guidelines
Element Guideline
UNIX commands Follow UNIX syntax and case rules when entering UNIX
commands at the DCL and TCPIP> prompts. For example,
enter the
ifconfig command in lowercase letters:
TCPIP> ifconfig options
When entering UNIX commands at the DCL or TCPIP>
prompt, enclose uppercase options in quotation marks. For
example:
$ TCPIP> sysconfig "-Q" inet
You can abbreviate commands, as shown in the following
example. The abbreviation must be unique through the first
four characters.
TCPIP> ifco options
If the abbreviation entered is not unique, an error message will
advise you to supply more characters. In the following example,
the SYSCONFIG command cannot be abbreviated because of
the SYSCONFIGDB command.
TCPIP> sysc -q
%CLI-W-ABVERB, ambiguous command verb -
supply more characters
Wildcards If you specify a wildcard (an asterisk [*]) on a command line,
you are asked for confirmation before the command executes.
For example:
TCPIP> REMOVE PROXY *
VMS User_name Type User_ID Group_ID Host_name
GRACKLE N 269 48 MAPLE
Remove? [N]:
To change this default behavior (so that you are not asked to
confirm), use the /NOCONFIRM qualifier with the command.
1.1.1 Setting Configuration Parameters
Some commands allow you to enter information in the database; others modify
only the run-time parameters. Table 1–2 shows the SET commands that affect
one or the other.
Using TCP/IP Services Management Commands 1–5