Technical data

Managing User Accounts
7.7 Maintaining User Accounts
In establishing login command procedures for interactive accounts, you have the
following choices:
Login
Command
Procedure Description
System As system manager, you normally create and maintain a standard login
command procedure in the system directory (the file is usually named
SYS$MANAGER:SYLOGIN.COM). You then assign the logical name SYS$SYLOGIN
to the name of the file so that whenever a user logs in, the procedure is executed.
Individual For any or all accounts, you can specify an additional login command procedure with the
/LGICMD qualifier of the AUTHORIZE commands ADD, MODIFY, or COPY. You can
give the login command procedure any valid file specification. Whenever the user logs
in, the additional procedure is executed after SYS$SYLOGIN.
User-specified
command file
If system (and, optionally, individual) login command procedures are not implemented,
the system looks for a command file called LOGIN.COM in the user’s login directory as
defined by the UAF (user authorization file) record device and directory fields. If the file
is found, the system executes it. The user develops and maintains this command file,
which should follow these conventions:
• Device and directory names must take the default file specification for the account.
• The file name and file type must be LOGIN.COM.
You can provide an aid to new users by copying a login command procedure template
into newly created top-level directories. However, to ensure proper ownership of the file,
change the owner UIC (user identification code) of the file to that of the user. Make this
change with the DCL command SET FILE/OWNER.
Example 7–1 illustrates typical systemwide login command procedures.
7–20 Managing User Accounts