Remote Node Definition Operations

There are four operations associated with remote node definitions:

Adding new definitions
Merging new definitions
Deleting existing definitions
Viewing existing definitions

To perform each of these operations, netu asks for the following information:

The vnode name of the remote node
The network protocol used by the remote node
The remote node address
The listen address of the Communications server at the remote node

Add or Merge Remote Node Definitions

A remote node definition identifies a particular node and a listen address for that node's Communications server and associates that node and address combination with a vnode name.

When a user uses a vnode name to connect to a database on a remote instance, the local instance must have a remote node definition that defines that vnode name for the remote instance to complete the connection. The netu utility offers two options for adding remote node definitions: add and merge.

Add and merge differ in how they handle the addition of a node definition whose vnode name matches the vnode name of an existing node definition. If you are using the add option, netu overwrites any existing node definitions that have the matching vnode name. If you are using the merge option, netu does not overwrite the existing definitions, but simply establishes another definition. The merge option is very useful if you want to run more than one Communications Server at a server node.

For example, assume that you want to run three Communications Servers at the node "eugenie." Each server has its own unique listen address for interprocess communications. If you use the add option to establish the remote node definitions for "eugenie" from "napoleon," you must provide a unique vnode name for each listen address. For example, you have the following vnode name and listen address combinations:

From napoleon:

Royal addr1
Lady addr2
Second addr3

If you use the merge option, you need only one vnode name. Using merge, set up the three node definitions at "napoleon" using the same vnode name for each and simply changing the listen address.

For example:

From napoleon:

Royal addr1
Royal addr2
Royal addr3

When users connect using the vnode name "Royal" Ingres Net connects them to one of the three Communications Servers. Ingres Net automatically tries each server, in random order, until it finds one of the three that is available. Users do not need to remember three vnode names or make three connection attempts. Using merge allows you to keep it simple for users, regardless of how many Communications Servers are running on an installation.

Note: Ingres Net does not allow two definitions that are exactly the same at the same node.

To add or merge a remote node definition

Start netu by entering netu at the operating system prompt.
The netu menu appears.
Select N (Modify Node Entry) from the menu.
The following prompt appears:

Enter command (add, merge, del, show, exit):
Select add or merge. (Type a or m instead of the full word.)
The add and merge options behave differently if the definition you are adding matches an existing vnode name. Be sure to read the paragraphs preceding this procedure before making a choice.
Define the account as a private or global account. The default is private.
- To accept the default, press Enter.
- To define a global node entry, enter G. You must be a user with Ingres privileges to define a global node entry.
Enter a remote vnode name.
Enter the network software type.
This is the name of the protocol that the remote node is using. For a list of valid entries see Network Protocol Keywords.
Enter the remote node address.
Enter the listen address of the remote node's Communications Server.
Netu adds one remote node definition for your local node and displays this prompt:

Enter operation (add, merge, del, show, exit):
Select another operation or select exit to Enter to the netu menu.

Delete Remote Node Definitions

To remove a remote node definition from a local node, the netu utility allows you to remove one or several definitions at a time. When you select the operation that deletes node definitions, netu responds with a series of prompts. When you have answered all the prompts, netu deletes all node definitions that match the answers you supplied.

To remove several definitions at once, use the asterisk (*) in response to the appropriate prompt. This is a wild card character that matches any entry. For example, if you want to remove all private node definitions for the vnode name "general," complete the deletion procedure, responding to the prompts in the following manner:

Enter Private or Global (P): <Enter>
Enter the vnode name of the remote node: general
Enter the node address of the remote node: *
Enter the network software type:
Enter the remote node address: *
Enter the remote Ingres/Net server listen address:
appropriate address

You cannot answer with an asterisk in response to the Global or Private prompt.

To remove node definitions from the local Communications Server

Start netu by entering netu at the operating system prompt.
The netu menu appears.
Select N (Modify Node Entry) from the menu.
The following prompt appears:

Enter command (add, merge, del, show, exit):
Enter del. (Type d in place of del.)
When netu asks you to specify if the definition is a private or global definition, do one of the following steps:
- If the node definition is private, press Enter.
- If the node definition is global, enter G. You must be a user with Ingres privileges to select G.
Enter the vnode name of the remote node. Enter the network software type.
This is the name of the protocol that the remote node is using. Valid entries are described in Network Protocol Keywords.
Enter the node address of the remote node.
Enter the listen address of the remote node's Communications Server.
Netu removes the node definition(s) from the local Communications Server and displays the following prompt:

Enter command (add, merge, del, show, exit):
Select another operation, or Enter to the netu menu by entering exit.

How You Change Remote Node Definitions

The procedure you use for changing an existing remote node definition depends on whether the vnode name for the definition is unique among the node definitions for the installation.

If the vnode name is unique (that is, associated with only one node definition), overwrite the existing definition. For instructions, see Overwrite an Existing Definition.

If the vnode name is not unique (that is, associated with more than one node definition), you must delete the incorrect definition and set up the new definition. For instructions, see Delete Old and Add New Definition.

Overwrite an Existing Definition

Use this procedure to change a node definition only if the vnode name associated with that definition is not associated with any other node definitions within the local set of remote node definitions.

To overwrite an existing definition

Start netu by entering netu at the operating system prompt.
The main menu appears.
Select N (Modify Node Entry) from the menu.
The following prompt appears:

Enter the operation (add, merge, del, show, exit):
Enter add. (Type a instead of add.)
Prompts appear.
Answer the prompts using the values of the new, correct node definition.
The utility overwrites the existing node definition with the values that you have just supplied and displays the following prompt:

Enter operation (add, merge, del, show, exit):
Continue with other node definition tasks or Enter to the netu menu by choosing exit.

Delete Old and Add New Definition

Use this procedure when there are two or more remote node definitions (at the same node) that are associated with the vnode name belonging to the definition that you want to change.

When the merge option has been used to set up several node definitions that use the same vnode name, you must be very careful when changing one of these definitions. You cannot overwrite the incorrect definition using the add option as in Overwrite an Existing Definition. If you try to do this, netu overwrites all of the definitions that have the specified vnode name, effectively deleting them all and leaving you with only the definition you have just added.

To safely change a node definition that has a vnode name in common with other node definitions, you must delete the old definition and use merge to add the new definition.

To delete an old definition and add a new one

Start netu by entering netu at the operating system prompt.
The main menu appears.
Select N (Modify Node Entry) from the menu.
The following prompt appears:

Enter operation (add, merge, del, show, exit):
Enter del. (Enter d instead of del.)
Answer the prompts that appear with the values from the definition you want to change.
When all the prompts are answered, netu deletes the node definition that has the values that you have just supplied and Enters you to the prompt:

Enter operation (add, merge, del, show, exit):
Enter merge. (Enter m instead of merge.)
Answer the prompts that appear with the values for the correct definition.
The utility adds a node definition with the values that you have just supplied and displays the following prompt:

Enter operation (add, merge, del, show, exit):
Continue with node definition tasks or Enter to the main netu menu by choosing exit.

Retrieve Remote Node Definition Information

To see the remote node definitions associated with a particular local node, the following procedure asks for information about the definitions and displays all the definitions that match the information you provide.

Use an asterisk in response to any prompt other than the one asking if the definition is private or global. An asterisk is the wild card character that matches any value.

To retrieve remote node definition information

Start netu by entering netu at the operating system prompt.
The netu menu appears.
Select N (Modify Node Entry) from the menu.
This prompt appears:

Enter operation (add, merge, del, show, exit):
Enter show. (Type s instead of show.)
When netu asks if the entry you want to see is a private or global entry, do one of the following:
- If the entry is private, press Enter.
- If the entry is global, enter G.
Enter the vnode name of the remote node definition.
Enter the network software type.
Enter the remote node's address.
Enter the listen address of the remote node's Communications Server.
The utility displays all of the definitions that match the information that you gave. If you used an asterisk as a wild card for any of the prompts, you receive more than one definition. The definitions appear in table format. You cannot change any node name definition while it is displayed in this format.

After the definition or list of definitions is displayed, the utility displays the following prompt:

Enter operation (add, merge, del, show, exit):
Continue with node definition tasks or choose exit to Enter to the netu menu.

Displayed Node Definition Examples

Here are some examples of the format and type of information that you receive when you retrieve node definition information for viewing.

Windows: The following table shows Windows Displayed Node Definition examples:

Global:	V_Node	Net Software	Node Address	Listen Address
	london	wintcp	uk1	II0
	rome	wintcp	italy2	II0
	n_york	wintcp	usa1	II0
	chicago	lanman	usa2	USA2_II

UNIX: The following table shows UNIX Displayed Node Definition examples:

Global:	V_Node	Net Software	Node Address	Listen Address
	london	tcp_ip	uk1	II0
	rome	tcp_ip	italy2	II0
	n_york	tcp_ip	usa1	II0

VMS: The following table shows VMS Displayed Node Definition examples:

Global:	V_Node	Net Software	Node Address	Listen Address
	n_york	sna_lu0	GW1	NYMVSPLU
	chicago	sna_lu0	GW2	CHMVSPLU
	london	decnet	uk1	II_GCC_0
	rome	decnet	rome	II_GCC_0
	s_fran	decnet	s_fran	II_GCC_0
	n_york	tcp_wol	usa1	II
	chicago	tcp_wol	usa2	KK