NDS leaf objects

Server-related leaf objects

This topic lists the available leaf objects that are related to NetWare servers and volumes, explains what each is used for, and indicates when to use each:

Leaf object Function Usage situation
Directory Map Represents a particular directory in the file system. Directory Map objects can be especially useful in login scripts by pointing to directories that contain applications or other frequently used files. You want to avoid making changes to many login scripts when the location of applications changes. Instead, you change only the Directory Map object.
For example, you have a directory that contains DOS 5.0. You could map a search drive to that directory in any login scripts you create.
But if you later upgrade to DOS 6.0 and rename the directory, you would have to change the mapping in every login script where that search mapping appears.
By using a Directory Map object instead, you would need to change the information in only that one object.
NCP Server Represents a server running NetWare on your network.
In the NetWare Server object's properties, you can store information about the server; such as its physical location and what services it provides.
In addition, the NetWare Server object affects the network in that it is referred to by several other objects.
Automatically created during server installation. It must exist for a server's file systems and volumes to be accessible.
If you have a bindery-based server, create this object to be able to access that server's volumes. When you create this object for a bindery-based server, that server must be running.
Volume Represents a physical volume on the network.
In the Volume object's properties, you can store identification information; such as the Host server, volume location, and so on. You can also set restrictions for use of the volume, such as space limits for users.
Optional for every physical volume on the network.
Automatically created for every physical volume during server installation.
Can be used to display information about the directories and files on that volume.

 -------------------------------------------------------------------------
| Leaf object  |  Function                  |  Usage situation           |
|--------------|----------------------------|----------------------------|
| Directory Map|  Represents a particular   |  You want to avoid making  |
|              |  directory in the file     |  changes to many login     |
|              |  system. Directory Map     |  scripts when the location |
|              |  objects can be especially |  of applications changes.  |
|              |  useful in login scripts by|  Instead, you change only  |
|              |  pointing to directories   |  the Directory Map object. |
|              |  that contain applications |  For example, you have a   |
|              |  or other frequently used  |  directory that contains   |
|              |  files.                    |  DOS 5.0. You could map a  |
|              |                            |  search drive to that      |
|              |                            |  directory in any login    |
|              |                            |  scripts you create.       |
|              |                            |  But if you later upgrade  |
|              |                            |  to DOS 6.0 and rename the |
|              |                            |  directory, you would have |
|              |                            |  to change the mapping in  |
|              |                            |  every login script where  |
|              |                            |  that search mapping       |
|              |                            |  appears.                  |
|              |                            |  By using a Directory Map  |
|              |                            |  object instead, you would |
|              |                            |  need to change the        |
|              |                            |  information in only that  |
|              |                            |  one object.               |
|--------------|----------------------------|----------------------------|
| NCP Server   |  Represents a server       |  Automatically created     |
|              |  running NetWare on your   |  during server             |
|              |  network.                  |  installation. It must     |
|              |  In the NetWare Server     |  exist for a server's file |
|              |  object's properties, you  |  systems and volumes to be |
|              |  can store information     |  accessible.               |
|              |  about the server; such as |  If you have a bindery-    |
|              |  its physical location and |  based server, create this |
|              |  what services it provides.|  object to be able to      |
|              |  In addition, the NetWare  |  access that server's      |
|              |  Server object affects the |  volumes. When you create  |
|              |  network in that it is     |  this object for a         |
|              |  referred to by several    |  bindery-based server, that|
|              |  other objects.            |  server must be running.   |
|--------------|----------------------------|----------------------------|
| Volume       |  Represents a physical     |  Optional for every        |
|              |  volume on the network.    |  physical volume on the    |
|              |  In the Volume object's    |  network.                  |
|              |  properties, you can store |  Automatically created for |
|              |  identification            |  every physical volume     |
|              |  information; such as the  |  during server             |
|              |  Host server, volume       |  installation.             |
|              |  location, and so on. You  |  Can be used to display    |
|              |  can also set restrictions |  information about the     |
|              |  for use of the volume,    |  directories and files on  |
|              |  such as space limits for  |  that volume.              |
|              |  users.                    |                            |
|--------------|----------------------------|----------------------------|

© 1999 The Santa Cruz Operation, Inc. All rights reserved.
UnixWare 7 Release 7.1.1 - 5 November 1999