HP 3PAR InForm OS 3.1.1 CLI Administrator's Manual

Setting the TPDSYSNAME Environment Variable on Solaris and Linux
• To set the environment variable on Solaris or Linux, see the following system output example.
Substitute your system name for <sysname> and use the correct syntax for your shell.
$ TPDSYSNAME=<sysname>
$ export TPDSYSNAME
$ cli
Setting the TPDSYSNAME Environment Variable on Windows
• To set the environment variable in Microsoft Windows for one instance of a Command Prompt
window, run set TPDSYSNAME=<sysname>. Substitute <sysname> with the name of your
system. The environment variable remains in effect for that window until you exit that window.
• To set the environment variable in Windows indefinitely and for all newly created Command
Prompt windows:
1. Perform Step 1 through Step 4 of the procedure for setting the TPDSOCKSSL environment
variable in Windows as described in “Using SSL” (page 49).
2. In the Environment Variable dialog box, enter TPDSYSNAME in the Variable box.
3. Enter your system name in the Value box.
4. Click OK.
Using the -sys Option
The global option –sys (system) overrides any setting of the environment variable TPDSYSNAME.
On the command line, enter –sys after the command name, followed by your system name. See
the following output example. Substitute your system name for <system1>.
$ showhost –sys <system1>
Using the System Name
The system prompts for the system name if the environment variable TPDSYSNAME is not set and
the –sys option is not used. To use the system name, see the following output example. Substitute
your system name for <system1>.
$ cli
system: <system1>
Setting Your Name and Password
Your name and password can be provided when prompted, or read from a file that is specified
with the environment variable TPDPWFILE or the global option –pwf (password file).
CAUTION: By setting the system name, user name, and password using environment variables,
you are not prompted for this information when running the CLI, which can be useful for scripting.
However, passwords must be kept secure. Using encrypted passwords in scripts, using an encrypted
pwfile, or the encrypted password on the command line raises the risk of password exposure. It
is imperative that the script, pwfile, or command line history file be strictly maintained to avoid
compromise of the encrypted password. Failure to do so can leave the user open to impersonation
by anyone with access to the encrypted string.
NOTE: LDAP users can save password files using the setpassword command. However, LDAP
users are limited access to only the system they were logged into when they saved their password.
50 Running the InForm OS Command Line Interface