[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1682.0. "Adding ALL-IN-1 account" by NCBOOT::HARRIS (oooppps) Wed Oct 28 1992 22:08

    ALL-IN-1 v3.0
    VMS 5.5
    
    creating accounts in ALL-IN-1 that do not have an exisiting VMS account
    
    everything seems to go ok, except it i look at the uaf file afterwards,
    the DEFAULT field says USER and the owner field id blank.
    
    here is the part of the create log where i think it is hosing up.
    
    thanks - ann
    
           UAF show [400,013534]
    %UAF-W-BADSPC, no user matched specification
    $       if $status then goto inc_retry_count
    $!
    $       set noon
    $       on error then continue
    $       UAF ADD US275173 /uic=[400,013534]
    %UAF-I-ADDMSG, user record successfully added
    %UAF-I-RDBADDMSGU,
    identifier US275173 value: [000400,013534] added to rights data base
    $       if .not. $status then goto wont_create
    $       set def sys$login
    $       goto make_vms_account
    $ make_vms_account:
    $!
    $       set noon
    $       on error then goto wont_create
    $!
    $       vms_account = f$extract(0, 8, vms_account)
    $! Set noverify to avoid display of password
    $!
    $       preserve_verify = f$verify(0)
    %UAF-W-DIRSYNERR, directory syntax error \PU01:[US275173]\
    -RMS-F-SYN, file specification syntax error
    %UAF-I-NOMODS, no modifications made to system authorization file
    %UAF-I-NAFNOMODS, no modifications made to network proxy data base
    %UAF-I-RDBNOMODS, no modifications made to rights data base
    $!
T.RTitleUserPersonal
Name		DateLines
1682.4not standardIOSG::TYLDESLEYThu Oct 29 1992 12:108
    Just to confirm Scott's assessment, this is either an old version
    of mua_create.com being used, or possibly a customization. Although
    I seem to recall the label make_vms_account:, I can't find it in 
    either the V2.3 or V2.4 mua_create.com's. Perhaps you could check 
    the oa$lib: areas for an old or custom com file?
    
    Cheers,
    DaveT
1682.5ANGLIN::HARRISLet the party begin...Thu Feb 11 1993 18:235
    sorry it took so long to get back....
    
    i did find an "old" mua_create.com on the 3.0 system.
    
    All is well now.
1682.6error accessing calendarANGLIN::HARRISLet the party begin...Thu Feb 11 1993 18:3624
    a different, yet similar question...
    
    ALL-IN-1 3.0-1, VMS 5.5-2, MR 3.2
    
    Customer has a program (called SYSADMIN) that the site administrators
    use to manage accounts.  they can create VMS acccounts with ALL-IN-1.
    creating VMS accounts works fine. adding ALL-IN-1 works ok EXCEPT that
    we keep getting the error
    
    Error occurred trying to access ANN, TESTA8 's Calendar
    
    when logging into the new account.  at the TM EV screen, the "little
    calendar" is missing.  i must have a field missing or incorrect in the
    profile - but what field?
    
    i recreated the .a1cal file with create/fdl - same error.
    ownership/protection is fine on the .a1cal file.
    
    what causes this error:
            Error occurred trying to access ANN, TESTA8 's Calendar
    
        thanks - ann
1682.7Just to make sureAIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Fri Feb 12 1993 12:573
        The name of the calendar file should be ANNTESTA.A1CAL.
        
        Dave Zaniewski
1682.8its all in the name...ANGLIN::HARRISLet the party begin...Fri Feb 12 1993 14:526
    dave -
    
    thanks.  renaming the .A1CAL worked.  now, I just have to look back and
    find out why it was created wrong in the first place!
    
    THANKS !  	ann