Supervising the Network

5-36
Customizing the User Environment
Login Script Commands and Variables
INCLUDE nesting is limited only by available memory. This means that one
subscript file can include another subscript file, which can include yet
another subscript file, and so on.
If the subscript is a text file, users must have at least File Scan and Read
rights to the directory containing the subscript.
If you are using another object’s login script as a subscript, users must have
the Browse right to the object whose script you are including and the Read
right to the object’s Login Script property.
Examples
To execute a text file called SCRIPT.NEW (located in the VOL1: volume) as a
subscript, add the following line to your main login script:
INCLUDE VOL1:ADMIN\USERS\SCRIPT.NEW
Suppose you are creating a container login script for all users under the
Organizational Unit object SALES_LA. You recently created a container login
script for users under the Organizational Unit object SALES_PV.
Now you’ve decided that the login scripts for the two different groups of users
are very similar. In fact, you decide that the SALES_LA users could use the
same login script as the SALES_PV users, but with a few more drive mappings.
In the SALES_LA login script, you could add the additional drive mappings,
and then use the INCLUDE command to execute the entire SALES_PV login
script as a part of the SALES_LA login script, as follows:
Create an alias for the SALES_PV Organizational Unit in the SALES_LA
Organizational Unit.
Add this line to the SALES_LA Organizational Unit’s login script.
INCLUDE .SALES_PV_ALIAS.SALES.ACME_US
Figure 5-2 illustrates how the INCLUDE command executes the SALES_PV
login script as part of the SALES_LA login script.