Supervising the Network

5-9
Customizing the User Environment
Creating, Modifying, Copying, and Printing Login Scripts
Table 5-2 Login Script Conventions
Subject Convention
Minimum login script No minimum. All four types of login scripts are optional. Login scripts
can have only one line or they can have many. There are no required
commands for login scripts.
Case Either uppercase or lowercase is accepted, except that identifier
variables enclosed in quotation marks and preceded by a percent sign
(%) must be uppercase. See “Identifier Variables” in this chapter.
Characters per line 150 characters per line is maximum; 78 characters per line (common
screen width) is recommended for readability.
Punctuation and symbols Type all symbols (#, %, “, _ ) and punctuation exactly as shown in
examples and syntax.
Commands per line Use only one command per line. Start each command on a new line;
press <Enter> to end each command and start a new command.
Lines that wrap automatically are considered one command.
The WRITE command output displays better if WRITE is repeated at
the beginning of each wrapped line.
Sequence of commands Generally, enter commands in the order you want them to execute, with
the following restrictions:
• ATTACH commands must precede related MAP commands to avoid
prompting the user for a username/password during login.
• If you use “#” to execute an external program, this command must
follow any necessary MAP commands.
• If sequence is not important, you should group similar commands,
such as MAP and WRITE commands, together to make the login
script easier to read.
Blank lines Blank lines don’t affect login script execution. Use them to visually
separate groups of commands.
Remarks (REMARK,
REM, asterisks, and
semicolons)
Lines beginning with REMARK, REM, an asterisk, or a semicolon are
comments that do not display when the login script executes. Use
remarks to record the purpose of each command or group of commands.
(For examples, see “REMARK” in this chapter).