Customizing the user environment

MAP

Use MAP to map drives and search drives to network directories.

MAP has the following command format:

MAP [option] [drive:=path]

Replace drive with any valid network drive letter, local drive letter, or search drive number.

Replace path with a drive letter, a full directory path, or a Directory Map object.

More than one command can be on the map line if the commands are separated by a semicolon (;), as shown in the following example:

   MAP *1:=SYS:PUBLIC;*2:=SYS:PUBLIC\DOS

When mapping a drive to a directory on an NDS server, begin the path with either the Volume object name or server/volume.

When mapping to a directory on a bindery-based server or to an NDS server that is not your current server, begin the path with the server's name.

Replace option with one of the following:

DISPLAY ON/OFF

Determines whether drive mappings are displayed on the screen when the user logs in. The default setting is ON. This option is valid only in login scripts.

ERRORS ON/OFF

Determines whether MAP error messages are displayed when the user logs in. MAP ERROR OFF must be placed before MAP commands in the login script. The default setting is ON. This option is valid only in login scripts.

INS

Inserts a drive mapping between existing search mappings. This option is valid in login scripts and at the DOS command line.

DEL

Deletes a drive mapping, making that drive letter available for other mapping assignments. This option is valid in login scripts and at the command line.

ROOT

Maps a fake root. OS/2 is always mapped to the root. Some applications require their executable files to be located in a root directory.

Since you may not want users to have rights at the root directory, you can map a fake root to a subdirectory instead. This option is valid in login scripts and at the command line.

C (CHANGE)

Changes a search drive mapping to a regular mapping and a regular mapping to a search drive mapping. This option is valid in login scripts and at the command line.

NP (No prompt)

When a MAP command conflicts with an existing drive mapping, MAP NP eliminates the prompt that asks the user if the new drive mapping should overwrite the old mapping.

This option is valid only at the command line.

P (Physical)

Maps a drive to the physical volume of a server rather than to the Volume object's name.

It is possible to have a Volume object name that conflicts with a physical volume name. (For example, object ACCT is an Accounting volume, but there is also an ACCT which is a physical volume.)

Therefore, if you prefer to map a drive to the physical volume name, use MAP P. This option is valid in login scripts and at the command line.

N (Next)

When used without specifying a drive number or letter, maps the next available drive. This option is valid in login scripts and at the command line.

Follow these guidelines when using MAP:

If you use MAP to automate drive map assignments during execution of the login script, users do not have to map drives manually every time they log in.
Specify drive mappings in a login script by entering the same commands that you would enter if you were using MAP at the command line.
To avoid having the result of each mapping displayed as it is executed, you can put the MAP DISPLAY OFF command at the beginning of your login script. When all drive map assignments have been completed, add the line MAP DISPLAY ON and MAP to your login script. This sequence provides a cleaner display for the users as they log in.
Instead of specifying drive letters such as F: or G:, you could use an asterisk followed by a number n to represent the nth network drive. For example, if your first network drive is F: then using MAP *3:= would assign H:, or if your first network drive is D: then using MAP *4:= would assign G:.
This allows drive letters to reorder themselves automatically when local drives are removed or added or when the first network drive is changed.
This also allows users to log in from workstations that have a different number of local drives than their regular workstation.
You can map a local drive (usually A: through C:) to a network directory, but you cannot access the local drive until you remove the network drive mapping.
You must not map a redirected drive, such as a CD-ROM drive, to a network drive.
In many cases, you might find it useful to map network drives in the following order:
Map the first network drive to the user's home directory.
If your users are running OS/2, map network drive P: to the SYS:PUBLIC directory.
This drive mapping is used by OS/2 workstations, as explained in NetWare Client for OS/2 User Guide.
If users are running Windows from the network, map a drive to each user's directory that contains user-specific files.
Map remaining drives to any directories in which users frequently work, such as project directories.

Mapping search drives

NOTE: OS/2 workstations do not use search drives. Instead, OS/2 users use the OS/2 commands PATH, DPATH, and LIBPATH in their CONFIG.SYS files.

For DOS and Windows workstations, you can map search drives to directories that contain applications, executable files, and so forth. Then users can execute those applications regardless of the directory in which they are currently working.

A maximum of 16 NetWare search drives is allowed.

NOTE: Any object names in the login script should either be in the user's context or should have an alias point to the real object in another context. Any object referenced by a name outside the user's context will not work when that object is moved or renamed or the context is renamed.

When you map a search drive, use a search drive number (an S followed by a number). This search drive number assigns the next available drive letter to the mapping, starting with Z and working backwards through the English alphabet.

The letter assigned to the search drive is put into the DOS path statement. If you already have search drives in the path statement, the command MAP S1:= will overwrite the first one in the path. To prevent search drive assignments from overriding existing DOS PATH letters, use the INSERT option when assigning search drives. For example, type

MAP INS S16:=path

To ensure that users can access NetWare utilities, DOS directories, and applications, we recommend you map search drives to these directories in the following order:

Map the first search drive (S1:) to the SYS:PUBLIC directory, which contains the NetWare utilities for DOS and Windows workstations.
Map the second search drive (S2:) to the DOS directory if users access DOS from the network.
Map the third and subsequent search drives (S3:, S4:, and so on) to directories containing applications and the electronic NetWare documentation.
If your users are running Windows from the network, map a search drive to the Windows directory for the Windows group.

To avoid inadvertently changing the order of any search drives that must be mapped to a specific drive letter, you can map all remaining search drives with the number S16:, which assigns the next lowest search number each time it is used.

This command assigns the next available drive letter to the search drive without displacing the previous search drives.

If you have an application that requires a particular drive letter, you can use the following command to map the search drive, replacing drive with the drive letter:

MAP S16:=drive:=path

If you map a search drive using a number already assigned to a search drive, NetWare makes the old search drive a network drive. The letter assigned to the old search drive remains assigned as the converted drive mapping. The new search drive takes the next unused letter of the alphabet.

Mapping drives to directory map objects

Another way to map a drive to a directory is to create a Directory Map object that points to the directory. Then, if you move the directory, you only need to change the Directory Map object rather than all of the login scripts that may include that mapping.

NOTE: It is best to use Directory Map objects in the user's current context. Do not use complete names that point to other contexts. If the map is in another context, you should create an alias that points to the real Directory Map object.

For example, to map a search drive to a Directory Map object whose complete name is APPL.SALES_LA.ACME_US, add the following line to the login script:

   MAP S2:=.APPL.SALES_LA.ACME_US

In the previous example, the Directory Map object's name begins with a period, which indicates that the drive is mapped to the drive Root.

If the user whose login script this line appears in is also located in the SALES_LA.ACME_US context, the MAP command does not have to specify the Directory Map object's complete name. Instead, the line would be

   MAP S2:=APPL

For more information about using Directory Map objects, see ``Loading operating systems and applications onto the network''.

For example:

To map the first search drive to the SYS:PUBLIC directory (which contains the NetWare utilities for DOS and Windows workstations) add the following line to the login script:
```
   MAP S1:=SYS:PUBLIC
```
The second search drive should be mapped to the DOS directory if users run DOS from the network.
If your network has more than one DOS directory, use variables to indicate the directory path. These variables are replaced by the correct information from the workstation software when each user logs in.
To use variables for the DOS directory path, enter the following command in the login script:
```
   MAP S2:=SYS:PUBLIC\%MACHINE\%OS\%OS_VERSION
```
If all users have the same types of computers and are using the same version of DOS, you probably have only one DOS directory. In this case, add a line similar to the following, substituting the correct directory names:
```
   MAP S2:=SYS:PUBLIC\IBM_PC\MSDOS\50
```
You can also create a Directory Map object that points to the DOS directory, then map the search drive to the Directory Map object.
For more information about creating DOS directories, see ``Loading operating systems and applications onto the network''.
To map the next available search drive to the SYS:APPL\WORDPROC directory, add the following line to the login script:
```
   MAP S16:=SYS:APPL\WORDPROC
```
If you have mapped a Directory Map object to this directory, you can substitute the Directory Map object's name for the directory path.
For example, suppose you created a Directory Map object called WPROC, which is located in the context SALES.ACME_US, and mapped that object to the SYS:APPL\WORDPROC directory.
Following the rule of no complete names in a login script, you would create an alias in your own context to the object in SALES.ACME_US. Then use the following line in your login script:
```
   MAP S16:=WPROC
```
Suppose an application in the FORM directory requires that it reside in the Root directory of drive P:, but you do not want to put the application in the Root directory for security reasons.
You can map a fake root to the directory and map a search drive to it at the same time by adding the following line to the login script:
```
   MAP ROOT S16:=P:=SYS:APPL\FORM
```
To map Richard's first four regular drive mappings to his home directory, the SYS:PUBLIC\OS2 directory (which contains the NetWare utilities for OS/2), the REPORTS directory, and the PROJECTS directory, add the following four lines to Richard's user login script:
```
   MAP *1:=VOL1:HOME\RICHARD
   MAP *2:=SYS:PUBLIC\OS2
   MAP *3:=VOL1:ACCOUNTS\REPORTS
   MAP *4:=VOL1:UPDATES\PROJECTS
```
To map Richard's fifth drive to the PUBLIC directory on a NetWare 3.11 server named FS1, you need to include the server name in the MAP command. Use the following line in your login script:
```
   MAP *5:=FS1\SYS:PUBLIC
```
If you are mapping a drive to a directory that is located on a volume within your current context, include the volume's common name in the MAP command, as demonstrated in the previous examples.
If you are mapping a drive to a volume that is not in your current context, first create an alias to that volume; then include the volume's common name in the MAP command.
For example, if the complete name of a volume not in your current context is VOL1.SALES.ACME_US, then create an alias named VOL1: to that volume. The MAP command would include only this common name.
To map a drive to the APPL directory in this volume, the line in the login script would be
```
   MAP *6:=VOL1:APPL
```

For more information about enabling users to run DOS from the network, refer to ``Loading DOS onto the network''. For details of how to set paths for OS/2 workstations, see the NetWare Client for OS/2 User Guide. Using Directory Map objects is explained in ``Loading operating systems and applications onto the network''.