9. NOT-CONFIG Commands

 

This chapter describes the NOT-CONFIG commands.

Command Summary

The following table lists the commands you can run from the NOT-CONFIG prompt.

NOT-CONFIG Command

Description

ADD NAME-MAPPING

Adds or modifies a name-mapping entry.

ADD OBJECT

Adds or modifies an object entry.

ADD PROXY

Adds or modifies a proxy entry.

ATTACH

Detaches the terminal from the calling process and reattaches it to another process.

DELETE NAME

Deletes a name-mapping entry.

DELETE OBJECT

Deletes an object entry or its options.

DELETE PROXY

Deletes a proxy entry.

EXIT

Saves the current configuration (if it has been modified), and quits the configuration utility.

GET

Reads in a DECnet application services configuration file. (GET is the same as USE.)

HELP

Displays help information.

NETCONTROL

Changes the functionality of the executing DECnet application services image.

PUSH

Starts a DCL subprocess.

QUIT

Quits the configuration utility. If the configuration file has been changed, QUIT asks if you want to save the file.

RELOAD

Reloads DECnet application services from the default configuration file.

SAVE

Writes out the current DECnet application services configuration file. (SAVE is the same as WRITE.)

SET

Sets NOT-CONFIG global parameters.

SHOW

Displays the current DECnet application services configuration.

SPAWN

Executes a single DCL command, or if entered without options, starts a subprocess with the same effect as PUSH.

STATUS

Displays the status of the DECnet application services configuration.

USE

Reads in a configuration file. (USE is the same as GET.)

VERSION

Displays the version and release information of the NOT-CONFIG configuration program.

WRITE

Writes out the current DECnet application services configuration to a file.  (WRITE is the same as SAVE.)

 

 

 

 

 

 

 

 

 

 


 

ADD NAME-MAPPING

Adds or modifies a name-mapping entry. Modify existing entries with the ADD NAME-MAPPING command by entering new information at each prompt. The name-mapping database maps local DECnet node names to TCP/IP node name equivalents.

 

FORMAT

ADD NAME-MAPPING [decnet-name] [tcp-name]

 

PARAMETERS

decnet-name

Specifies the DECnet node name. If you omit the node name, you are prompted to supply it. The name can be a maximum of six characters.

tcp-name

Specifies the TCP/IP node name. If you omit the node name, you are prompted to supply it. Enter an underscore (_) in front of the node name (_nodename) to indicate that DECnet should be used instead of DECnet application services.

 

EXAMPLE

This example specifies that DECnet be used with the TIRED host, and that DECnet application services be used with the ZIPPY host.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>ADD NAME-MAPPING
DECnet Nodename: TIRED
TCP Nodename: _
[Added mapping "TIRED" = "_"]
NOT-CONFIG>SHOW NAME-MAPPING
DECnet nodename   TCP nodename
---------------   ------------
TIRED             _
ZIPPY             ZIPPY.EXAMPLE.COM
NOT-CONFIG>

 

 

 

 


 

ADD OBJECT

Adds or modifies an object entry. Modify existing entries with the ADD OBJECT command by entering new information at each prompt. Display information created with ADD OBJECT with the SHOW OBJECT /FULL command. Delete an object with the DELETE OBJECT command. The object database identifies the objects (services) provided for incoming connections.

 

FORMAT

ADD OBJECT [entry] [NUMBER number] [FILE file]
           [FULLNAMES-SUPPORTED { TRUE | FALSE }]
           [USER user] [PASSWORD password]
           [PROXY { NONE | INCOMING }]

 PARAMETERS

entry

Specifies an object name. If you omit the object name, you are prompted to supply it. The object name can be up to 16 characters in length.

 

NUMBER number

Specifies an object number in the range 0 to 255. If you omit the object number, it defaults to 0. You can use any many objects with number 0 as you want; however, each number greater than 0 can only have one object associated with it. The OpenVMS operating system reserves numbers 1 to 127 for its own objects. User-defined objects are typically numbered 0.

 

FILE file

Specifies a file name. If you omit the file name, no file name is used. For number 0 objects, the default file name is SYS$LOGIN:object_name.COM. Copies of the command file must exist in SYS$LOGIN for each person who might use the object.

Objects can execute an image accessible by all logins by storing the image in SYS$SYSTEM.

 

FULLNAMES-SUPPORTED

If specified, the object supports the OpenVMS fullnames feature. This feature delivers the fully       qualified domain name of the client node to the server with the connection notification. The MAIL and FAL objects default this value to TRUE; all other objects default to FALSE. This allows MAIL to be answered even if you do not have appropriate name mappings configured. The fullnames feature is provided with OpenVMS VAX V6.1 and is a partial feature of OpenVMS Alpha 7 and later. On OpenVMS Alpha systems, enough fullnames support is provided for DECnet application services to accept fully qualified domain names; however, fullnames support is not supported by HP for OpenVMS Alpha systems.

 

USER username

Specifies a user name associated with the object. When a process is created to service the object request on your system, OpenVMS uses this user name.

 

PASSWORD password

Specifies a password associated with the object’s user name.

 

PROXY

Set PROXY NONE to disable PROXY handling for only the specified object. When proxy handling is disabled, any connection to the object logs into the user name and password specified on the object with the ADD OBJECT objectname, USERNAME username, PASSWORD password command; or, in the absence of an object user name and password, to the default user name and password for the system. The default is PROXY INCOMING.

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>ADD OBJECT MAIL NUMBER 0 FILE SYS$SYSTEM:MAIL.EXE
NOT-CONFIG>ADD OBJECT MY_OBJECT
[Added object "MY_OBJECT" number 0]
NOT-CONFIG>SHOW OBJECT/FULL
Object Name Number Username     Password    FullNames Proxy    Filename
----------- ------ --------     --------    --------- -----    --------
DTR          63                             NO        INCOMING DTR
FAL          17                             YES       INCOMING FAL.EXE
MAIL         27                             YES       INCOMING MAIL_SERVER.EXE
MY_OBJECT    0
NML          19                             NO        INCOMING NML.EXE
NOTES        33    NOTES$SERVER FNORDIES    NO        NONE     NOTES$SERVER.EXE
PHONE        29                             NO        INCOMING PHONE.EXE
VPM          51    MAIL$SERVER  FNORDIES    NO        NONE     VPM.EXE
NOT-CONFIG>

 

 

 

 


 

ADD PROXY

Adds or modifies a proxy entry. Modify existing entries with the ADD PROXY command by entering new information at each prompt.

 

FORMAT

ADD PROXY [rmt_node::rmt_username local_username]

 

PARAMETERS

rmt_node::rmt_username

Specifies a remote user name in the form nodename::username. The nodename can be any host name identifier; for example, a six-character DECnet name or a fully qualified domain name. If you omit the user name, you are prompted to supply it.

 

local_username

Specifies the local user name. If you omit the user name, you are prompted to supply it. You cannot use special characters such as ampersand (&) in a user name. You can enter an asterisk (*) to indicate that the local user name is the same as the remote user name. You can add as many as 16 local user names to a single remote user name. Use the /DEFAULT qualifier to specify which one to use normally.

 

QUALIFIERS

/DEFAULT

Specifies that this is the default proxy.

 

DESCRIPTION

The proxy database identifies which remote users can access a local account without specifying a password. When you search for a node name in the proxy table, the following order is used to determine which nodes are permitted:

1.      A fully qualified domain name has first priority (for example, WHATNO.FOO.EXAMPLE.COM::SYSTEM)

2.      *.domain2.domain1.domain0:: (for example, *.FOO.EXAMPLE.COM::SYSTEM)

3.      *.local.domain:: (for example, *.EXAMPLE.COM::SYSTEM)

4.      *.domain:: (for example, *.COM::SYSTEM)

5.      *:: (for example, *::SYSTEM)

6.      Steps 1-5 again, with a wildcard to designate the remote user name.

 

 

Note: The default proxy is different from the DECnet default proxy.  With DNAS, the first proxy that matches is always applied if a remote username is not specified.  Specifying a proxy as /default says to put this name first in the list.  With DECnet, the /default qualifier says to use that proxy if one is not specified, but if a proxy is not specified and there is no default, then no proxy is used.

 

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>ADD PROXY
Remote User: FLOWERS::FNORDIST
Local User: FNORDIST
[Added proxy "FLOWERS::FNORDIST" = "FNORDIST"]
NOT-CONFIG>SHOW PROXY
Remote User            Local Users
--------------------   ------------
*.EXAMPLE.COM::*           *
FLOWERS::FNORDIST      FNORDIST
NOT-CONFIG>

 

 

 

 


 

ATTACH

Detaches the terminal from the calling process and reattaches it to another process. Use the SPAWN SHOW PROCESS /SUBPROCESSES command to list the names of subprocesses. Use the DCL LOGOUT command to return to the original process. If the MULTINET_DISABLE_SPAWN logical is set, ATTACH does not work.

 

FORMAT

ATTACH process-name

 

PARAMETERS

process_name

Specifies the name of a process to which you want your terminal attached. Not all subprocesses can be attached; some testing may be required.

 

EXAMPLE

This example creates and exits attached subprocesses. The SPAWN command creates a subprocess. Then MM is invoked from that subprocess. Next, the SPAWN SHOW PROCESS /SUBPROCESSES command lists all the active subprocesses: _TWA42: is NOT-CONFIG, PROC_1 is MM, and PROC_2 is the SPAWN SHOW PROCESS /SUBPROCESSES command.

The ATTACH _TWA42: command returns control to NOT-CONFIG. The ATTACH PROC_1 command returns control to MM. When MM is exited, control returns to the first subprocess. Then LOGOUT returns control to NOT-CONFIG.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>SPAWN
$ MM
MM>SPAWN SHOW PROCESS /SUBPROCESSES
. . .
There are 3 processes in this job:
 _TWA42:
     PROC_1
        PROC_2 (*)
MM>ATTACH _TWA42:
NOT-CONFIG>ATTACH PROC_1
MM>EXIT
$ LOGOUT
NOT-CONFIG>

 

 

 

 


 

DELETE NAME

Deletes a name-mapping entry.

 

FORMAT

DELETE NAME entry

 

PARAMETERS

entry

Specifies the name-mapping entry to delete.

 

EXAMPLE

In this example, a name-mapping entry is created then deleted.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>ADD NAME JOY FNORD.EXAMPLE.COM
[Added mapping "JOY" = "FNORD.EXAMPLE.COM"]
NOT-CONFIG>DELETE NAME JOY
NOT-CONFIG>

 

 

 

 


 

DELETE OBJECT

Deletes an object entry or its options. Use ADD OBJECT to change the object number. Use SHOW OBJECT/FULL to confirm deletions.

 

FORMAT

DELETE OBJECT [entry] [FILE] [USER] [PASSWORD]

 

PARAMETERS

entry

Specifies the object name to delete the object and all its options.

 

FILE

Specifies the FILE keyword to delete the file.

 

USER

Specifies the USER keyword to delete the user name.

 

PASSWORD

Specifies the PASSWORD keyword to delete the user password.

 

EXAMPLE

In this example, an object is added then displayed. The associated file name and object are removed. The object can be removed directly if desired. These steps only illustrate the possibilities, not an actual procedure sequence.

 

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>ADD OBJECT FISH NUMBER 0 FILE SYS$LOGIN:OH.COM
NOT-CONFIG>SHOW OBJECT FISH
Object Name    Number    Filename
-----------    ------    --------
FISH            0        SYS$LOGIN:OH.COM
NOT-CONFIG>DELETE OBJECT FISH FILE
[Changed object "FISH" number 0]
NOT-CONFIG>SHOW OBJECT FISH

Object Name    Number    Filename
-----------    ------    --------
FISH            0
NOT-CONFIG>DELETE OBJECT FISH
NOT-CONFIG>

 

 

 

 


 

DELETE PROXY

Deletes a proxy entry.

 

FORMAT

DELETE PROXY entry

 

PARAMETERS

entry

Specifies the entry to delete from the proxy database.

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>ADD PROXY FLOWERS::NOTHER JOY
[Added proxy "FLOWERS::NOTHER" = "JOY"]
NOT-CONFIG>ADD PROXY FLOWERS::NOTHER ME
[Added proxy "FLOWERS::NOTHER" = "ME"]
NOT-CONFIG>SHOW PROXY FLOWERS
Remote User            Local Users
--------------------   ------------
FLOWERS::NOTHER        JOY ME
NOT-CONFIG>DELETE PROXY FLOWERS ME
NOT-CONFIG>SHOW PROXY FLOWERS
Remote User            Local Users
--------------------   ------------
FLOWERS::NOTHER        JOY

 

 

 

 



EXIT

Saves the current configuration (if it has been modified), and quits the configuration utility.

 

FORMAT

EXIT

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>EXIT
[Configuration not modified, so no update needed]
$

When the configuration has not been changed, a message appears to indicate the configuration file is not updated.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>ADD PROXY MYNODE::NEWUSER NEWUSER
NOT-CONFIG>EXIT
[Writing configuration to MULTINET:NOT.CONFIGURATION]
$

When the configuration changes, a message appears to indicate that the configuration file has been updated.

 

 

 

 


 

GET

Reads in a DECnet application services configuration file. (GET is the same as USE.) After using the GET command, you can use other NOT-CONFIG commands to display and modify the new configuration.

 

FORMAT

GET config_file

 

PARAMETERS

config_file

Specifies the name of the configuration file to read in.

 

EXAMPLE

This example reads in the MULTINET:NEW_CONFIG.CFG file.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>GET MULTINET:NEW_CONFIG.CFG
[Reading in configuration from MULTINET:NEW_CONFIG.CFG;1]
NOT-CONFIG>EXIT

 

 

 

 


 

HELP

Displays help information.

 

FORMAT

HELP [topics]

 

PARAMETERS

topics

Specifies a space-delimited list of topics that begins with a topic, followed by subtopics. The default topic is HELP.

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>HELP
HELP
               Invokes command help.
               Format
               HELP   [topics]
Additional information available:
ADD      ATTACH       Command_Summary     DELETE     EXIT     GET
HELP     NETCONTROL   PUSH       QUIT     RELOAD     SAVE     SET
SHOW     SPAWN        STATUS     USE      VERSION    WRITE
Topic?  RETURN
NOT-CONFIG>

 

 

 

 


 

NETCONTROL

Changes the functionality of the executing DECnet application services image.

 

FORMAT

NETCONTROL [hostname]

 

PARAMETERS

hostname

Specifies the name of a host. If you do not specify the host name, it defaults to the local host.

 

DESCRIPTION

After invoking NETCONTROL, you can issue commands to the NETCONTROL server to affect MULTINET_SERVER operations on that host.

 

RESTRICTIONS

The NETCONTROL server is normally protected from unauthorized access by a restriction list.

 

EXAMPLE

This example reloads the NOT server.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>NETCONTROL
Connected to NETCONTROL server on "127.0.0.1"
 EXAMPLE.COM Network Control Mon 13-Mar-2019 7:42am-EST
NOT>?

NETCONTROL command, one of the following:
ATTACH   PUSH     QUIT     QUOTE    SELECT   SPAWN    VERBOSE
DEBUG    NOOP     RELOAD   VERSION
NOT>SELECT NOT
NOT>RELOAD
 NOT database reload done
NOT>QUIT
NOT-CONFIG>

 

 

 

 


 

PUSH

Starts a DCL subprocess. Attaches to a parent DCL command interpreter if it exists. To return from DCL, use the ATTACH command. If the MULTINET_DISABLE_SPAWN logical is set, PUSH does not work.

 

FORMAT

PUSH

 

EXAMPLE

In this example, PUSH is used to go to the DCL command line to disable broadcasts. The LOGOUT command returns control to NOT-CONFIG.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>PUSH
$ SET TERM /NOBROADCAST
$ LOGOUT
NOT-CONFIG>

 

 

 

 


 

QUIT

Quits the configuration utility. If the configuration file has been changed, QUIT asks if you want to save the file.

 

FORMAT

QUIT

 

EXAMPLE

This example shows how to quit the NOT-CONFIG utility without saving any changes.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>QUIT
Configuration modified, do you want to save it ? [NO] NO
$

 

 

 

 


 

RELOAD

Reloads DECnet application services from the default configuration file.

 

FORMAT

RELOAD

 

EXAMPLE

This example shows how to reload the default configuration file.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>RELOAD
Connected to NETCONTROL server on "127.0.0.1"
 FNORD.EXAMPLE.COM Network Control Mon 13-Mar-2019 7:42am-EST
 NOT database reload done
NOT-CONFIG>

 

 

 

 


 

SAVE

Writes out the current DECnet application services configuration file. (SAVE is the same as WRITE.)

 

FORMAT

SAVE [config_file]

 

PARAMETERS

config_file

Specifies the name of DECnet application services configuration file to write out. The default is the      file from which the configuration was read.

 

EXAMPLE

This example shows how to save your changes to the configuration file.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>SAVE
[Writing NOT configuration to MULTINET_COMMON_ROOT:[MULTINET]NOT.CONFIGURATION;nn]
NOT-CONFIG>

 

 

 

 


 

SET

Sets NOT-CONFIG global parameters.

 

FORMAT

             { DECNET-LOADED [TRUE|FALSE] }
             { DOMAIN-DEFAULT domain }
             { HOST-NAME hostname }
SET          { PASSWORD-DEFAULT password }
             { PREFER-DECNET-TO-TCP [TRUE|FALSE] }
             { USERNAME-DEFAULT username }

 

PARAMETERS

DECNET-LOADED

If set to TRUE (the default), specifies that DECnet application services are being run with DECnet. If set to FALSE, only DECnet application services are used.

 

DOMAIN-DEFAULT

Specifies an alternate domain name. If you specify a DECnet node name with a dot, the domain host name is used, as is, as a TCP/IP node name. The default domain name is only appended if the TCP node name does not contain a dot. The maximum length for a domain name is 256 characters.

 

HOST-NAME

Specifies a name to override the SYS$NODE definition to set a six-character host name. This parameter is useful if there is a name conflict with the six-character DECnet node name.

 

PASSWORD-DEFAULT

Specifies a default password to use with the object database.

 

PREFER-DECNET-TO-TCP

If set to TRUE, specifies that DECnet is preferred to TCP/IP for making the connection.

 

USERNAME-DEFAULT

Specifies a default user name to use with the object database.

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>SET DOMAIN-DEFAULT EXAMPLE.COM

 

 

 

 


 

SHOW

Displays the current DECnet application services configuration.

 

FORMAT

            {NAME-MAPPING [entry]}
            {OBJECTS [/FULL] [entry]}
SHOW        {PROXY [entry]}
            {GLOBAL-PARAMETERS}
            {[entry]}

 

PARAMETERS

NAME-MAPPING [entry]

Displays the complete NAME-MAPPING database or a single entry if you specify entry.

 

OBJECTS [/FULL] [entry]

Displays the complete OBJECT database or a single entry if you specify entry. If you specify /FULL, user name and password information is also displayed.

 

PROXY [entry]

Displays the complete PROXY database or a single entry if you specify entry.

 

GLOBAL-PARAMETERS

Displays the current settings of the global parameters.

 

[entry]

Displays information only about the specified entry.

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>SHOW OBJECT /FULL

Object Name Number Username     Password    FullNames Proxy    Filename
----------- ------ --------     --------    --------- -----    --------
DTR          63                             NO        INCOMING DTR
FAL          17                             YES       INCOMING FAL.EXE
MAIL         27                             YES       INCOMING MAIL_SER
VER.EXE
NML          19                             NO        INCOMING NML.EXE
NOTES        33    NOTES$SERVER FNORDIES    NO        NONE     NOTES$SER
VER.EXE
PHONE        29                             NO        INCOMING PHONE.EXE
VPM          51    MAIL$SERVER  FNORDIES    NO        NONE     VPM.EXE
. . .
NOT-CONFIG>SHOW NAME
DECnet nodename   TCP nodename
---------------   ------------
holmes            _
yobro             _
. . .
NOT-CONFIG>SHOW PROXY
Remote User            Local Users
--------------------   ------------
*.EXAMPLE.COM::*         *
FLOWERS::FNORDIST        FNORDIST

 

 

 

 


 

SPAWN

Executes a single DCL command, or if entered without options, starts a subprocess with the same effect as PUSH. To return from DCL, use the LOGOUT command. If the MULTINET_DISABLE_SPAWN logical is set, SPAWN does not work.

 

FORMAT

SPAWN [command]

 

PARAMETERS

command

Specifies a command to execute. If you omit the command, a DCL subprocess is created.

 

QUALIFIERS

/INPUT=file-spec

Specifies an input file to the command you enter with SPAWN.

 

/[NO]LOGICAL_NAMES

Specifies whether logical names and logical name tables are copied to the subprocess.

 

/[NO]SYMBOLS

Specifies whether global and local names are passed to the subprocess.

 

/[NO]WAIT

Specifies whether control returns without waiting for the command to complete. Do not use this qualifier with commands that have prompts or screen displays.

 

/OUTPUT=file-spec

Specifies a file that retains the output of the command invoked with SPAWN. This qualifier only works when a single command is entered without creating a DCL subprocess. In addition, this qualifier is positional; you must specify it immediately after SPAWN or its other qualifiers.

 

EXAMPLE

This example displays terminal information, captures the output in a file, then displays the information with the TYPE command.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>SPAWN/OUTPUT=FOO. SHOW TERM
NOT-CONFIG>SPAWN TYPE FOO.

This example invokes a command procedure.

NOT-CONFIG>SPAWN @COMPROC

This example displays help information about NOT-CONFIG. Use the LOGOUT command to return control to NOT-CONFIG.

NOT-CONFIG>SPAWN
$ HELP MULTINET CONFIGURE /NOT
. . .
$ LOGOUT
NOT-CONFIG>

 

 

 

 


 

STATUS

Displays the status of the DECnet application services configuration.

 

FORMAT

STATUS

 

EXAMPLE

The n/pppp numbers shown in this example indicate how many entries are currently configured (n) and the number of potential numbers that can be configured (pppp).

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>STATUS
This is the MultiNet NOT configuration program Version 5.6(nn)
There are 7/5000 entries in the name mapping list.
There are 1/5000 entries in the proxy list.
There are 7/5000 entries in the object list.
The configuration MULTINET:NOT.CONFIGURATION has not been modified.
NOT-CONFIG>

 

 

 

 


 

USE

Reads in a configuration file. (USE is the same as GET.)

 

FORMAT

USE config_file

 

PARAMETERS

config_file

Specifies the name of the configuration file to read in.

 

DESCRIPTION

After using the USE command, you can use other NOT-CONFIG commands to display and modify the new configuration.

 

EXAMPLE

This example reads in the MULTINET:NEW_CONFIG.CFG file.

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>USE MULTINET:NEW_CONFIG.CFG
[Reading in configuration from MULTINET:NEW_CONFIG.CFG;1]
NOT-CONFIG>EXIT

 

 

 

 


 

VERSION

Displays the version and release information of the NOT-CONFIG configuration program.

 

FORMAT

VERSION

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>VERSION
This is the MultiNet NOT configuration program Version 5.6(nn)
NOT-CONFIG>

 

 

 

 


 

WRITE

Writes out the current DECnet application services configuration to a file. (WRITE is the same as SAVE.)

 

FORMAT

WRITE [config_file]

 

PARAMETERS

config_file

Specifies the name of DECnet application services configuration file to write out. The default is the      file from which the configuration was read.

 

EXAMPLE

$ MULTINET CONFIGURE /NOT
MultiNet NOT Configuration Utility 5.6(nn)
[Reading in NOT configuration from MULTINET:NOT.CONFIGURATION]
NOT-CONFIG>WRITE
[Writing NOT configuration to MULTINET_COMMON_ROOT:[MULTINET]NOT.CONFIGURATION;nn]
NOT-CONFIG>