Conference iosg::all-in-1_v30

1635.0. "Admin can create/rename but not delete users!" by KERNEL::LOAT (Bored....Bored....BORED!!!!) Tue Oct 20 1992 17:41

    
    A customer is running ALL-IN-1 3.0 under VMS 5.5, and he's got a
    problem with an administrator account he's using.
    
    From this administrator account, the user can create and rename
    accounts, but when the administrator attempts to delete an account,
    they get an error:
    
    "Failed to submit to batch - not privileged to submit jobs".
    
    The only thing I can find is that in both SA_SUBMIT_CREATE.SCP and
    SM_SUBMIT_RENAME.SCP, the submitting to the batch queue is done using
    GET OA$DCL = 'a1submit ....' whereas MUA_DEL_INTER.COM uses the DCL
    command "$ a1submit ....".
    
    Can someone out there explain the difference between these, and maybe
    throw light on why the user is getting errors when trying to delete a
    user?
    
    Thanx
    
    Steve.
    

    Steve,
    
    Not able to investigate this too far, but I recall getting errors like
    this when the file being submitted does not have the same owner as the
    ALL-IN-1 Profile file (see A1SUBMIT - Application Programming Ref.
    Volume 2, page 13). Could you check the ownership on the files being
    submitted in this case? (MUA_DEL_ACCOUNT.COM ?). Thanks.
    
    Cheers,
    DaveT

    
    	The rule that A1SUBMIT enforces is that the submitted file must
    	have the same owner as A1SUBMIT.EXE actually. (Uses $GETJPI to
    	get it). The documentation must be wrong if it says PROFILE.
    	Amounts to the same thing, the owner is probably wrong on the
    	scripts.
    
    Regards,
    Paul

    Yep - it does say Profile. I remember now, its the exe file that
    counts; I've changed the ownership a few times! Sorry.
    
    dt