DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration

* Object name?                                           :

Specify the DECdns full name of the object for which the sink accepts incoming connections. Unless the value of this characteristic is null, the sink employs the Session Control layer's Keep me Here function to maintain the object name in the namespace.

* End user specification?                                :

Specify the Digital Network Architecture (DNA) Session Control local address for which the sink accepts incoming connections (for example, number=82).

* Catch all filter action?                               :

Specify the action to take if neither the specific filter setting nor the global filter setting matches an event, or if a filter setting that matches an event is set to ignore. The choices are:

BLOCK --- Discard the event.
PASS --- Report the event.

* Description?                                           :

Specify an informational string that can be used to describe the sink.

* Display UIDs?                                          :

Answering YES displays the entity's unique identifier, which is generated when the entity is created.

* Client type?                                           :

Specify how the application is to accept the events received by the sink. The choices are:

CONSOLE --- Events go the operator's console (OPCOM).
DEVICE --- Events go to a device.
FILE --- Events go to a file.

If you answer FILE to the "Client type?" prompt, the procedure displays the following prompt:

* File name?                                              :

Enter the file specification you want to use to capture events (for example, sys$manager:evd_events.log).
If you answer DEVICE to the "Client type?" prompt, the procedure displays the following prompt:

* Device name?                                            :

Enter the device you want to use to capture events (for example, TWA1:).

* Configure another Sink?                            [NO] :

If you do not want to configure another sink, press Return to proceed to the next prompt. If want to configure another sink, enter YES and press Return. The procedure returns you to the "Sink name?" prompt and repeats the prompts required to configure another sink.

If you want to configure an outbound stream, answer YES.

* Configure an Outbound Stream?                     [YES] :

Specify the outbound stream name that you want to manage with this command (for example, local_stream).

* Outbound Stream name?                    [local_stream] :

Specify the number of octets that the outbound stream allows to process events. This value is derived from (but is not necessarily equal to) the value specified in the maximum buffer size argument of the create command (for example, 16384).

* Maximum buffer size?                                    :

Specify the number of seconds to wait between connection attempts. The connect retry timer operates continuously from the time the outbound stream is enabled until the stream is disabled or until the connect timer enabled characteristic is set to FALSE. If the outbound stream is already connected to the sink when the timer expires, no connection is attempted at that time. The timer resets and connection attempts continue whenever the timer expires.

* Connect retry timer?                                    :

Answer YES to have the connect retry timer operational. Answer NO to disable it.

* Connect timer enabled?                                  :

Specify the number of seconds to wait before shutting down an idle connection. A 0 value indicates that the disconnect timer is not operating and that connections are never disconnected automatically.

* Disconnect timer?                                       :

Specify the action to take if neither the specific filter setting nor the global filter setting matches an event or if a filter setting that matches an event is set to Ignore. The choices are:

BLOCK --- Discard the event.
PASS --- Report the event.

* Catch all filter action?                                :

Specify the full DECdns object name of the sink associated with this outbound stream. This object name is used to make the connection with the sink.

* Sink object?                                             :

Specify the full node name (DECdns namespace name included) of the sink associated with outbound stream.

* Sink node?                                               :

Specify the sink Session Control end user specification of the sink associated with this outbound stream (for example, number=82).

* Sink end user?                                           :

Specify the sink address tower of the sink associated with this outbound stream.

* Sink address?                                            :

If you do not want to configure another outbound stream, press Return to proceed to the next prompt. If you want to configure another outbound stream, enter YES and press Return. The procedure returns you to the "Outbound Stream name?" prompt and repeats the prompts required to configure another outbound stream.

* Configure another Outbound Stream?                  [NO] :

Answer YES to use the Phase IV Relay. This allows you to record and process events that occur on an OpenVMS system running DECnet-VAX Phase IV software. The Phase IV Relay entity receives the events from a Phase IV node, encapsulates them, and posts them in the DECnet-Plus system Event Dispatcher.

* Configure Phase IV Relay?                          [YES] :

The procedure displays:

 
                      Summary of Configuration 
 
 
 Node Information: 
      Directory services chosen:        DECDNS,LOCAL,DOMAIN 
      Primary directory service:        DECDNS 
      DECdns full name:       ACME:.WABBIT.ELMER 
      Local Full name:        LOCAL:.ELMER 
      Fully Qualified 
      Host name:              ELMER.WABBIT.ACME.EDU 
      Node Synonym:           ELMER 
      Phase IV Address        15.27 
      Phase IV Prefix:        49:: 
      Autoconfiguration of Network Address: Enabled 
      Session Control Address Update Interval:      10 
      Routing ESHello Timer:  600 
  
 
 Device Information: 
      Device: XQA0 (DELQA): 
               Data Link name:  CSMACD-0 
               Routing Circuit Name:    CSMACD-0 
 
      Device: ASYNC (floating async line): 
               Data Link name:  ASY_DDCMP-0 
               Routing Circuit Name:    ASY_DDCMP-0 
 
 
 Transport Information: 
         NSP Transport:                          Configured 
          Maximum number of logical links:         200 
          Maximum Transmit and Receive Window:     20 
          Maximum Receive Buffers:                 4000 
 
        OSI Transport:                          Configured 
          Maximum number of logical links:         200 
          Maximum Transmit and Receive Window:     20 
          Maximum Receive Buffers:                 4000 
        Congestion Avoidance Disabled 
 
 
 Event Dispatcher Configuration: 
       Sinks:            local_sink 
       Outbound Streams: local_stream 
       Phase IV Relay:   Enabled 
 
* Do you want to generate NCL configuration scripts? [YES] :

If you answer YES, the configuration program uses the information you entered to create the Event Dispatcher NCL script. The configuration program then returns to the Configuration Options menu. To implement the Event Dispatcher NCL script, reboot the system or disable the entity and execute the script.
If you answer NO, the configuration procedure returns to the Configuration Options menu and does not generate NCL scripts.

3.9 Reconfiguring the Application Database

To reconfigure the application database, proceed as follows from the Configuration Options menu:

* Which configuration option to perform?                 [1] : 7

Select Option 7 and press Return.

* Do you want to ADD or DELETE an Application?         [ADD] :

Answer ADD to create the application entity on the local node, allocate resources for it, and open the service interface. Answer DELETE to delete the entity and reclaim associated resources. Entering either ADD or DELETE in reply to this prompt displays the following prompt. The NOTES application is used here as an example.

* What is the name of the Application?                        : NOTES

When defining an application, you must identify the name of the object. DECnet object names are descriptive alphanumeric strings of up to 12 characters.

If you are deleting an application, the procedure displays the following two prompts. If you are adding an application, the procedure skips the next two prompts.

* Are you sure you want to DELETE this application?      [NO]:

If you want to delete the application, answer YES.

* Do you want to generate NCL configuration scripts?   [YES] :

If you want to generate the NCL configuration scripts, answer YES.

If you are adding an application, the procedure displays the following prompt:

* What is the destination type for 'notes'?           [NAME] :

The destination type can be either NAME or NUMBER. To select NAME, press Return. To select NUMBER, enter NUMBER and press Return.

If you select NAME, the procedure displays the following prompt:

* What is the destination name for 'notes'?                 :

Your reply to this prompt can be either the application name (for example, NOTES) or a destination object name (for example, IAF:.SALES.BOSTON). The destination name is the DECdns full name of the node that provides the application.

The application name can be from 1 to 16 characters. The destination object name can be a maximum of 512 characters and is entered in this format:

NamespaceNickname:.DirectoryPath.NodeObject

If you enter NUMBER, the procedure displays the following prompt:

* What is the destination number for 'notes'?                : 33

DECnet software uses object numbers as unique object identifiers. Object numbers have a range of 1 to 255. Generic objects such as MAIL and FAL have object numbers that are recognized throughout the network. User-defined images can have unique object numbers; numbers between 128 and 255 are reserved for this purpose.

For the NOTES application, enter 33 at this prompt. (This is the number that Digital uses for this application.)

If you are adding a user-defined application, choose a number from 128 to 255. If you are adding an application defined by Digital, select the appropriate number from Table 3-3.

Table 3-3 Object Type Numbers
Number Mnemonic Description

0 Task User program

1--16 Reserved for Digital use

17 FAL File access listener for remote file and record access

18 HLD Host loader for RSX-11S downline task loading requests

19 CML CMIP Management Listener object

20 RSTS/E media transfer program (NETCPY)

21--22 Reserved for Digital use

23 REMACP Network terminal handler (host side)

24 Network terminal handler (terminal side)

25 MIRROR Loopback mirror

26 EVL Event receiver

27 MAIL OpenVMS Mail utility

28 Reserved for Digital use

29 PHONE OpenVMS Phone utility and RSX-11M/M-PLUS Phone utility

30--41 Reserved for Digital use

42 CTERM Network terminal handler

43--62 Reserved for Digital use

63 DTR DECnet Test Receiver object

64--127 Reserved for Digital use

128--255 Reserved for customer use

**Table 3-3 Object Type Numbers**
Number	Mnemonic	Description
0	Task	User program
1--16		Reserved for Digital use
17	FAL	File access listener for remote file and record access
18	HLD	Host loader for RSX-11S downline task loading requests
19	CML	CMIP Management Listener object
20		RSTS/E media transfer program (NETCPY)
21--22		Reserved for Digital use
23	REMACP	Network terminal handler (host side)
24		Network terminal handler (terminal side)
25	MIRROR	Loopback mirror
26	EVL	Event receiver
27	MAIL	OpenVMS Mail utility
28		Reserved for Digital use
29	PHONE	OpenVMS Phone utility and RSX-11M/M-PLUS Phone utility
30--41		Reserved for Digital use
42	CTERM	Network terminal handler
43--62		Reserved for Digital use
63	DTR	DECnet Test Receiver object
64--127		Reserved for Digital use
128--255		Reserved for customer use

* Do you want to specify another application address?    [NO]:

If a node has more than one application address, enter YES and the previous prompts are repeated.

* What is the name of the Client for 'notes'?                :

Specify the name of the local user that you want activated upon receipt of the connect request containing the destination name matching one of the values in the destination names: attribute.

* What is the Image name for 'notes'? :Sys$system:notes$server.exe

Specify the file name of the program you want invoked upon receipt of a Connect Request containing a destination name matching one of the values in the destination names: attribute.

* Incoming Alias for 'notes' enabled?                 [TRUE] :

Specify how the specified application responds to incoming connect requests directed to the alias node address. If you specify FALSE, the application does not accept incoming connect requests that have been directed to the alias node address.

* Incoming Proxy for 'notes' enabled?                 [TRUE] :

Controls whether incoming proxy requests are honored. If you specify FALSE, requests to invoke proxies on incoming requests are ignored.

* Outgoing Alias for 'notes' enabled?                 [TRUE] :

Specify whether a particular object uses the alias node identifier in its outgoing connect requests. If you specify FALSE, the specified object cannot use the alias node address in its outgoing connect requests.

* Outgoing Proxy for 'notes' enabled?                 [TRUE] :

Specify the default action to execute when a user does not explicitly specify whether to invoke a proxy. If you specify FALSE, there will be no default action.

* Require node synonym for 'notes' enabled?           [TRUE] :

If you specify TRUE, then by default, the remote node name is passed to the application in synonym form. If a synonym is not available, the full name is used. If you specify FALSE, the full name is passed to the application by default.

* What is the Incoming OSI TSEL for 'notes'?                 :

Specify the transport service access point (TSAP) identifier for which the specified application accepts connections.

Note
This function is currently not implemented. Press Return to continue to the next prompt.

* What is the User Name for 'notes'?          [NOTES$SERVER] :

Enter the user name that you want to use when creating the account for the application you are configuring.

If you do not want to create an account for that application, you can either enter NONE and press Return, or press the space bar and press Return.

If you decide to create an account for that application, the following two questions appear:

* What UIC should 'notes' use?         [[200,200]] : [376,377]

Specify the UIC allocated upon creation of this application entity instance.

* Rights identifiers for 'NOTES$SERVER'?         :net$examine, 
 net$declareobject,net$decnetaccess

Specify the rights identifiers (if any) needed by the application. If there are two or more rights identifiers, separate them with commas.

The procedure then creates the account for the application you want configured and displays the following messages:

%NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account NOTES$SERVER 
* Do you want to generate NCL configuration scripts?   [YES] :

If you answer YES, the configuration program uses the information you entered to create an application NCL script and displays the following information:

%NET$CONFIGURE-I-CHECKSUM, checksumming NCL management scripts modified by 
NET$CONFIGURE 
%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed

Note
The net$configure procedure only provides checksums of those NCL management scripts it creates or modifies. It does not provide checksums of user-modified NCL scripts.

The configuration program then returns to the Configuration Options menu. To implement the application NCL script, reboot the system or disable the entity and execute the script.

If you answer NO, the configuration procedure returns to the Configuration Options menu and does not generate NCL scripts.

3.10 Reconfiguring the MOP Client Database

To reconfigure the MOP client database, proceed as follows from the Configuration Options menu:

* Which configuration option to perform?                 [1] : 8

Select Option 8 and press Return.

* Do you want to ADD or DELETE a MOP Client?           [ADD] :

Answer ADD to create an entity on the specified node, allocate resources for it, and open the service interface. Answer DELETE to delete the entity from the specified node and reclaim associated resources.

* Name of the MOP Client?                              : SUPERX

Specify the simple name of the client (for example, SUPERX).

If you elect to delete the MOP client, the procedure displays the following prompt:

* Are you sure you want to DELETE this client?               :

If you want to delete this client, answer YES.

* Circuit for 'superx'?                                      :

Specify the name of the MOP circuit you want to use for this client.

* Physical addresses for 'superx'?                           :

Specify the set of LAN addresses for the client on the circuit specified by the CIRCUIT characteristic.

* Secondary Loader for 'superx'?                             :

Specify the files you want loaded when the client requests a secondary loader during a downline load operation. File identifications are interpreted according to the file system of the local system.

* Tertiary Loader for 'superx'?                              :

Specify the files you want loaded when the client requests a tertiary loader during a downline load operation. File identifications are interpreted according to the file system of the local system.

* System Image for 'superx'?                                 :

Specify the files you want loaded when the client requests a system image during a downline load operation. File identifications are interpreted according to the file system of the local system.

* Diagnostic Image for 'superx'?                             :

Specify the files you want loaded when the client requests a diagnostic image during a downline load operation. File identifications are interpreted according to the file system of the local system.

* Management Image for 'superx'?                             :

Specify the files you want loaded when the client requests a management image during a downline load operation. File identifications are interpreted according to the file system of the local system.

* Script File for 'superx'?                                  :

Specify the files you want loaded when the client requests a CMIP initialization script during a downline load operation. File identifications are interpreted according to the file system of the local system.

* Dump File for 'superx'?                                    :

Specify the files to write to when the client is upline dumped.

* Dump Address for 'superx'?                             [0] :

Specify the address of the files to write to when the client is upline dumped.

* Verification for 'superx'?            [%X0000000000000000] :

Specify the verification string you want sent in a boot message to the specified client.

* Phase IV Client Address (aa.nnn) for 'superx'?             :

Specify the Phase IV node address you want given to the client system when it is loaded. This address is passed in a load characteristics message; whether it is needed depends on the software being loaded.

* Phase IV Client Name for 'superx'?                      [] :

Specify the Phase IV node name you want given to the client system when it is loaded. This name is passed in a load characteristics message; whether it is needed depends on the software being loaded.

* Phase IV Host Address for 'superx'?                        :

Specify the Phase IV node address you want passed as the host node address when a client is loaded. This address is passed in a load characteristics message; whether it is needed depends on the software being loaded.

* Phase IV Host Name for 'superx'?                        [] :

Specify the Phase IV node name you want passed as the host node name when a client is loaded. This name is passed in a load characteristics message; whether it is needed depends on the software being loaded.

* Do you want to generate NCL configuration scripts?   [YES] :

If you answer YES, the configuration program uses the information you have entered to create the MOP client NCL script. The configuration program then returns to the Configuration Options menu. To implement the MOP client NCL script, reboot the system or disable the entity and execute the script.

If you answer NO, the configuration procedure returns to the Configuration Options menu and does not generate NCL scripts.

3.11 Reconfiguring Event, MOP Client, Application Entities, and the Naming Search Path

You can use user-defined site-specific NCL scripts for the Event Dispatcher, MOP client, application, and search path entities. (See Section 2.2.4 for further information about creating the site-specific search path script.)

The network startup procedure calls four site-specific NCL scripts (if they exist) when the network is started. These scripts must be in SYS$MANAGER. They are called immediately after their Digital-supplied counterparts are executed. The following table lists the scripts and their counterparts.

User-Defined
Site-Specific Script Digital-Supplied
Script

NET$EVENT_LOCAL.NCL NET$EVENT_STARTUP.NCL

NET$APPLICATION_LOCAL.NCL NET$APPLICATION_STARTUP.NCL

NET$MOP_CLIENT_LOCAL.NCL NET$MOP_CLIENT_STARTUP.NCL

User-Defined Site-Specific Script	Digital-Supplied Script
NET$EVENT_LOCAL.NCL	NET$EVENT_STARTUP.NCL
NET$APPLICATION_LOCAL.NCL	NET$APPLICATION_STARTUP.NCL
NET$MOP_CLIENT_LOCAL.NCL	NET$MOP_CLIENT_STARTUP.NCL

These scripts are user-defined and user-maintained and thus will not be overwritten or deleted by net$configure. Digital recommends that whenever possible, you place your site-specific changes in these user-defined NCL scripts.

Note
If you invoke net$configure.com to edit a standard NCL script (NET$entity_STARTUP.NCL), the standard NCL script is superseded and renamed to NET$entity_STARTUP.NCL-OLD (where entity is a particular entity name).

If you must make changes to the standard NCL scripts and you want to retain your modifications after invoking net$configure, you can either manually edit the NCL script to replace the user modifications or rename the appropriate NET$entity_STARTUP.NCL-OLD script back to NET$entity_STARTUP.NCL. Be sure to incorporate any new changes as well. The net$configure.com procedure flags these modifications the next time it checksums the scripts.

3.12 Reconfiguring the Cluster Alias

All or some nodes that are OpenVMS Cluster members can be represented in the network as a single node by establishing an alias for the cluster. The alias allows users access to common resources on the OpenVMS Cluster without knowing which nodes are members of the cluster. It is not necessary for every member of the cluster to join the alias. Refer to the DECnet-Plus for OpenVMS Network Management guide for more information about setting up a OpenVMS Cluster alias.

To reconfigure the cluster alias, proceed as follows:

* Which configuration option to perform?                 [1] : 9

Select Option 9 and press Return.

* Do you want to ADD or DELETE an alias?               [ADD] :

Answer ADD to add the specified node to the cluster. Answer DELETE to remove the specified node from the cluster.

* Full name of Cluster Alias                                 :

Specify the full name that uniquely identifies the cluster alias node (for example, IAF:.SALES.BOSTON).

If you are removing a node from the cluster, the procedure displays the following prompt:

* Are you sure you want to DELETE this alias?            [NO]:

If you answer YES to this prompt, the node is removed from the cluster.

3.12.1 Specifying an Address

If you are adding a node to the cluster, the procedure displays the following prompt:

* Cluster Alias Phase IV Address (aa.nnnn OR AA-00-04-00-xx-xx) :

Specify either the DECnet Phase IV node address or Ethernet physical address of the alias. The Phase IV node address has the format area-number.node-number (for example, 63.171). The Ethernet physical address has the format AA-00-04-00-xx-xx, where xx-xx is calculated from the Phase IV node address. To determine the Ethernet physical address, proceed as follows:

Convert the Phase IV node address to its decimal equivalent as follows:

(area-number * 1024) + node-number = decimal equivalent 
(For example, (63 * 1024) + 171 = 64683 decimal)

Convert the decimal node address to its hexadecimal equivalent and reverse the order of the bytes to form the hexadecimal node address.
```
(For example, 64683 decimal = FCAB hexadecimal, 
   reversed = ABFC hexnodeaddress) 
```
Incorporate the hexadecimal node address in the following format:
```
AA-00-04-00-hexnodeaddress 
(For example, AA-00-04-00-AB-FC) 
```

3.12.2 Determining Selection Weight

The selection weight determines the number of sequential incoming connects passed to this alias member node in the round-robin sequence before proceeding to the next member node in the sequence. A value of zero means this node is not eligible to receive incoming connections to this alias address. Selection weight apportions incoming alias connections according to the capacity of each alias member.

For example, nodes with greater capacity should have larger values of selection weight, while OpenVMS Cluster satellites should generally have a value of zero. Specify a nonzero selection weight if this node is connected locally to a dual-ported disk, or if it will be serving any multihost disks, such as RFxx or HSC-connected disks, to other cluster members. Values between 0 and 10 are suggested.

* Selection weight for this cluster node [0 for satellites]  :

  PROFILE_006.HTML
  OSSG Documentation
   2-DEC-1996 12:33:31.06

Legal