|
|
|
|
The NDMA symbolic path file is used to keep a list of all the symbolic path names used by NDMA.
You can use this file to define logical paths to the directories that you wish to use that cannot be accessed using the standard file naming conventions used by NetView DM. For example, if you are using the directory /usr/ndma/inbound, then you can send or retrieve files from this directory by assigning the symbolic path name rcvdir to it, and then using the path rcvdir in host commands.
This section explains how to set up the data file that controls this mapping between the file names used by NetView DM and the corresponding path names for files on the SNAP-IX computer.
Note that if there are multiple copies of NDMA active on a single SNAP-IX computer then they will share a single symbolic path file.
Most commands issued from the NetView DM program include the name of a file on the Solaris computer (for example, a command can include the name of a file to be sent from the host to the Solaris computer, or the name of a file on the Solaris computer to be deleted). The NetView DM program uses file names consisting of between one and three strings that are each of eight characters, and separated by dot characters. (The NetView DM program also accepts four-part file names, but these are intended for use with other programs and should not be used when communicating with NDMA.)
NDMA then translates these names into Solaris path names using the information in the symbolic path file, which is described in Symbolic Path File Format. The mapping depends on the number of 8-character strings in the supplied name, as follows:
A 1-part name is taken to be a file name with no extension; NDMA assumes that the file is in the default directory for NDMA files.
A 2-part name is taken to be either a directory and file name or a file name with a file name extension. NDMA checks the first part of the name against the list of path aliases in the symbolic path file:
If the name matches one of these aliases, NDMA assumes that the second part of the name is a file name (with no extension), and that the file is in the directory specified for this alias.
Otherwise, NDMA assumes that the two parts of the host file name specify the Solaris file name and file name extension, and that the file is in the default directory for NDMA files.
A 3-part name is taken to be a directory, file name, and file name extension. NDMA checks the first part of the name against the list of path aliases in the symbolic path file:
If the name matches one of these aliases, NDMA assumes that the file is in the directory specified for this alias.
Otherwise, NDMA assumes that the file is in a subdirectory with this name in the default directory for NDMA files.
The symbolic path file used by SNAP-IX is /opt/sna/ndm/ndmpath.dat. The version of this file delivered with the SNAP-IX NDMA software is a sample; you will need to modify it to specify appropriate path names for your host system and your Solaris computer.
This file is an ASCII text file which can be maintained using a text editor. The file contains up to 20 lines of text; the maximum length of each line in the file is 65 characters followed by a line feed.
Each line in the file is in the following format (position 1 indicates the first character in the line):
Path alias used in host commands. If this alias is shorter than eight characters, the remaining character positions must be filled with spaces.
For the first line in the file, which indicates the default path, the alias must consist of eight space characters.
Space character
Full path name on the Solaris computer corresponding to the alias. If the path name is shorter than 56 characters, it can be followed immediately by the terminating line feed character; you do not need to include trailing space characters.
The first line in the file has an alias consisting of eight space characters, and specifies the default path; if a host command includes a file name with no path, NDMA assumes that the required file is in this directory.
The remaining lines define path aliases; if a host command includes one of these aliases as the path name for a file, NDMA matches the alias against this line of the file to determine the correct directory.
The following is an example of the symbolic path file format:
/usr/local/bin
rcvdir /usr/ndma/inbound
senddir /usr/ndma/outbound
The following examples show how NetView DM file names in different formats are mapped to Solaris file names using the symbolic path file above.
| NetView DM file name | Solaris file name |
| thisfile | /usr/local/bin/thisfile |
This example shows a 1-part host file name (which means that no path is included).
NDMA assumes that the required file is in the default directory, specified using the first record in the symbolic path file (in this example, /usr/local/bin).
| NetView DM file name | Solaris file name |
| senddir.newfile | /usr/ndma/outbound/newfile |
This example shows a 2-part host file name. NDMA matches the first part of the name against a record in the symbolic path file, so the required file is in this directory (in this example, /usr/ndma/outbound). The second part of the host file name is taken to be the Solaris file name (with no extension).
| NetView DM file name | Solaris file name |
| newfile.ext | /usr/local/bin/newfile.ext |
This example shows a 2-part host file name. NDMA cannot match the first part of the name against a record in the symbolic path file, so the file is in the default directory (in this example, /usr/local/bin). The two parts of the host file name are taken to be the Solaris file name and file name extension.
| NetView DM file name | Solaris file name |
| senddir.newfile.ext | /usr/ndma/outbound/newfile.ext |
This example shows a 3-part host file name. The first part of the file name is taken to be a directory (in this example, /usr/ndma/outbound ). NDMA matches this name against a record in the symbolic path file, so the required file is assumed to be in this directory. The second and third parts of the host file name are taken to be the Solaris file name and file name extension.
| NetView DM file name | Solaris file name |
| backup.newfile.ext | /usr/local/bin/backup/newfile.ext |
This example shows a 3-part host file name. The first part of the file name is taken to be a directory. Because this name does not match any path alias in the symbolic path file, it is taken to be a subdirectory of the default directory (which is, in this example, /usr/local/bin). The second and third parts of the host file name are taken to be the Solaris file name and file name extension.
|
|
|
 |
|