Listening Entries

The ROUTE-FILE normally contains one listening entry for each type of network. However, you will require additional listening entries under the following circumstances:

To create a new listening entry, at the Entry type  prompt, enter 2  for ‘Listening’. You will see the following prompts:

  1. Enter System Name [q] :

    Each Listening entry must have a unique system name. It must contain at least one character (it cannot be the single letter ‘q’) and must not be greater than 49 characters in length.

  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 must be used for connections from Northgate Series 18/19 systems.

    full OSI full network connection. This is preferred for OSI connections from Northgate UNIX systems.

    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.

    Notes

    • You will only need one listening loopback entry. You will, however, need at least one destination loopback entry.
    • On some types of system, local loopback is not available. An alternative is described in Destination Entries.

    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 Northgate support representative.

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

  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 this listening entry for all OSI network interfaces (multibind) [y, (n), q] :

    This prompt is only displayed if the provider type is ONE. See Types of Entry.

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

    Each connection can be defined as character mode or DDA mode. 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.

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

  7. Is it an ICL entry [y, (n), q] :

    • If the listening entry will accept incoming calls from ICL systems enter y. You will be prompted for additional information – refer to the ROSI-ICL System Administration Guide for details.
    • Otherwise, press RETURN to accept the default.

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

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

  8. port number : default 1203 :

    This prompt is only displayed for TCP connections. The port number should not normally be changed – press RETURN to accept the default.

  9. host name :

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

    • For TCP connections, the host name should normally be “anyhost” or IP address 0.0.0.0. Alternatively, you can use the name of the local host as displayed by hostname or unname -n. Note that, in the latter case, the host name must exist in the file /etc/hosts or, if you are using a Domain Name Service (DNS), be recognised by the DNS.

      If your host has multiple physical network interfaces, you should set the host name to “anyhost” unless you wish to restrict the entry to listening on a particular interface.

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

    If you are adding an X25, XUI or TCP entry, go to step 14.

  10. 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.

    • To accept the default TSAP, press RETURN.
    • To alter the TSAP, enter y. The following prompt is displayed:

      TSAP [q]:

      Enter the required TSAP.

  11. default ethernet address : EthernetAddress
     
     alter default ? [y,(n),q] :

    This prompt is only displayed for OSI null network connections.

    • Press RETURN to accept the default Ethernet address – you will see the following:

      Ethernet address is EthernetAddress

    Note: You will normally only need to alter the Ethernet address on systems with multiple physical network interfaces (for example, Heartbeat systems) – for details, contact your Northgate support representative.

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

    This prompt is only displayed for OSI full network connections (but not if ONE, multibind has been selected).

    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 NSAP format, press RETURN. The following prompts are displayed:

    default ethernet address : EthernetAddress
    
    alter default ? [y,(n),q] :

    Note: You will normally only need to alter the Ethernet address on systems with multiple physical network interfaces (for example, Heartbeat systems) – for details, contact your Northgate support representative.

    Press RETURN to accept the default Ethernet address – you will see the following:

    Ethernet address is EthernetAddress
    NSAP is Nsap

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

  13. PLId generation to use called TSAP instead of calling TSAP ? [y, (n), q] :

    This prompt is only displayed for character mode listening entries. Answer y  (yes) if you are using Location Based Security and connection is via a non-Northgate terminal server that does not associate a TSAP with each physical port. When this option is selected, the entry is known as a Type 2 listening entry. See Types of Entry and Network Security for more details.

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

  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        : MX2
    Entry type         : listening
    Device             : /dev/rcs/tcp0
    Interface type     : TLI
    Provider type      : TCP
    Port Number        : 1203
    Host Name          : mx2
    Network info       : 
    Comment            : 
    
    commit entry [y,n,q]:
    • Enter y  to confirm the entry.
    • Enter n  or press RETURN to leave the ROUTE-FILE unchanged.

    Note: After adding a Listening entry, you must use the rcslisten command to enable the session manager to accept incoming calls for the new entry.

Go to top button