A User file is a file on the system directory that, in addition to identifying the user, specifies the environment the system activates after you sign on and after you exit from an
application.
An environment is a program that has control of the system at any given time. Environments include the SignOn form, the Executive, the Mail Manager, utilities such as the Editor, application programs such as word processing, programming language environments, etc.
A User file can also include entries that specify files pertaining to specific applications (for example, the word processing program's Print Wheels file).
User File Names
A User file name consists of two parts:
o the user name assigned to the user (refer to User Names, in this section)
o the suffix .user
For example, a user assigned the user name Worker1 would have a User file named Worker1.user.
Adapting the System to Your Requirements Figure 2-1 User File (Sample) :SignonExltFl1e:[sys]<sys>Exec.run :SignOnChainfile:[sys]<sys>Exec.run :SignOnTextFl1e:[sys]<sys>System.Txt :SignOnVolume:sys
:SlgnOnOlrectory:sys :SignOnFilePrefix:
:SignOnPasSIlJOrd:
:ExecCmdfile:[sys]<sys>Sys.cmds :WpFormatSet:[sys]<SYS>Wp.fmt :.pPrinters:[sys]<sys>Sys.Printers :WpprlntWheelS:[sYS]<sYS>Wp.Whl
User File Entries
2-3
A User file entry consists of a keyword enclosed in colons, followed by a parameter. For example, the first entry of the typical User file in figure 2-1 consists of the keyword :SignOnExitFile: followed by the parameter
[Sys]<Sys>Exec.run.
Note: The system requires the colons to read the file correctly.
The system ignores an entry if it does not begin with a keyword enclosed in colons.
Each entry specifies one feature of the user configuration. For example, the third and fourth entries in figure 2-1 specify [Sys] as the SignOn volume and <Sys> as the SignOn directory, respectively.
User files include SignOn entries, which specify items such as the path the system sets when you sign on, and can also include entries specifying parameters for applications such as word processing.
User File SignOn Entries
The User file SignOn entries (refer to table 2-1) specify the following items:
o the initial path
o a system password (optional)
o a message the system displays immediately when you sign on (optional)
o the Executive command file
a the initial environment (the environment that the system activates when you sign on)
a the exit environment (the environment that the system activates when you exit a program or enter the
ACTION-FINISH
key sequence) Table 2-1User File SignOn Entries
Keyword Parameter
:SignOnVolume:
:SignOnDirectory:
:SignOnFilePrefix:
:SignOnPassword:
:SignOnExitFile:
:SignOn T extFile:
:SignOnChainFile:
specifies the volume in the default path specifies the directory in the default path specifies a file prefix in the default path specifies a password required to sign on to the system
specifies the run file of the environment the system loads whenever you exit an application or enter ACTION-FINISH
For example, to return to the Executive when you finish a session with an application, enter the Executive run file [Sys] <Sys> Exec.run.
specifies one or more files containing text that the system displays when you sign on You can specify the default text file [Sys]<Sys>System.txt and/or other files containing messages you want the system to display before activating the initial environment.
The system also displays any text you enter between the end of the last (or only) text file and the first colon of the next entry in the User file.
specifies the run file of the initial environment.
For example, to activate the Executive when you sign on, you enter the Executive run file, [Sys]<Sys>Exec.run.
To bypass the Executive and activate an application, programming language, or BTOS utility, enter the appropriate run file (for applications and programming languages, refer to the applicable documentation; for BTOS utilities, refer to appendix A).
Adapting the System to Your Requirements
2-5
Table 2-1 User File SignOn Entries (continued)Keyword Parameter
:ExecCmdFile:
If the Executive command that activates the application, programming language, or BTOS utility has a command form, you can specify one or more parameters; use the following guidelines:
o the parameter(s) must appear in the line(s) immediately following the Sign On Chain File entry.
o the line(s) containing the parameter(s) do not begin with a colon.
o the first parameter must be the command that activates the application, programming language, or BTOS utility.
o the parameter entries can not include wild card characters.
o if you are using the word processing program to edit the file, use the SHIFT·RETURN key combination to end each line.
o two or more blank lines must follow the last parameter entry.
o the next line following the blank lines must begin with a colon (even if it contains no other entry).
specifies the Executive command file If none is specified, the system uses the default file [Sys]<Sys>Sys.cmds.
To be valid, a User file must include all of the SignOn entries that specify the default path (the path the system sets when you sign on). You can omit the parameter for file prefix and password; however, you must include the keyword.
The entry specifying the exit file is also required. The entries specifying a SignOn text file, chain file, and Executive command file are optional.
User File Application Entries
User files can include entries specifying parameters for applications. For example, the last three entries in figure 2-1 specify parameters for the word processing program.
Some applications have default parameters that you can change by specifying them in a User file. Others, such as the Mail Manager, require that you make entries. Refer to the application's documentation for further information.
Default User File
The system software includes a default User file, [Sys]<Sys>.user (refer to figure 2-2). In addition, some applications (for example, Multiplan) place User files on the system directory when you install the software. Refer to the application's documentation for further information.
The default User file allows any user to sign on to the
system without an entry in the User Name field of the Sign On form.
Note: To prevent unauthorized use of your system, you should delete the default file after you create the new User files for the authorized users of your system.
Figure 2-2 Default User File [Sys]<Sys>.user :ExecCmdFile:[sys]<sys>Sys.Cmds
:SlgnOnvolume:sys :SlgnOnOlrectory:sys :slgnOnFllePreflx:
:SignOnPasslIIOrd:
:SlgnOnExltFl1e:[sys]<sys>Exec.run
Adapting the System to Your Requirements 2-7
Creating and Modifying User Files
You can use any of the following tools to create or modify a User file:
o the Editor
o the word processing program o the User File Editor
When you use the Editor or the word processing program to create or modify a User file, you must be careful to make your entries in the proper format (refer to User File Entries, in this section).
When you use the User File Editor, the system formats the User file automatically.