[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

1201.0. "No space available message as MUA CU fails " by COMICS::TALBOT (Trevor Talbot) Fri Aug 07 1992 11:36

    Hi,
    
    	Has anyone seen problems with creating accounts and getting the
    mail message to the manager saying, 
    
    'No space available on any of the specified disks'
    
    	AND
    
    having in the log file (oa$log:oa$create_fred4.log)
    
    Finished adding disk quota with status = -3
    
    
    My Analysis so far:
    
    I can re-produce this here by modifying the oa$lib:sm_add_diskquota.com
    file to delete the sm_diskquota_out'pid'.tmp file just after the line
    SYSMAN DISKQUOTA SHOW 'USER'/DEV='DEV'/OUT='DISKQUOTA'
    so that the later reads of the .tmp fail and cause the jump to the
    label failed_quota.
    
    Or as the customer alledges his .tmp exists, but this is empty!! yep,
    it's true, I re-produced this as well BUT HOW DID IT become empty?
    
    The sysman command line when used outside of ALL-IN-1 works (according
    to customer) but when run through ALL-IN-1 remains created but empty??!
    
    Anyone got any ideas?
    
    -Trev
    
    p.s This site did have a co-exist prior to upgrading to full v3.0, I'm
    not sure whether this may have any bearing..
T.RTitleUserPersonal
Name		DateLines
1201.1several possibles to tryIOSG::TYLDESLEYFri Aug 07 1992 13:1939
Trevor,

There are several places within sm_add_diskquota.com that can cause a 
goto failed_quota e.g.:
    
$       on error then goto failed_quota
...
$       if f$search(diskquota_out) .eqs. "" then goto failed_quota
...
$       on warning then goto failed_quota
    
Since some of them are pretty general (on warning), then it's difficult
to say exactly where the customer's problem lies. One thing that seems 
certain is that the device passed to the procedure exists, otherwise it 
would have returned with an error 'invalid_device' pretty early on.

I have just $set verify on this com on the system here, and it worked with 
no problem. Is it possible that you ask your customer to do the same?
e.g. 
    $set verify                          just after the line:
    $! Check the parameters		 and: 
    $set noverify			 just before the line:
    $set default 'save_default'
    
should do it. Create an account, with this file in oa$lib: (site)  and 
then look at A1SUB.LOG in the manager account ALL-IN-1 directory. This 
should identify for you exactly why the add diskquota failed with this
particular message.

Sorry can't help further. You might also like to try the old faithfuls/
simple ones regarding disks:
1. have they got their disk logicals set up right, e.g. defined 
   /translation=concealed and all that?
2. has the manager account itself got quota on those disks?
3. is there any space left?

Cheers
daveT
1201.2The penny is dropping! I think.COMICS::TALBOTTrevor TalbotFri Aug 07 1992 15:4224
    Hi,
    
    	Thanks for the reply, Dave, I may have sussed why the file is
    blank,
    
    The sm_submit_create.com switches off severity messages etc..
    
    i.e set message/nosev/noid/nofac/notext
    
    now if you do this interactive and specify
    
    $mc sysman diskquota show newuser/dev=device/out=t.tmp
    
    because the newuser has no previous record in quota.sys and the error
    message supression is in place the file gets created and left blank.
    
    repeat the same for an existing account and the .tmp file has data in
    it.  
    
    Now the thing I have not yet sussed, and would like help on is, why his
    switches it all off and mine doesn't?
    
    -Trev
1201.3...DroppedCOMICS::TALBOTTrevor TalbotFri Aug 07 1992 16:5312
    I have now re-produced fully his problem, and fixed it for him!
    
    I could not see the problem earlier due to me using an existing VMS
    account that already had a valid quota entry. When I asked ALL-IN-1 to
    create a NEW VMS and ALL-IN-1 account then the -3 appeared without me
    having to fudge the .com.
    
    In the customer's sm_add_diskquota.com we add just prior to the sysman
    command the set message/sev/id/fac/text and all now seems o.k. This
    looks like a bug to me!
    
    -Trev
1201.4This error also when user has invalid UICAIMTEC::DONOHUE_FMon Aug 10 1992 17:0524
    
    FYI,
    
     I had a customer who was seeing similar symptoms as this problem, the
    same message in the mail notifying that the account creation failed,
    and the status = -3 failure when trying to add diskquota, but it
    was for a different reason.
    
     In this case, the VMS account already existed and the device did not
    have quotas even enabled, but the VMS account had an invalid identifier
    (i.e. it was not the same as the VMS account name but was an old
    VMS account name that had used this UIC before).  And when the
    SET MESSAGE ans SET VERIFY was used, the A1SUB.LOG contained
    the error on the SYSMAN DISKQUOTA command:
    
     "Invalid UIC specified"
    
    After removing the old ID and readding an ID for this user with the
    correct UIC, then the ALL-IN-1 account could be created successfully.
    
    Hope this is helpful,
    
    Faith
1201.5What version of VMS?AIMTEC::DONOHUE_FFri Aug 14 1992 16:5815
    
    I have been researching this problem to write a STARS article but I
    cannot seem to reproduce the error when trying to create a user account
    in either of these situations, when disk quotas are enabled and it
    is a new VMS account being created or when the VMS account exists
    and the identifier is invalid.  I am testing this on BL123A, with
    VMS 5.4.  And in both cases the account are created successfully.
    
    What version of VMS did the orginal problem or reproduction of it
    occur on?  
    
    Still trying to reproduce this one,
    
    Faith