The Finger listing may include such information as:
What You Can Do
The following table lists the capabilities provided by Finger and the sections that explain how to use them.
Capability | Section |
---|---|
Display brief information about all users on a host | 2.3.1 |
Display detailed information about one or more specific users on a host | 2.3.2 |
Display information about all users logged into the local OpenVMS Cluster system | 2.3.3 |
Get information from a host that is not directly accessible to your local host | 2.4 |
Make planning and project information about yourself available to other Finger users | 2.5 |
What You Need
The Finger software must be enabled (see your system manager). If the Finger software is not enabled on your local OpenVMS host, when you attempt to display information about users on that host, an error message is returned. For example, the following error message indicates the Finger image was not installed with the privileges required. See your system manager.
%SYSTEM-S-NOTALLPRIV, not all requested privileges authorized
The Finger utility must be enabled on any remote host for which you want information. If the software does not exist or is disabled on the remote host, an error message is returned, such as the following:
FINGER-I-CONNREF, Connection refused
Use the following rules for command syntax, quotation marks, and
wildcards when you type FINGER command lines.
2.1.1 Quotation Marks
By default, the Finger utility translates all user and host name specifications to lowercase. If you specify any letters that must be uppercase, then you must enclose them in quotation marks. In the following example, the UNIX user name includes uppercase letters that need quotation marks around them:
FINGER "B"OB"M"ILLER@BASE1
Wildcards are not accepted for OpenVMS hosts, but may be valid for some
UNIX hosts.
2.1.3 Qualifiers
Qualifiers to the FINGER command must follow immediately after the command, preceding the user and/or host name. If the qualifier follows the user and/or host name, the Finger utility interprets the qualifier as a user name. For example, in the following command the qualifier /FULL incorrectly appears after the user specification. As indicated by the last line in the display, the Finger server interprets "/FULL" as a user login name.
$ FINGER ROLLINS /FULL Username Program Login Term/Location ROLLINS $ Mon 15:02 64626::ROLLINS Login name: ROLLINS In real life: Professor Rollins Account: RES9 Directory: WORK1$:[ROLLINS] Last login: Tue 4-MAR-1997 09:05:29 Unread mail: 25 Project: Homeopathic medicine/Silica No Plan. Login name: /FULL In real life: ???
The following example shows the correct position of the qualifier (the information displayed now includes user ROLLINS' real name and current program).
$ FINGER /FULL ROLLINS [stlab1.bastyr.edu] Username Real Name Program Login Term/Location ROLLINS Ben Rollins $ Mon 15:02 64606::ROLLINS $ Mon 09:42 64606::ROLLINS Login name: ROLLINGS In real life: Professor Rollins Account: RES9 Directory: WORK1$:[ROLLINS] Last login: Tue 4-MAR-1997 09:05:29 Unread mail: 27 Project: Homeopathic medicine/Silica No Plan.
You can obtain online help for the Finger utility and use of the FINGER command by typing either of the following commands:
$ HELP TCP_IP_SERVICES DISPLAYING_USER_INFORMATION $ HELP TCP_IP_SERVICES FINGER_COMMAND
To display information about all users on a remote host, enter the FINGER command followed by the host name (FINGER @hostname). To display more detailed information about a particular user, specify the user name with the host name (format FINGER username@hostname). To display information about all users on your local host, enter the FINGER command without specifying a host name. To display detailed information about a specific user on your local host, enter the FINGER command followed by the user name. Table 2-1 summarizes the different ways to display user information.
If you need ... | Use this command... |
---|---|
Brief information about all users on a remote host | FINGER @ hostname |
Brief information about all users on your local host | FINGER |
Brief information about all users on your cluster | FINGER/CLUSTER |
Detailed information about a specific user on a remote host | FINGER username@ hostname |
Detailed information several users on a remote host | FINGER user1name@ hostname user2name@ hostname |
Detailed information about a specific user on your local host | FINGER username |
Detailed information about several users on your local host | FINGER user1name user2name |
More detailed information about users on the local host, including their real name and all logins | FINGER/FULL |
Detailed information about a specific local user and brief information about all local users | FINGER/ALL username |
2.3.1 Displaying Information About All Users
To display brief information about all users on a host, use the FINGER
command with the host name only, in the format @hostname. If
you use the FINGER command alone (without specifying a host name), you
receive brief information about all users on your local system. The
following example shows how to display brief information about all
users on remote host SCIENCE:
$ FINGER @SCIENCE [science.ucd.edu] Username Program Login Term/Location BRADY $ Thu 07:50 dialin_706_101.ucd.lab.edu CORRIT $ Tue 13:30 64334::CORRIT DAVE MAIL Mon 15:02 64334::DAVE DAWSON $ Thu 14:57 FLOYD $ Mon 17:00 KITT TPU Mon 16:57 62555::KITT MIRTH $ Wed 16:04 UCDVAX::MIRTH NATALIE $ Tue 09:23 64222::NATALIE RAPSONG $ Mon 18:50 64442::RAPSONG
To display details about one or more users on a remote host, specify the user name or a list of user names, including the host name with each user name, as shown in the examples that follow. To display more information about users on your local host, specify the user name(s) without a host name. The information about each user includes the following items in addition to the user (login) name, program, login time, and terminal/location that is returned in the default, brief display:
The following examples show how to display information about specific users.
$ FINGER HOWE@BEARINGS [bearings.us.beacorp.com] Username Program Login Term/Location HOWE MAIL Mon 15:02 84640::HOWE Login name: HOWE In real life: Abe Howe Account: INVENT Directory: DISK$1:[HOWE] Last login: Tue 14-MAR-1997 10:15:39 No unread mail Project: Inventory No Plan.
$ FINGER HOWE@BEARINGS JESSE@BEARINGS BILLINGS@CLASS [bearings.us.beacorp.com] Login name: HOWE In real life: Abe Howe Account: INVENT Directory: DISK$1:[HOWE] Last login: Tue 14-MAR-1997 10:15:39 No unread mail Project: Inventory No Plan. [bearings.us.beacorp.com] Username Program Login Term/Location JESSE $ Thu 09:24 Login name: JESSE In real life: JESSE BOYD Account: PLAN3 Directory: DISK$1:[JESSE] Last login: Mon 3-MAR-1997 16:48:50 Unread mail: 1 Project: Planning Plan: Next phase: December Email: jesse@bearings.us.beacorp.com Phone: 526-5444 [class.ucb.beacorp.com] Login name: billings (messages off) In real life: M. T. Billings Office: BLDG2-2, 236-8936 Home phone: 508-466-7873 Directory: /usr/users/billings Shell: /usr/bin/csh On since Jan 17 14:33:06 on :0 On since Jan 17 14:33:13 15 days Idle Time on ttyp1 On since Jan 17 14:33:13 2 days 23 hours Idle Time on ttyp2 On since Feb 4 13:13:50 2 days 23 hours Idle Time on ttyp5 No Plan.
$ FINGER DALB@BEARINGS @BEARINGS Username Program Login Term/Location Login name: DALB In real life: Bob Dalb Account: ENG_3 Directory: WORK1$:[DALB] Last login: Thu 6-MAR-1997 16:26:06 No unread mail Project: TCP/IP Services for OpenVMS No Plan. BRADY $ Thu 07:50 dialin_706_101.lkg.dec.com BYRD $ Mon 17:00 CORTEZ $ Tue 13:30 60121::CORTEZ DALB UCX$FINGER Thu 16:26 54242::DALB KURT $ Mon 16:57 32556::KURT LARSON SHWCLSTR Mon 17:01 MUELLER $ Wed 16:04 VALVE::MUELLER NASAN $ Tue 09:23 44500::NASON PHILLIPS $ Tue 02:42 REMHST::PHILLIPS ROLLINS $ Mon 18:50 46142::ROLLINS SIMMEL MAIL Thu 14:12 VALVE::SIMMEL
$ FINGER/ALL HOWE
To display information about users on all nodes in your local OpenVMS Cluster, use the /CLUSTER qualifier, as in the following examples.
$ FINGER/CLUSTER Username Node Program Login Term/Location ANND UCDAXP $ Mon 17:00 BRADY UCDAXP $ Thu 07:50 dialin_706_101.ucd.lab.edu CALLING UCDALP RTPAD Thu 14:50 CALLING UCDAXP $ Thu 14:57 CURREN UCDAXP $ Tue 13:30 84051::CURREN DOBB UCDWON UCX$FINGER Mon 11:50 GILBERT UCDVAX MAIL Thu 14:34 pcgil.admin.ucd.edu IMMIN UCDALP $ Wed 16:21 BIXBY::IMMIN KITT UCXAXP $ Mon 16:57 62555::KITT KITTEL UCXALP $ Thu 14:12 AGGIE::KITTEL LEVINE UCDUNI DECW$SESSION Thu 10:50 LEVINE UCDALP UCX$UCP Thu 10:30 llevine.philos.ucd.edu MILLLER UCDALP UCX$FINGER Thu 15:00 AGGIE::MILLER MIRTH UCDVAX $ Tue 17:09 MIRTH UCDVAX RTPAD Mon 17:27 NATALIE UCDAXP $ Tue 09:23 64222::NATALIE POFF UCXAXP $ Tue 02:42 AGGIE::POFF RAPSONG UCDAXP $ Mon 18:50 64442::RAPSONG TIBBS AGGIE $ Tue 20:43 UCXAXP::TIBBS
$ FINGER/CLUSTER/FULL Username Real Name Node Program Login Term/Location ANND Ann Darin UCDAXP $ Mon 17:00 UCDAXP $ Tue 11:51 BRADY Robert Brady UCDAXP $ Thu 07:50 dialin_706_101.ucd.edu UCDWON $ Fri 08:31 CALLING Alvin Calling UCDALP RTPAD Thu 14:50 UCDAXP $ Thu 14:57 CURREN Steve Curren UCDAXP $ Tue 13:30 84051::CURREN UCDVAX $ Tue 14:20 DOBB Barry Dobb UCDWON UCX$FINGER Mon 11:50 UCDAXP $ Wed 09:20 GILBERT Joanne Gilbert UCDVAX MAIL Thu 14:34 pcgil.admin.ucd.edu IMMIN Armen Immin UCDALP $ Wed 16:21 BIXBY::IMMIN KITT Evelyn Kitt UCXAXP $ Mon 16:57 62555::KITT UCDALP SEARCH Mon 16:43 62555::KITT KITTEL Herb Kittel UCXALP $ Thu 14:12 AGGIE::KITTEL LEVINE Larry Levine UCDUNI DECW$SESSION Thu 10:50 UCDALP UCX$UCP Thu 10:30 slevine.philos.ucd.edu MILLLER Paul Miller UCDALP UCX$FINGER Thu 15:00 AGGIE::MILLER MIRTH Phil Anson UCDVAX $ Tue 17:09 UCDVAX RTPAD Mon 17:27 NATALIE Natalie Beardsley UCDAXP $ Tue 09:23 64222::NATALIE POFF Pamela Offred UCXAXP $ Tue 02:42 AGGIE::POFF RAPSONG Aaron Feller UCDAXP $ Mon 18:50 64442::RAPSONG TIBBS Eugene Tibbs AGGIE $ Tue 20:43 UCXAXP::TIBBS
If your host does not have a direct connection to a remote host, you can use a forwarding host to get the information about users on that remote host. Your local host must be able to connect directly to the forwarding host, and the forwarding host must be able to connect directly to the destination. Specify the destination host and the forwarding host in the following format: username@destination_host@forwarding_host. For example, system UNION.CTSTATEU.EDU is not directly reachable, but you can get information from it indirectly through a gateway named U-GW.PA.ABCORP.COM. You would enter the following command to get information about user JONES on host UNION.CTSTATEU.EDU:
$ FINGER JONES@UNION.CTSTATEU.EDU@U-GW.PA.ABCORP.COM
By default, the Finger server does not allow queries to be forwarded
from one host to another. To enable forwarding on the Finger server,
see your system manager.
2.5 Making Your Information Available to Other Users
You can use the Finger utility to display a user's project and plans. The project (a single line of text) indicates the user's current project, work assignment, or work group. The user's plans can include several lines of information, such as where the user will be throughout the week, what the user plans to accomplish during the week, or even such information as the user's Web site, E-mail address, and telephone number, as in the following example:
I will be in my office Monday through Wednesday working at the S.F. lab. On Thursday and Friday, I will be at UC Irvine for a conference. Web site http://bio.ucd.edu/peters/r_peters.html
If you want to make such information about yourself available to other users through the Finger utility, create the following files in your home directory and add the appropriate information:
.PLAN | A file that contains your plans, whereabouts, and other information you want to have displayed. The file can contain more than one line. |
.PROJECT | A file that specifies your project and/or work group. The file can contain only one line. |
To use FINGER commands, type them at the DCL prompt.
This section provides a complete description of the FINGER command, its parameters, and qualifiers.
Displays information about users on a host. You can display:
- Brief listings of all users on a host
- Detailed listings about specific users
- Listing of users on a cluster
Specifying the FINGER command without a user or host specification displays information about users logged in on your local system.
FINGER [/ALL | /CLUSTER | /FULL] [username][@hostname]
username
Optional. Required for detailed information about a user.Specify the user login name. For information about a user on your local system, do not include the @hostname. For information about a user on a remote system, include the host name (username@hostname).
@hostname
Optional. Required for information about users on a remote system.For information about a specific user on a remote host, include the user name with the host name (username@hostname). For information about all users on the remote host, specify the host name only (@hostname). Omit the host name to display information about users on your local host.
/ALL
Optional. Use when specifying a local user name. The /ALL qualifier must follow immediately after the FINGER command.Displays a brief listing of all users in addition to detailed information about any specified users. Use this qualifier primarily for displaying information about users on the local host. The /ALL qualifier is ignored by most remote Finger servers when you specify a remote host name in the command line. To display brief information about all users on a remote host in addition to detailed information about specific users, specify the user@hostname format for each user plus @hostname (to list brief information about all users). Separate each user@hostname and @hostname specification with a space.
/CLUSTER
Optional. The /CLUSTER qualifier must follow immediately after the FINGER command. Do not specify a remote host name with this qualifier.Displays information about all users logged into the local OpenVMS Cluster system.
/FULL
Optional. The /FULL qualifier must follow immediately after the FINGER command.Displays detailed information such as the user's real name and all logins of the user (without /FULL, the display includes the last login only). Use this qualifier primarily for displaying information about users on the local host.
#1
$ FINGER FRANKEL@KCRA Username Program Login Term/Location FRANKEL $ Mon 15:10 KCRA::FRANKEL Login name: frankel In real Life: Sam Frankel Account: CC_Y9M Directory: WORK1$:[FRANKEL] Last login: Mon 29-MAR-1997 13:10:22 No unread mail No plan
#2Displays detailed information about user FRANKEL at host KCRA.
$ FINGER @OXYGEN [oxygen.gp.org] Username Program Login Term/Location BARD $ Mon 17:00 CASON LSEDIT Thu 14:57 CORR $ Tue 13:30 24151::CORR DUDLEY $ Mon 15:02 24646::DUDLEY GRAND $ Thu 07:50 NITROGEN::GRAND KURT $ Mon 16:57 22556::KURT KYLIE MAIL Thu 14:12 ELEMENT::KYLIE MYRA $ Wed 16:04 BIGVAX::MYRA NASON $ Tue 09:23 24200::NASON PHILLIPS $ Tue 02:42 BIGALP::PHILLIPS RAWLINGS $ Mon 18:50 24042::RAWLINGS
#3Displays brief information about users logged into host OXYGEN.
$ FINGER/FULL Username Real Name Program Login Term/Location BAIRD Randall Baird $ Mon 17:00 CARR Rich Carr LSEDIT Thu 14:57 SHWCLSTR Mon 17:01 CORTEZ Julia Cortez $ Tue 13:30 23441::CORTEZ DANBOY Dan Keller $ Thu 16:12 ogrady.ucsb.edu GANDHI T.J. Gandhi TPU Mon 16:57 12556::GANDHI TPU Tue 15:27 12556::GANDHI LIMO Michael Limorley MAIL Thu 14:12 TOPDAY::LIMO LSEDIT Thu 19:03 TOPDAY::LIMO MENNING Mark Menning $ Wed 16:04 TOPDAY::MENNING $ Mon 18:58 HAPDAY::MENNING NELSON Anne Nelson $ Tue 09:23 22200::NELSON ROBERTS Michael Roberts $ Mon 18:50 22042::ROBERTS $ Mon 18:34 HAPDAY::ROBERTS
#4Displays the real name and all logins for each user.
$ FINGER/CLUSTER Username Node Program Login Term/Location SMITH MOUNTB TPU Fri 09:47 MOUNTB::SMITH JONES MOUNTC $ Tue 18:02 BROWN MOUNTC $ Mon 17:04 TAYLOR MOUNTB EDT Thu 15:59 CROSBY MOUNTC RTPAD Thu 14:59 CARPENTER MOUNTB $ Wed 17:23 MOUNTB::SYSTEM BLACK MOUNTC $ Tue 10:42 MOUNTC::BLACK
Displays information about all users on all members of the cluster.
The DIGITAL TCP/IP Services for OpenVMS (UCX) software includes the File Transfer Protocol (FTP) service.
The following table lists the FTP file services and the sections that explain how to use them.
Capability | Section |
---|---|
Type either DCL-style or UNIX-style command syntax | 3.1 |
Customize the way FTP processes commands and file transfers |
3.3
3.6.2 |
Display all FTP commands sent to the remote host during command processing | 3.3 |
Display all replies from the remote host during command processing | 3.3 |
Gain access to OpenVMS files without specifying your user name or a password | 3.4.2 |
Use either OpenVMS or UNIX command syntax in command procedures that use FTP | 3.6 |
Set and display the default (working) directory on the local or remote host | 3.7 |
Create and delete remote directories | 3.8 |
View remote directories | 3.9 |
Delete a remote file | 3.10 |
Rename a remote file | 3.10 |
Append a local file to a remote file | 3.11 |
Display the contents of a file on a remote host | 3.12 |
Copy files from a connected remote host to your local host | 3.13.1 |
Copy files from your local host to the connected remote host | 3.13.2 |
Preserve OpenVMS file attributes when copying files to a UNIX system and back again | 3.13.6 |
Copy files to and from a DECnet node | 3.14 |
Print remote files at a printer connected to the local host | 3.15 |
Print a local file at a printer connected to a remote host | 3.15 |
Suspend FTP to spawn a subprocess at the DCL prompt | 3.16 |
What You Need
To use FTP, you need the following:
Command Summary
To use FTP, issue the commands summarized in Table 3-1 (for complete command descriptions see Section 3.17).
DCL-Style Command | Equivalent UNIX-Style Command |
Description |
---|---|---|
Starting and Exiting (At the DCL Prompt) | ||
FTP | ftp | Invokes FTP |
FTP remote_host | ftp remote_host | Invokes FTP and establishes a connection to a remote host |
Starting and Exiting (At the FTP> Prompt) | ||
CONNECT | open | Establishes a connection to a remote host |
DISCONNECT | close | Closes the connection with the remote host |
EXIT
Ctrl/Z |
quit | Closes the connection with the remote host and exits FTP |
Sending Commands to the Remote Host | ||
APPEND | append | Appends a local file to a remote file |
CREATE/DIRECTORY | mkdir | Creates a remote directory |
DELETE |
delete
mdelete |
Deletes remote files |
DIRECTORY | ls | Lists remote file names and related information |
GET |
get
mget |
Copies files from the remote host to the local host |
LOGIN | user | Logs you into a remote host |
PUT |
put
mput |
Copies files from the local host to the remote host |
RENAME | rename | Renames remote files |
SET DEFAULT |
cd
lcd |
Sets the remote working directory or the local working directory |
SHOW DEFAULT | pwd | Displays the name of the current working directory |
VIEW | view | Displays the contents of a file on the current output device. |
Suspending FTP to Return to DCL Prompt | ||
SPAWN | ! | Suspends FTP to create a subprocess at the local DCL prompt |
Customizing Your Session's Environment | ||
DISABLE LOG | debug | Disables the display of all the protocol commands sent to the remote host |
DISABLE PARSE | glob+ | Disables the expansion of file names |
DISABLE
PORT_COMMAND |
sendport+ | Disables the sending of the FTP protocol PORT command |
DISABLE REPLY | debug+ | Disables the display of all responses from the remote host |
DISABLE
TRANSFER_VERIFICATION |
hash+ | Disables the display of # for each 1K bytes of data transferred |
DISABLE
VMS_PLUS |
N/A | Disables the special OpenVMS-to-OpenVMS transfer mode |
ENABLE LOG | debug | Enables the display of all protocol commands sent to the remote host |
ENABLE PARSE | glob+ | Enables the expansion of file names |
ENABLE
PORT_COMMAND |
sendport+ | Enables the sending of the FTP protocol PORT command |
ENABLE REPLY | debug+ | Enables the display of all responses from the remote host |
ENABLE
TRANSFER_VERIFICATION |
hash+ | Enables the display of # for each 1K bytes of data transferred |
ENABLE
VMS_PLUS |
N/A | Enables the special OpenVMS-to-OpenVMS transfer mode |
HELP | ? | Invokes help |
QUOTE | quote | Sends FTP commands to the remote host without local interpretation |
SET TYPE | type | Defines the data representation for file transfers |
SHOW STATUS | status | Displays the current FTP parameter settings and, if you have an open connect, the name of the connected host |
SPAWN | ! | Spawns a subprocess at the DCL prompt |
Use the following rules for command syntax, quotation marks, and
wildcards when you type FTP command lines.
3.1.1 DCL and UNIX Command Formats
With the FTP command and most of the commands at the FTP prompt, you can use either DCL-style or UNIX-style syntax. For example, the DCL-style DIRECTORY and UNIX-style ls commands produce the same results, as shown in the following example:
FTP> DIRECTORY/BRIEF *.DIR 200 PORT command successful 150 Opening data connection for DISK$2:[FLIGHT]*.DIR (11.21.308.100,2643) com.dir;1 dis.dir;1 mail.dir;1 226 NLST Directory transfer complete. 43 bytes received in 00:00:00.09 seconds (0.42 Kbytes/s) FTP> FTP> ls *.dir 200 PORT command successful 150 Opening data connection for DISK$2:[FLIGHT]*.DIR (11.21.308.100,2644) com.dir;1 dis.dir;1 mail.dir;1 226 NLST Directory transfer complete. 43 bytes received in 00:00:00.04 seconds (1.02 Kbytes/s) FTP>
When you communicate with a non-OpenVMS host, you need to enclose the following with quotation marks: