PROFILE version 2.0 new features: ================================================================================ Qualifiers can now be used with PROFILE, either from the DCL command line, or from within the program itself. The following qualifiers are valid: /QUOTA=amount - default value is 1000 and amount is not specifically required in this case. /NOQUOTA - diskquota will not be added when creating a new account. /OVERDRAFT=amount - default value is 100 and amount is not specifically required in this case. There is no negative for this qualifier. /NOMAIL - mail notification will not be sent to the new user. /MAIL - mail, in the form of a welcome message, will be sent to the new user. This is the default setting. /NODIRECTORY - directory will not be created for the new user. Can be abbreviated to /NODIR. /DIRECTORY - directory will be created. Can be abbreviated to /DIR. This is the default setting. /NOADD_IDENTIFIER - do not add account identifier when creating a new account. Can be abbreviated to /NOADD. /ADD_IDENTIFIER - add account identifier when creating a new account. This is the default setting. Can be abbreviated to /ADD. /NOECHO_PASSWORD - do not echo the password to the screen when entering a new value. Also, when this qualifier is given, the password field will always say "(secret)". Can be abbreviated to /NOECHO. /ECHO_PASSWORD - password will be displayed on the screen, if it's a new account, and will be echoed when entering a change to the password field. This is the default setting. Can be abbreviated to /ECHO. ================================================================================ The security alarm generated by the audit server now presents an accurate view of the fields that have been modified. In the previous version of PROFILE, all fields were set regardless of their changed status. Now only those items that have been changed will be reflected in the security alarm. This only works for a single account addition/modification, however, and a bug persists wherein the changed fields from the first account changed will carry over to a second account modification, unless the program is exited and then restarted. This behavior only reflects on the security alarm and does not actually cause any abnormal changes to the accounts themselves. This will be fixed in a future release (I hope!). ================================================================================ The code has been completely rewritten and broken down into smaller pieces to make it more manageable. Also, modification of the code by the user is no longer necessary, since the qualifiers make reconfiguration possible. ================================================================================ New keystroke commands: C - cancel the change made to an item, or field of items, and restore the previous value. R - restore all items to their original values. ? - display a brief overview of keystroke commands. ================================================================================ When modifying access times, the cursor used to jump above or below to the next field when coming to the end of the line. Now, because it seems to make more sense to me, the cursor stays on the same line when reaching the end of the column. ================================================================================ All changed items on the main board are now highlighted so that the user can see at a glance what has been changed. For new accounts, any field that would normally be set different than the DEFAULT account will be highlighted as well. ================================================================================ When renaming an existing account, the directory is now changed to match the name of the new user.