HPlogo Using the Node Management Services (NMS) Utilities > Chapter 4 Using NMMGR Utility Screens

Configuration Subtree Copy Screen

MPE documents

Complete PDF
Table of Contents
Index

The Configuration Subtree Copy screen in Figure 4-8 "Validate Configuration File Screen" allows you to copy specified parts of a configuration subtree into either the same configuration file or a different configuration file. This feature can save you a lot of time when you are configuring multiple nodes or subsystems in the same way. Note that the source or target file can be on a remote node in the network. (You can also use the COPYCONF maintenance mode command to perform this function. See Chapter 5 "Using NMMGR in Maintenance Mode" for more information on the maintenance mode commands.)

This screen can be reached by pressing the [Go To COPY SUB] key at the Utility screen.

Figure 4-8 Validate Configuration File Screen

[Validate Configuration File Screen]

Description

Use the Configuration Subtree Copy screen to copy a contiguous set of screens called a subtree from one configuration file to another or within the same configuration file. To copy a subtree, enter the name of the source file and path and the destination file and path in the fields provided and press the [Subtree Copy] key.

The source file is the name of the file that the data will be copied from. If you are copying a subtree from the current configuration file to another location within the same file, you can leave both the Source file and the Destination file fields blank.

The source path specifies the path name of the topmost screen in the subtree that you want to copy. All screens below the top screen will be copied.

The destination file is the name of the file that data will be copied to. This can be the same file that you are copying from, which provides a convenient way to configure two links that are very similar. After configuring the first link, you can simply copy all the screens in the link's configuration and modify the new link configuration as needed.

The destination path specifies the point in the destination file below which the copied screens will be added.

Fields

Source file

This field contains the name of the file that configuration data will be copied from. If left blank, the current configuration file is assumed.

If the file is on a remote node, you must use a file equation and prefix the file name with an asterisk (*). You may use an MPE command from the command window to set a file equation without having to leave NMMGR.

Source path

(Required field.) The source path contains the path name associated with the topmost screen in the subtree being copied. The field is composed of eight NMMGR path identifier slots. Enter one path identifier in each slot, leaving blanks at the end of each identifier. Leave any unused identifier slots empty. For example, the source path "NETXPORT.NI.LAN1.INTERNET" would be entered as: 


  NETXPORT.NI      .LAN1    .INTERNET.        .        .        .
Destination file

This field contains the name of the file the configuration data will be copied to. If this field is left blank, the current configuration file is assumed.

If the file is on a remote node, you must use a file equation and prefix the file name with an asterisk (*).

Destination path

Like the source path, the destination path is composed of eight path identifiers. You need to enter only those identifiers that are different from the source path. To copy data from the source file to the identical location in the destination file, leave this field blank. If, for example, you wish to change the fifth path identifier, then the fifth slot in the destination path should contain data. Only those parts of the path name that were designated by the user can differ among corresponding identifiers in the source and destination paths. User-selected types must match. For example, if the source file includes a direct connect link, the corresponding identifier in the destination path must also be a direct connect link.

Overwrite existing subtree

(Required field.) This field indicates whether or not existing data in the destination configuration file is to be overwritten when the copy is performed. A Y will purge all the existing data in the destination subtree and insert the data from the source subtree; an N will not allow the copy to continue if data exists where the destination subtree starts. The default is N.

In this example, a subtree copy is being performed from node A to node B. Since the copy is being made to a remote node, the user must make a DSLINE connection to node B and set up a file equation to represent node B's configuration file. This is done by entering the commands shown below:

Example

:REMOTE HELLO MGR.PUB.SYS;DSLINE=B

:FILE CONFIG=NMCONFIG.PUB.SYS;B,OLD

The source file and path on node A are entered into the source file and Source path fields. They appear here: 
  Source file:  [NMCONFIG.PUB.SYS]
  Source path:  NETXPORT.NI      .LAN1    .INTERNET.       .       .        .
The diagram in Figure 4-9 "Specified Subtree" shows the subtree specified by this path.

Figure 4-9 Specified Subtree

[Specified Subtree]

For this copy, the destination file and path were specified as: 
  Destination file:  [*CONFIG              ]
  Destination path:         .       .LAN2   .    <~>  .       .       .       .
The diagram in Figure 4-10 "Results of Copy" illustrates the results of the copy.

Figure 4-10 Results of Copy

[Results of Copy]

NOTE: When subtrees contain several records, copies that occur over DSLINE connections will take considerably longer than copies between two local configuration files. It is several times faster to DSCOPY the configuration file to the destination node, then perform the subtree copy between two local configuration files.



Validate Configuration File Screen

Chapter 5 Using NMMGR in Maintenance Mode