remote File Format for tip

Purpose

Describes remote systems contacted by the tip command.

Description

The /etc/remote-file file describes the remote systems that can be contacted using the tip command. When a user invokes the tip command, the command reads the remote file to find out how to contact the specified remote system. If invoked with the SystemName parameter, the tip command searches the remote file for an entry beginning with that system name. If invoked with the PhoneNumber parameter, the command searches the remote file for an entry beginning with tipBaudRate, where BaudRate designates the baud rate to be used for the connection.

Any tip user can create an individual remote file in the format of the remote file. The individual remote file can be named with any operating system file name and placed in any directory to which the user has access. To instruct the tip command to use the new file, set the REMOTE environment variable before issuing the tip command, or use the tip command remote variable.

A sample remote file for tip is included with the operating system. The sample file is named /usr/lib/remote-file. This sample file contains two examples, either of which is a complete remote file. One of the examples uses a set of general dialer definitions, followed by general system definitions, and specific systems. The second example defines each system individually.

Any user can copy the sample file to some other directory and modify it for individual use. A user with root user authority can copy the sample file to the /etc/remote file and modify it to suit the needs of a particular site.

Format of Entries

The general format of an entry in the /etc/remote-file file is a system name, baud rate, or dialer name followed by a description and one or more attributes, as follows:

OR

OR

The name of the system or dialer is followed by a | (pipe symbol) and a description of the system or dialer. More than one system or dialer name can be given; in this case, they must be separated by pipe symbols and precede the Description parameter. The last section in this list is always treated by the tip command as a description, not a system name.

The Description field is followed by a : (colon) and a list of attributes separated by colons. Each entry must also end with a colon.

An entry can be continued on the next line by typing a \ (backslash). The continuation line must begin with a : (colon) and can be indented for readability.

Any line beginning with a # (pound sign) is read as a comment line.

Note: Spaces can be used only within the Description parameter or in comment lines.

Attributes Used to Define Systems and Dialers

Use the following attributes to describe systems in the remote file:

Setting Up Group Entries

Set up entries in the remote file in two ways. Define each system individually, giving all of its attributes in that entry. This works well if you are contacting several dissimilar systems.

Or group the systems by similarity. To do this, use two or three groups, depending on how the systems are similar. The groups can be arranged by:

• Dialer definitions, including the device, baud rate, call unit, ACU type, and dial-up flag.
• General system definitions, including any information that several systems have in common. Use the tc attribute to refer to a dialer entry.
• Specific system descriptions, which use the tc attribute to refer to one of the general system types or a dialer entry.

You can omit either the dialer definitions or the general system definitions, depending on the way the remote systems are grouped.

Examples

Defining a System Individually

To define a system without using the tc= attribute, enter:

vms750|ghost|NPG 750:\
   :dv=/dev/tty36,/dev/tty37:br#9600:el=^Z^U^C^S^Q^O:\
   :ie=$@:oe=^Z:

This entry defines system vms750 , which can also be referred to as ghost . The system can be accessed using either /dev/tty36 or /dev/tty37 , at a baud rate of 9600 . The end-of-line mark is ^Z^U^C^S^Q^O . The input end-of-file mark is $@ and the output end-of-file mark is ^Z . Since no phone number is defined, the system is accessed over a direct connection.

Grouping Systems by Similarity

The following examples use a dialer entry and a general system entry, followed by specific system entries that refer to the general entries.

1. To define a dialer, enter:

   
   dial1200|1200 Baud Able Quadracall attributes:
   \   :dv=/dev/cul1:br#1200:at=dn11:du:

   This entry defines a dialer called dial1200 . The dialer is connected to device /dev/cul1 and is an ACU type of dn11 . The dial-up (du ) flag is set.

2. To define a general system type and refer to a dialer entry, enter:

   unix1200|1200 Baud dial-out to another UNIX system:\   :el=^U^C^R^O^D^S^Q:ie=%$:oe=^D:tc=dial1200:

   This entry defines a system type called unix1200 . The end-of-line mark for communication with this type of remote system is ^U^C^R^O^D^S^Q . The input end-of-file mark is %$ and the output end-of-file mark is ^D . The dialer defined by the dial1200 entry is used.

3. To describe a specific system, enter:

   zeus|CSRG ARPA VAX-11/780:pn=@:tc=unix1200:

   This entry describes system zeus , which is described as a CSRG ARPA VAX-11 . The tip command then searches the /etc/phones file for the telephone number (pn=@ ) and uses the attributes of a unix1200 system type (tc=unix1200 ).

Implementation Specifics

This file is part of the Basic Networking Utilities Program (BNU) in BOS Extensions 1.

Files

Related Information

The tip command.

The Contacting Connected UNIX Systems Using the tip Command in AIX Version 4.3 System Management Guide: Communications and Networks.