When creating an account creation template in ALL-IN-1 V2.4, it will complain
if you try to use a logical name for the device.  I really want to use
groupname$DISK: for the device, and always have prior to V2.4.  What I need is
to have the DISK1 field on the template form allow the use of a logical name,
and for that logical, not its translation, to show up on the user's profile.

Here is what I did to remove this restriction.

1. Using CM, comment out two lines in OA$SM_VALIDATE_MA_DEVICE.COM:

   $!
   $! The two commands below make it so that we cannot use logical names
   $! for our disks in the user profile during account creation.  Thus
   $! they were commented out. (11/02/90 C.M. Simon)
   $!
   $!      parsed_device = f$parse(device,,,"DEVICE","SYNTAX_ONLY")
   $!      IF parsed_device .NES. device THEN GOTO err_dev_invalid
   $!

   The procedure will still check to make sure that the device name or
   logical you entered is a disk and is mounted, but will no longer care
   if what you entered is equal to the actual device name.

2. Using CM, modify the named data of SM$CREATE.FRM:

   In the section ~~PREPOP_DIRECT~~, one line needs to be changed:

   	.
   	.
      GET UAF_DIR = UAF$DIRECTORY[VMSUSR]\\
      GET DISK = UAF$DEVICE[VMSUSR]    		<==== change this line
     ELSE 
   	.
   	.
    	.
   	.
      GET UAF_DIR = UAF$DIRECTORY[VMSUSR]\\
      GET DISK = SMTEMPLATE:TEMPLATE.DISK1[TEMPLATE] <=== to this
     ELSE
    	.
   	.
    The effect this has is to get the logical name you entered in the
    template instead of the actual device name from the existing VMS
    account's UAF record.  (The logical will be validated using
    OA$SM_VALIDATE_MA_DEVICE.COM, so if you don't make the change in step
    1, this isn't going to work.)

3. Copy the form SM$CREATE2 to the development area.  No changes are
   needed, but this one must be moved to the live area because is it part
   of a form set with SM$CREATE.

4. Move OA$SM_VALIDATE_MA_DEVICE, SM$CREATE, and SM$CREATE2 to the live
   area and precompile OA$LIB:SITEMANAGER.


    DISCLAIMER:

    The steps described above make use of the following assumptions:

    1) Our VMS accounts are NOT created from inside ALL-IN-1.
    2) We do not use the feature which allows multiple devices to be
       specified on the account creation template.