HP OpenVMS Systems Documentation

Content starts here

DECnet-Plus for OpenVMS
Network Management

Previous Contents Index Converting NCP Commands in an NCP Command File to NCL

The following example shows how to convert NCP commands contained within an NCP command procedure to their closest NCL command equivalent within the procedure.

decnet_migrate> convert ncp_file input_file [to output_file]

For more information about the convert ncp_file command, see Appendix D. Editing a Command File That Contains NCL Commands

The following example shows how to invoke the Language-Sensitive Editor (LSE) with the edit command. You automatically set up LSE by specifying .com or .ncl file extensions for the NCL command file that you are editing.


The LSE layered product must be installed and licensed on your system. For more information about LSE, see the Guide to Language-Sensitive Editor.

The initial placeholder used to start expanding a command is {NCL_SCRIPT}.

decnet_migrate> edit file-name

For more information about the edit command, see Appendix D.

2.2 Using the Graphical User Interface for DECnet Phase V Network Management

You can access NCL either through a command line interface or through the graphical user interface (GUI). The GUI allows network managers to view the status of network components and control those components from a Motif-based window interface located at SYS$SYSTEM:NET$MGMT.EXE.

The NET$MGMT GUI utility is a Motif application that you can use as a learning tool to ease the transition to NCL. This utility can help you become familiar with the DECnet Phase V hierarchy of manageable components (modules, entities, and subentities) and with NCL syntax.

The NET$MGMT GUI utility can also perform some task-oriented functions that involve many NCL commands or functions that are complex in some way. It provides a way to perform the equivalent of ncp show known links and ncp show known node counterson a Phase V system.

Refer to Appendix I for more information about the NET$MGMT GUI.

2.3 Using the NCP Emulator to Convert NCP Commands to NCL

Many DIGITAL software products must register themselves with the network during their installation. Some of these products issue NCP commands during the installation. The NCP Emulator converts the NCP commands to NCL commands.

The NCP Emulator is designed to facilitate software installations on DECnet Phase V systems; it is not intended as a replacement for NCL. The NCP Emulator supports conversion for the NCP commands listed in Table 2-2.

To have session control applications registered when you install them, you must have the following identifiers:


The following example shows how to set up these identifiers. This example assumes you are installing the applications from the SYSTEM account.

%UAF-I-GRANTMSG, identifier NET$EXAMINE granted to SYSTEM
%UAF-I-GRANTMSG, identifier NET$MANAGE granted to SYSTEM
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-NAFNOMODS, no modifications made to network proxy data base
%UAF-I-RDBDONEMSG, rights data base modified

In addition, ensure that the following NCP Emulator private command files are added to, and run from, the site-specific system startup file:


Note that the NCP Emulator attempts to communicate with the NET$MOP component of your DECnet Phase V system. Therefore, before invoking the NCP Emulator, ensure that the NET$MOPprocess is running (see Section 10.3 for information about starting MOP).

Table 2-2 NCP Commands Converted by the NCP Emulator
Verb Entities

All other NCP commands are unsupported and will cause an %NCP-W-SYSMGT error message. Some of these unsupported NCP commands have corresponding NCL commands that perform identical operations. Table 2-3 lists the equivalent NCL command for each of these unsupported NCP commands.

Table 2-3 Equivalents for Unsupported NCP Commands
NCP Command NCL Equivalent
CONNECT set host/mop
LOAD load mop circuit
load mop client
LOOP CIRCUIT loop mop circuit
loop mop client
TRIGGER boot mop circuit
boot mop client

2.3.1 Information About Supported NCP Commands

This section includes special notes about the NCP commands that the NCP Emulator tool supports.


In DECnet Phase IV NCP, the SHOW command displays the volatile database information (information on the running system), while the LIST command displays the permanent database information. Using the DECnet Phase V NCP Emulator, both of these commands are converted to display volatile database information. NCL has no command that displays permanent database information. In addition, the output for these commands differs slightly between DECnet Phase IV NCP and the DECnet Phase V NCP Emulator.

SET Command

The NCP SET command usually spawns an equivalent NCL command. If the NCP SET command specifies the name of a component that does not exist, usually the spawned NCL command creates an entity with that name, just as the NCP command does.

You can use node numbers as the target of the SET command, such as in the following example:


If you use a node number as the target, and if a mop client does not already exist with a matching PHASE IV CLIENT ADDRESS (or ADDRESSES) attribute, the NCP Emulator checks DECdns for a synonym. If a synonym is found, the NCP Emulator uses the synonym as the name of the mop clientwhen it is created.

You can specify NAME as part of the SET command as in the following example:


The name is used as the mop clientname.

The SET KNOWN NODE/CIRCUIT/OBJECT ALL command executes both the standard NCL startup script and the private command procedure maintained by the NCP Emulator. If you use only SET ALL on a specific named entity, the NCP Emulator executes the private command file.

DEFINE Command

The DEFINE command writes NCL commands to the private script files. When using the command to define nodes, if you specify the node address, the NCP Emulator searches the script file for a client with the corresponding address. If the NCP Emulator does not find a corresponding address, and if you did not specify the NAME parameter in the same command, the emulator checks DECdns for a node synonym. If you specify the NAMEparameter later, the mop client is renamed.

The NCP Emulator does not support the NCP DEFINE KNOWN command.

CLEAR Command

The CLEARcommand clears a parameter or a set of parameters in the corresponding NCL entity instance. The CLEAR ALL command deletes the instance.

PURGE Command

The PURGE command removes the SETcommand for a parameter from the private script file. The PURGE ALLcommand removes the entire object.

The NCP Emulator does not support the NCP PURGE KNOWN command.

Because the PURGEcommand operates only on the NCP Emulator private command file, use NET$CONFIGUREto purge objects from the standard system applicationsor mop clients scripts (SYS$MANAGER:NET$APPLICATION_STARTUP.NCL and SYS$MANAGER:NET$MOP_CLIENT_STARTUP.NCL).

TELL Command

The TELL command functions as it does in DECnet Phase IV, allowing you to remotely manage Phase IV nodes. For more information on how to remotely manage Phase IV nodes by using the NCP Emulator, see Section 2.3.4.


The SET EXECUTOR NODE command works as expected for managing Phase IV nodes.

2.3.2 Information About Supported NCP Components

The NCP Emulator supports all NCP components except the following:

  • AREA
  • X.25/X.29 modules

If you attempt an operation with one of these unsupported components, you will receive the %NCP-W-UNRCMPerror message or, with the AREA or LINKS components, a message stating that no information exists for these components in the database.

The remainder of this section includes special notes about the supported NCP components.

EXECUTOR Component

The NCP Emulator supports only the SHOW and LIST commands with the EXECUTOR component. It does not change or clear any EXECUTOR parameters.

The only relevant EXECUTORparameters are NAMEand ADDRESS. The Identification displayed with the SHOW EXECUTORcommand indicates that the node is DECnet-Plus, but the executor type is displayed as "nonrouting IV."

NODE Component

The DECnet Phase IV NODE component usually corresponds to the NCL mop client entity, since a product installation usually requires that type of information. You can reference a node by name, which results in a look-up in the mop clientdatabase. If the NCP Emulator does not find a name, it checks DECdns for a node synonym with that name and the corresponding DECnet Phase IV address.

If you refer to a node by node number, the NCP Emulator first searches the mop clientdatabase for a client with a PHASE IV CLIENT ADDRESSattribute matching the specified node address. If it finds a client with a matching address, the corresponding client name becomes the node name. If the emulator does not find a matching address, it then searches for a client that has, as one of its ADDRESSESattributes, an address that begins with AA-00-04-00and translates to the specified address. If it still cannot find a matching address, the emulator uses DECdns. Because referencing nodes by address is not efficient, DIGITAL recommends that you avoid doing so.

With the NCP Emulator, KNOWN NODES refers to all NCL mop client entities. The NCP Emulator maps MOP-related parameters only. For example, it maps the following DECnet Phase IV SET NODE command parameters to the corresponding NCL mop client attributes:


DECnet Phase IV node parameters such as ACCESS and COUNTER TIMER have nothing to do with NCL MOP, so they are ignored during the translation from NCP to NCL.

The NCP Emulator does not attempt to set, clear, purge, or define any other parameter. Permanent database operations (DEFINE, PURGE, SET ALL) manipulate the file SYS$MANAGER:NET$NCP_MOP_CLIENTS.COM.

OBJECT Component

The NCP OBJECT component maps to the NCL session control applications entity. The permanent database for objects is SYS$MANAGER:NET$NCP_APPLICATIONS.COM.

CIRCUIT Component

The NCP CIRCUIT component refers to the NCL csma-cd station and mop circuit entities. The SHOW KNOWN CIRCUITS command will list all of the csma-cd station entities currently configured.

Only two circuit characteristics are used by the NCP Emulator: STATE and SERVICE. The STATE characteristic determines whether MOP will service requests from that circuit. It is determined by the csma-cd station stateattribute. The NCP Emulator can change the STATEparameter from Off to On but not from On to Off.

The SERVICEparameter indicates whether a mop circuit exists and whether the service is enabled. The parameter also is used to enable or disable the service, such as with the NCP SET CIRCUIT SERVICE ENABLED command.

The NCP Emulator uses the mop circuit entity that is linked to the datalink circuit.

Circuit names are always of the form "ddd-u", where "ddd" indicates the device type (such as SVA and BNA) and "u" indicates the controller (0 or 1, for example).

The naming scheme is the same scheme used with NCP. The NCP Emulator attempts to translate a circuit name to the correct csma-cd stationand mop circuit, regardless of their actual names used with NCL. For example, the circuit name SVA-0 translates to the station whose COMMUNICATIONS PORT attribute is "ESA" and to the mop circuitwhose LINK NAME attribute refers to the station with "ESA". The name BNA-1 translates to the station with "ETB."

Enabling the SERVICEparameter on a circuit first creates (if necessary) the appropriate csma-cd station and/or mop circuit, and then enables the LOAD SERVER, DUMP SERVER, and CONSOLE REQUESTERfunctions on the mop circuit. Disabling SERVICE disables the same functions on the mop circuit.

The circuits command procedure is SYS$MANAGER:NET$NCP_MOP_CIRCUITS.COM.

2.3.3 Running the NCP Emulator on Your System

Use the following command to run the NCP Emulator. The NCP Emulator will prompt you for an NCP command, as shown in the following example:

$ run sys$system:ncp

2.3.4 Remotely Managing DECnet Phase IV Nodes

You can use the NCP Emulator tool to manage remote Phase IV nodes with the TELL and SET EXECUTOR NODEcommands. For example, to zero EXECUTOR counters on a remote Phase IV node from a local Phase V node, enter the following commands:

$ run sys$system:ncp
NCP> tell remnod"account password" zero exec counters

The NCP Emulator tool is not intended for management of Phase V nodes. The following error is returned when an NCP Emulator command is attempted on a Phase V system without specifying a remote Phase IV system:

NCP> zero exec counters
%NCP-W-SYSMGT, System-specific management function not supported

Previous Next Contents Index