If you have groups of users with identical login script needs, you can create a Profile object, then create a login script for it. Then you can assign each user to be a member of that Profile object.
The following list shows an example of a profile login script you might create for users in the Profile object ACCOUNTING. This profile login script would execute after the container login script had executed.
Prevents MAP commands from displaying on the screen as they are assigned.
Prevents mapping errors from displaying on the screen.
Maps the first available search drive (after those assigned in the container login script) to the directory that contains the database program.
5:=VOL1:ACCOUNTS\NEW
Maps the fifth network drive (after those assigned in the container login script) to the NEW subdirectory.
6:=VOL1:ACCOUNTS\RECORDS
Maps the sixth network drive (after those assigned in the container login script) to the RECORDS subdirectory.
Executes WSUPDATE which updates the IPXODI.COM file on the user's workstation with a new version of the file located in the first search drive.
Allows MAP commands to display.
Displays a list of all drive mappings.
Displays a blank line between the list of mappings and following lines.
Causes the phaser sound occurs twice on Friday's to alert the user
while the message Weekly progress report is due today
displays on the screen.
Stops the profile login script and sends the user into a menu program called WORK.EXIT also prevents any user login scripts from executing.
If you want a user login script to execute after the profile login script, put these lines at the end of the user login script instead.
(DOS workstations with the machine name IBM_PC do not need the PCCOMPATIBLE line.)
The EXIT command does not work on OS/2 workstations.