DECnet-Plus now returns the node synonym koi to applications that require Phase IV-style node names.
The default node synonym directory is .DNA_NodeSynonym. If you plan to use a node synonym directory other than this default directory, you must define the logical name DECNET_MIGRATE_DIR_SYNONYM to the synonym directory name you want to use in sys$manager:net$logicals.com. (If you do not have a sys$manager:net$logicals.com procedure on your system, you can create one using sys$manager:net$logicals.template.) This makes the definition permanent (that is, it will not be deleted when you reboot the system).
Use the following format to define an alternate node synonym directory:
$ define decnet_migrate_dir_synonym "alt-directory-name"
If you use a synonym directory name that includes special characters or three or more dots, the system might produce an error. To avoid this, enclose the synonym directory name in quotes. For example:
$ define/system decnet_migrate_dir_synonym ".ch.noun.synonym"
The net$configure procedure needs this logical name to be defined at all times if you wish to use a synonym directory other than .DNA_NodeSynonym. Be sure to add this definition to net$logicals.com to ensure that the definition of the synonym directory will be permanent.
You can use the logical name described in Section 7.4.1 for either the BASIC or the ADVANCED configuration option.
You must define this logical name before you use any of following procedures:
If synonym lookup fails in the namespace, the software does one of the following:
The system displays a message that it has redefined the logical names.
If you are already using a namespace created with Version 1 of the VAX Distributed Name Service (DNS) (running on DECnet Phase IV), you can continue to use the namespace when you upgrade your networking software to DECnet-Plus for OpenVMS. However, because of differences in the way that DNS Version 1 and DECdns Version 2 handle access control, you must prepare your DNS Version 1 namespace for use by DECnet-Plus. DNS Version 1 and DECdns Version 2 interpret principal specifications in access control entries (ACEs) differently.
In DNS Version 1, servers recognize principals only in the form nodename::username. In DECdns Version 2, servers recognize principals primarily in the form nodename.username. For DECdns Version 2 clerks and servers to interpret and process existing DNS Version 1-style access control entries in the namespace, you need to create a backtranslation directory (.DNA_BackTranslation) and a node synonym directory (.DNA_NodeSynonym) in the root directory of the namespace. You must then populate these directories by registering all the nodes participating in the Version 1 namespace.
To prepare a namespace created with DNS Version 1 for use by DECnet-Plus, follow these steps:
DNS> add access pastry::system directory . /rights=(r,w,d,t,c)
DNS> add access pastry::system clearinghouse .paris_ch /rights=(r,w,d,t,c)
Note
If the node you configured as a Version 2 clerk in Step 1 is a new node, or is being assigned a new DECnet Phase IV-compatible address, you should update the DECnet node databases on all Version 1 servers in the namespace to include the new address before you proceed.
Refer to the DECnet-Plus for OpenVMS Network Management guide for complete information on how to use the decnet_register utility and the decnet_register_decdns.com utility to perform these steps.
When you have completed this step, the DNS Version 1 namespace is ready for use by other nodes running DECdns Version 2 on DECnet-Plus for OpenVMS software.
Perform this procedure only once to prepare a DNS Version 1 namespace for use with DECnet-Plus. After the node synonym and backtranslation directories are populated, you can configure new DECdns clerks, new DECdns servers (for VAX only) into an existing namespace, or convert existing DNS Version 1 servers to DECdns Version 2 format in the normal manner. Refer to the DECnet-Plus DECdns Management guide for information on how to convert a DNS Version 1 clearinghouse to DECdns Version 2 format.
The net$configure.com procedure creates an Export/Import file to register your node in the appropriate namespace. If your node is already registered, the decnet_register Export/Import file is not created.
The decnet_register Export/Import file is a text file that has the following format where <synonym> is the node synonym name you selected during configuration:
sys$manager:decnet_register_import_file_<synonym>.TXT
. . . Updating nodes listed in SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT 1) local:.elmer Error - Node registration was unsuccessful Please correct any problems and re-register the node LOCAL:.elmer The specified node name is already in use as a synonym Used by node: LOCAL:.WABBIT.ELMER Synonym: elmer You can choose to stop processing this command, continue executing this command until completion or until the next error, or ignore further errors and continue to completion. Number of nodes registered: 0 Number of nodes modified: 0 Number of update failures: 1 %NET$CONFIGURE-E-COULDNOTREG, could not automatically register node in the LOCAL directory service********************************************************************** WARNING This node could not be registered in one or more of the directory services you have chosen. When this procedure completes you or your network manager will have to manually register this node in the directory service(s) for which the error occurred. See the DECnet-Plus Installation and Configuration guide for more details, or contact your network manager. Once the problem has been rectified, you or your namespace manager can use the following decnet_register command(s) to register your node in the appropriate directory service(s): For the LOCAL directory service: DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE - SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_ELMER.TXT Once the node has been successfully registered in the appropriate directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change node name/namespace name) to complete the node's network configuration and startup. **********************************************************************
If net$configure.com cannot access the DECdns namespace you have selected, it is most likely because:
When this happens, you will see the following message (this example uses ACME: as the namespace that is not accessible):
************************************************************************* WARNING NET$CONFIGURE.COM cannot access the ACME: namespace, either because the namespace is not available at the moment, your node does not have proper access to the namespace, or because the namespace you are using is new and the directories have not been created yet. Therefore, the decnet_register tool cannot attempt to look up or register your node into the ACME: namespace. When the problem is rectified, please use the decnet_register import file to register your node into the ACME: namespace. *************************************************************************
If you receive this message because the namespace you are using is new and the namespace directories have not been created yet, use the decnet_register manage command to invoke decnet_register_decdns.com (located in SYS$MANAGER:) to create the proper directories. For more details, refer to the DECnet-Plus for OpenVMS Network Management guide.
If you see the preceding warning messages, net$configure will display another message indicating how you or your namespace manager can attempt node registration once the problem is resolved. For example:
********************************************************************** WARNING This node could not be registered in one or more of the directory services you have chosen. When this procedure completes you or your network manager will have to manually register this node in the directory service(s) for which the error occurred. See the DECnet-Plus Installation and Configuration guide for more details, or contact your network manager. Once the problem has been rectified, you or your namespace manager can use the following decnet_register command(s) to register your node in the appropriate directory service(s): For the DECdns directory service: DECNET_REGISTER IMPORT DIRECTORY DECDNS FILE - DECNET_REGISTER_IMPORT_FILE_ELMER.TXT For the LOCAL directory service: DECNET_REGISTER IMPORT DIRECTORY LOCAL FILE - DECNET_REGISTER_IMPORT_FILE_ELMER.TXT Once the node has been successfully registered in the appropriate directory service(s), invoke option 2 of NET$CONFIGURE.COM (Change node name/namespace name) to complete the node's network configuration and startup. **********************************************************************
You may see the previous messages if the following exists:
$ mcr dns$control DNS> add group <ns>:.worldread_group member local:.*... DNS> add clear <ns>:.<ch_name> access <ns>:.worldread_group as group for r,t
These commands will give your primary Local full name the proper access it needs to look up information regarding the secondary DECdns full name you have chosen.
Note
If you use DECDNS for the primary directory service and LOCAL for the secondary directory service, these steps are not necessary.
Part III contains the following appendixes:
The POLYCENTER Software Installation utility replaces VMSINSTAL as the method of installing layered products for OpenVMS such as the OSI applications for DECnet-Plus for OpenVMS, and X.25 for OpenVMS Alpha. It allows you to install several software products with a single command.
Note
Before installing DECnet-Plus using the POLYCENTER Software Installation utility for the first time on OpenVMS VAX Version 7.1, you should execute the following DCL command:$ product register product vms/version=v7.1/source=sys$updateThis needs to be done only once in the life of the OpenVMS system; it makes a permanent entry in the POLYCENTER Software Installation utility database, so it remains effective across system boots and for all future software upgrades.
If you do not perform this operation before installing DECnet-Plus, the installation recommends termination due to the failure to locate the product "DEC VAXVMS VMS Version 7.1." Answer YES to the question Do you want to terminate? and perform the product register command as in the above example.
Additional details for using the POLYCENTER Software Installation utility to install, manage, and remove software products on your system are provided in the OpenVMS System Management Utilities Reference Manual.
To obtain DCL Help for POLYCENTER, type the DCL command help product, followed by the name of a POLYCENTER Software Installation utility command (for example: help product install).
PRODUCT Command | Qualifiers |
---|---|
CONFIGURE
Creates a product configuration file (PCF) for one or more products in reference format. Optionally, uses the values in an existing PCF to create the new PCF. |
/CONFIGURATION
/HELP /LOG /OUTPUT |
COPY
Manipulates a product distribution. You can use copy to create a sequential copy from a reference copy, a reference copy from a sequential copy, or to create a copy without changing the format. |
/DESTINATION
/FORMAT /HELP /LOG /OUTPUT /OWNER_UIC /SOURCE |
EXTRACT RELEASE_NOTES
Accesses the release notes for the selected product or group of products. |
/DISPLAY
/LOG /OUTPUT /SOURCE |
FIND
Looks at the distribution media and reports on the products it finds there. |
/LOG
/OUTPUT /SOURCE |
INSTALL
Installs one or more software products on your system. |
/CONFIGURATION
/DESTINATION /HELP /LOG /OUTPUT /PURGE /REMARK /SOURCE /TEST /WORK |
RECONFIGURE
Changes the active configuration choices for a product. |
/CONFIGURATION
/HELP /LOG /OUTPUT /REMARK /SOURCE |
REGISTER PROCESSOR
Adds a processor in a computing facility. Used primarily within a DCL command procedure during system startup. |
/BASE_SYSTEM
/BOOTSTRAP /DESTINATION /GLOBAL /HELP /LOG /OPERATING /OUTPUT /REMARK |
REGISTER PRODUCT
Registers a product in the product database. |
/DESTINATION
/HELP /LOG /OUTPUT /REMARK /SOURCE |
REGISTER VOLUME
For a volume containing installed products, records a change in volume label in the product database. |
/HELP
/LOG /OUTPUT |
REMOVE
Removes a software product from your system and the product database. |
/HELP
/LOG /OUTPUT /REMARK /WORK |
SHOW FILE
Displays information about files created during a software product installation. |
/BRIEF
/DEVICE /DIRECTORY /FULL /PRODUCT |
SHOW HISTORY
Displays a log of actions, users, and remarks that apply to a particular product. |
/ACTION
/BEFORE /BRIEF /FULL /REMARK /SINCE /STATE /USER |
SHOW PRODUCT
Displays information about the products installed on your system. |
/ACTION
/BEFORE /BRIEF /DEVICE /DIRECTORY /FILE /FULL /LINK /PATCHED /SINCE /SOFTWARE /STATE /STATUS /USER |
UNREGISTER PROCESSOR
Removes a processor from a computing facility. Used primarily within a DCL command procedure during system startup. |
/HELP
/LOG /OUTPUT /PURGE /REMARK |
Some software products require you to make a set of choices when you install the product. For example, if you are installing a tool that checks spelling, you might choose which languages you want to include. When you use the POLYCENTER Software Installation utility, you can configure a product in one of three ways:
By saving your answers in a PCF and using the file for subsequent installations, you can reduce or eliminate the questions asked when you install a product. You can also create multiple PCFs for each product. This allows you to customize software installations for unique hardware situations or for different usage patterns within a group.
If you create a PCF as a separate operation, rather than as part of the installation procedure, you can determine how your choices are recorded in the PCF. You have the following options:
The following are valid responses to questions asked during an installation:
To get help on using the POLYCENTER Software Installation utility script, at the DCL prompt type the following command:
$ help product
The POLYCENTER Software Installation utility verifies that any or all of the following are true, depending on your product:
When the POLYCENTER Software Installation utility detects a problem in any of these areas, it asks if you want to continue the installation. If you want to continue, type YES. If you want to stop the installation, press Return.
The POLYCENTER Software Installation utility resolves some conflicts automatically. For other types of conflicts, the POLYCENTER Software Installation utility provides feedback on the nature of the conflict, letting you decide how you want to proceed.
PROFILE_004.HTML OSSG Documentation 2-DEC-1996 13:01:42.74
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.