Destination Entries

You will need a destination entry for each remote system to which your local system connects.

At the Entry type  prompt, enter 1  for 'Destination'. You will see the following prompts:

1. Enter System Name [q] :

   Each destination system name must be unique. It must contain at least one character (it cannot be the single letter 'q') and must not be greater than 49 characters in length.

   Note that the system name is the name by which the destination system is known to your local system. It will normally be the same as the network name of the destination system (on UNIX systems, the name displayed by the uname -n command), but could be a local alias. You might, for instance, create multiple entries for the same destination system, with each using a different protocol, by giving each entry a different system name.

2. network type
 
 1. null
 2. full
 3. local loopback
 4. x25
 5. xui
 6. tcp
 
 Enter type [q] :

   Enter the network type (1 to 6) as follows:

   null

   OSI null network connection. This was used for connections to NEC Software Solutions Series 18/19 systems and is no longer relevant.

   full

   OSI full network connection. This may be used for OSI connections to NEC Software Solutions UNIX systems, although TCP is generally preferred to OSI.

   local loopback

   A local loopback entry is required for:

   • Communication between client programs on Reality databases and servers on the local UNIX system.

   • SovereignX Background Processors.

   • SovereignX printing.

   Note

   • You will not normally need more than one destination loopback entry. You will, however, need a corresponding listening loopback entry.

   • To use a local loopback entry, you will also need one or more Q-type entries.

   • On some types of system, local loopback is not available. If an open device failure error occurs when attempting local communication, try using a TCP or OSI full network destination entry instead, specifying the local host as the destination. You will also need a listening entry for the chosen protocol.

   x25

   For connections via an X.25 network.

   xui

   For X.25 User Interface connections.

   tcp

   TCP/IP network connection.

3. default device : defaultDevice
 
 alter default ? [y,(n),q] :

   You should normally press RETURN to accept the default device driver.

   Note

   You will normally only need to alter the device driver on systems with multiple physical network interfaces (for example, Heartbeat systems); for details, contact your NEC Software Solutions support representative.

   If you are adding a local loopback entry, go to step 14.

4. Provider type
 
 1. PCLINK2
 2. Retix
 3. Series X X25
 4. TCP
 5. OSI-DP
 6. ONE
 
 default : default provider type
 
 enter type [q] :

   You must accept the default provider type. Press RETURN.

5. Is it a character mode entry [y, (n), q]:

   Each connection can be defined as character mode or DDA. See Connection Type for details of when to use DDA and when to use character mode.

   • For character mode connections, enter y.

   • Otherwise, press RETURN to accept the default, DDA connection type.

   Note

   This prompt is not displayed for X.25 User Interface (XUI) connections.

   If you are adding an OSI entry, go to step 8.

6. port number: default 1203:

   This prompt is only displayed for TCP connections:

   • For connections to other computers, it should not normally be changed - press RETURN to accept the default.

   • For connections to networked printers, enter the port number appropriate to your printer. Refer to Adding a Network Printer for more information.

7. host name:

   This prompt is only displayed for TCP, X.25 or XUI connections.

   • For TCP connections, this must be one of the following:

     • The name of an entry in your /etc/hosts file.

     • A host name recognised by your Domain Name Service(DNS).

     • The IP address of the required host.

     • A question mark. This defines the entry as a skeleton destination entry.

   • For X.25 and XUI connections, enter the name of the remote host as specified in your local X.25 configuration file.

   If you are adding a character mode entry, go to step 11. Otherwise, go to step 14.

8. change TSAP address: default 02,tsap [y,(n),q]:

   This prompt is only displayed for OSI (null and full) network entries. tsap is the default TSAP - 0203 for DDA connections or 0202 for character mode connections. Note that the TSAP must be the same as that used in the appropriate listening entry on the destination system.

   • To accept the default TSAP, press RETURN.

   • To alter the TSAP, enter y. The following prompt is displayed:

     TSAP [q]:

     Enter the required TSAP.

9. Ethernet address [q] :

   This prompt is only displayed for OSI null network connections. Enter the Ethernet address of the remote system. An Ethernet address is always 12 hexadecimal characters.

10. Authority & Format Identifier : default 49 [q] :

    This prompt is only displayed for OSI full network connections.

    To accept the default AFI, press RETURN. The following prompt is displayed:

    change NSAP format ? : default 490001<ethernet_address>01 [y,(n),q] :

    To accept the default NSAP format press RETURN. The following prompt is displayed:

    Ethernet address [q] :

    Enter the Ethernet address (12 hexadecimal characters).

    Note

    Refer NSAP Format Option for details of how to enter an NSAP in a format other than the default.

    Unless you are adding a character mode entry, go to step 14.

11. Is this destination either for use by NPU (Network
 Printing Utility) or for a device which requires
 Call User Data (eg. NetworkX) ? [y,(n),q] :

    • Enter y  if you are configuring a network printer or a device that requires Call User Data (for example, NetworkX).

    • Enter n  for any other type of character mode connection (for example, terminal connections to non-NEC systems).

    If you have entered n, go to step 14.

12. NPU type
  
  1. Telnet
  2. MPS 'FF'
  3. SPAG Y/13
  4. DDA
  5. LPR
 
 Other types
 
 6. NX (Network X)
 7. General CUD
 
 enter type : default raw [q] :

    • Options 1 to 5 are additional protocols for npu.

    • If you are connecting via NetworkX, enter 6.

    • If you are not connecting via NetworkX, but your connection requires Call User Data, enter 7.

    • If you do not require an additional protocol or Call User Data, press RETURN without typing an option number.

13. If you have selected option 6 or 7 above, you will be prompted:

    Call User Data (hexadecimal) : [q] :

    Enter the required Call User Data. For NetworkX, refer to your NetworkX manuals for details.

    Note that the five npu protocol options also require additional data.

14. Comment:

    The comment line may be up to 78 characters of alphanumeric text, describing the ROUTE-FILE entry.

15. Finally, the complete entry is displayed, as in the example below.

    System name        : SYS1
    Entry type         : destination
    Device             : /dev/rcs/tp4-fnw0
    Interface type     : TLI
    Provider type      : ONE
    TSAP               : 0203
    NSAP               : 49000108001122334401
    Network info       : 
    Comment            : full network, DDA
    commit entry [y,(n),q] :

    • Enter y  to confirm the entry.

    • Enter n  or press RETURN to leave the ROUTE-FILE unchanged.