![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
To manage entities, you issue directives (commands) using NCL. The commands enable you to manage local or remote network components by identifying entities throughout the network by their unique entity names. For instance, you can create, examine, and modify entities.
For definitive information about modules, entities, and supported attributes, characteristics, status, counters, and commands, refer to the DECnet-Plus Network Control Language Reference.
Note
DECnet Phase IV and Phase V differ in how network components are managed. Chapter 2 provides information on converting Network Control Program (NCP) commands to Network Control Language (NCL) commands. Appendix A provides a table of Phase IV components and parameters and their equivalent DECnet Phase V entities and attributes.
DECnet Phase V networks can be organized as local area networks (LANs) or wide area networks (WANs) or a combination of the two. A LAN provides for communications within a limited geographical area, such as a building or a cluster of buildings. A WAN permits long-distance communication over media such as dedicated, leased and dialup lines, and microwave and satellite links. A WAN can include one or more LANs.
DECnet-Plus allows you to manage the following local and wide area links:
For more detailed descriptions of DECnet-Plus network configurations, refer to the Introduction and Planning guides.
In a Phase IV network, you use the Network Control Program (NCP) to configure, control, monitor, and test the network. In a DECnet Phase V network, you use the Network Control Language (NCL) to perform the same tasks. For an introduction to NCL, refer to the DECnet-Plus Network Control Language Reference. This chapter describes ways to convert NCP commands to NCL commands for use on DECnet Phase V nodes.
Command procedures that issue NCP commands to manage the local node do not work in the DECnet Phase V environment. Similarly, command procedures that issue NCP commands to a remote node do not work if the remote node has been upgraded to DECnet Phase V software. Do the following to revise any command procedures that issue NCP commands:
$ run sys$system:ncp NCP>
Digital supplies a tool, decnet_migrate, that converts NCP commands to NCL commands when possible. The tool converts individual NCP commands to NCL commands, and NCP commands within command procedures to NCL commands.
Three decnet_migrate convert commands convert NCP commands to NCL equivalents, where equivalents exist. The command conversion might not be complete because of the differences between NCP and NCL. You might have to edit the NCL command before you can use it. For example, this applies to Phase IV components that have new entity names for DECnet Phase V. In the output that convert generates, the parts of the commands that cannot be converted are set off in braces, for example, {{{string}}}.
Table 2-1 lists the NCP commands that the decnet_migrate convert commands can convert to NCL. Many NCP commands have NCL equivalents or near equivalents. See Appendix A for a list of NCP commands with their nearest NCL equivalents. For an alphabetical command reference for decnet_migrate, see Appendix D.
You may also use the Language-Sensitive Editor (LSE) to assist you when writing procedures that contain NCL commands (see Section 2.1.1.4).
| Verb | Entity | Attribute or Argument |
|---|---|---|
| tell | node_name | command_to_convert |
| set or clear | executor | address |
| area maximum cost | ||
| area maximum hops | ||
| broadcast routing timer | ||
| buffer size | ||
| delay factor | ||
| delay weight | ||
| inactivity timer | ||
| incoming proxy | ||
| incoming timer | ||
| maximum address | ||
| maximum area | ||
| maximum buffers | ||
| maximum cost | ||
| maximum hops | ||
| maximum links | ||
| maximum pathsplits | ||
| maximum visits | ||
| node | ||
| outgoing proxy | ||
| outgoing timer | ||
| retransmit factor | ||
| segment buffer size | ||
| state | ||
| type | ||
| all | ||
| show | executor | summary |
| status | ||
| characteristics | ||
| counters | ||
| loop | executor | count |
| length | ||
| with | ||
| show | node node-name | summary |
| known nodes | status | |
| active nodes | characteristics | |
| adjacent nodes | counters | |
| trigger | node or via | physical address |
| service password | ||
| via | ||
| Verb | Entity | Attribute or Argument |
| load | node or via | from |
| management file | ||
| physical address | ||
| secondary loader | ||
| service password | ||
| tertiary loader | ||
| via | ||
| loop | node | count |
| length | ||
| with | ||
| set or clear | circuit | active base |
| known circuits | active increment | |
| cost | ||
| dead threshold | ||
| dying base | ||
| dying increment | ||
| dying threshold | ||
| hello timer | ||
| inactive base | ||
| inactive increment | ||
| inactive threshold | ||
| polling state | ||
| router priority | ||
| state | ||
| all | ||
| show | circuit | summary |
| known circuits | status | |
| active circuits | characteristics | |
| counters | ||
| loop | circuit | count |
| length | ||
| physical address | ||
| with | ||
| set or clear | line | clock |
| known lines | dead timer | |
| delay timer | ||
| line speed | ||
| receive buffers | ||
| retransmit timer | ||
| scheduling timer | ||
| state | ||
| stream timer | ||
| all | ||
| Verb | Entity | Attribute or Argument |
| show | line | summary |
| known lines | status | |
| characteristics | ||
| counters | ||
| show | link | summary |
| known links | status | |
| characteristics | ||
| counters | ||
| set or clear | object | accept |
| known objects | account | |
| alias incoming | ||
| alias outgoing | ||
| default user | ||
| file | ||
| number | ||
| password | ||
| proxy | ||
| type | ||
| user | ||
| all | ||
| show | object | summary |
| known objects | status | |
| characteristics | ||
| counters | ||
| show | logging | summary |
| known logging | status | |
| characteristics | ||
| counters |
Invoke decnet_migrate by entering the following command:
$ run sys$update:decnet_migrate
The following example shows how to convert a single NCP command to its closest equivalent.
decnet_migrate> convert command "ncp-command"
To convert to NCL, replace ncp-command with the NCP command exactly as if it were entered at the NCP> prompt and enclose the command in quotation marks. After you execute the command, the output of the convert command appears on your terminal.
For more information about the convert command, see Appendix D.
The following example shows how to convert NCP commands contained within a DCL command procedure to their closest NCL command equivalent within the procedure.
decnet_migrate> convert dcl_file input_file [to output_file]
For more information about the convert dcl_file command, see Appendix D.
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.
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.
Note
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.
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.
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.
$ SET DEF SYS$SYSTEM $ RUN AUTHORIZE UAF> GRANT/ID NET$EXAMINE SYSTEM %UAF-I-GRANTMSG, identifier NET$EXAMINE granted to SYSTEM UAF> GRANT/ID NET$MANAGE SYSTEM %UAF-I-GRANTMSG, identifier NET$MANAGE granted to SYSTEM UAF> EXIT %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).
| Verb | Entities |
|---|---|
| CLEAR |
CIRCUIT
KNOWN CIRCUITS OBJECT KNOWN OBJECTS |
| DEFINE |
CIRCUIT
NODE OBJECT |
| PURGE |
CIRCUIT
KNOWN CIRCUITS OBJECT KNOWN OBJECTS |
| SET |
CIRCUIT
EXECUTOR NODE NODE KNOWN NODES OBJECT |
| SHOW/LIST |
CIRCUIT
KNOWN CIRCUITS EXECUTOR NODE KNOWN NODES OBJECT KNOWN OBJECTS |
| TELL |
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.
| 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 |
This section includes special notes about the NCP commands that the NCP Emulator tool supports.
SHOW/LIST Command
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:
SET NODE 12.88 LOAD FILE LOAD.SYS
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:
SET NODE 12.88 NAME ROYK
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.
PROFILE_VMS_001.HTML OSSG Documentation 2-DEC-1996 12:34:46.80
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.