Conference iosg::all-in-1_v30

1662.0. "%OAFC-I-SRVNOTAVAIL and Start Server bug or feature ?" by GIDDAY::SETHI (Man from Downunder) Tue Oct 27 1992 05:00

    Hi All,
    
    A customer was having a problem with the Shared File Cabinet when they
    tried to edit a document they got the error message
    "%OAFC-I-SRVNOTAVAIL, file cabinet server is not available",  looked
    for the process <node name>$SRV73 that was missing.
    
    To start the server we accessed the sub-system Manage Servers (MS) from
    the Manage File Cabinets (MFC) and chose the option STA.  The Server
    was in a stopped status.  Very straight forward so far I think that I
    have spotted a bug and I will SPR it if required, on the other hand it may
    not be a bug but a feature.
    
    If you are not logged in as the ALL-IN-1 manager the batch job is
    submitted and the following message is displayed "RAKOFF::"73="
    submitted to MB$BATCH_RAKOFF for startup".  The command that is used is
    the VMS submit command and not the A1SUBMIT for example
    
    submit/que=MB$BATCH_RAKOFF/-
    param=(DISK$OFFICE_DISK:[ALLIN1.DATA_SHARE]RAKOFF$SERVER73.DAT;1,RAKOFF$SRV73)/
    noprint/noidentify/log=oa$log:oafc$server_startup.log

    No message is displayed indicating that you have to be logged in as the
    ALL-IN-1 system manager.  Looking at the logfile nothing is displayed
    indicating a problem.  If you chose the STO option to stop the selected
    server you have no problems at all.
    
    I would like to draw attention to the following points 
    
    1. Being able to stop the server from an accounts that has access to the
       System Managers sub-system and NOT being able to start the server to me
       seems inconsistent.
    
    2. The lack of warning and/or error messages I feel is unacceptable
       when trying to start the server from an account other than the ALL-IN-1
       system managers' account.  The logfiles also does not give you any
       error messages.
    
    3. Should the A1SUBMIT image be invoked and not the VMS SUBMIT image when 
       submitting the batch job ?
    
    4. The batch job does not inform you that the server has start nor is
       the status field updated.  To update the status field you have to
       spawn out or logout of ALL-IN-1 than log back in.
    
    Having discussed this oddity there are two schools of thought.  The first 
    one argues that the functionality is correct because there should be only
    one ALL-IN-1 managers account.  The secound group argues if you can access
    the ALL-IN-1 system managers sub-system you should be able to use all the
    fuctionality unless stated in the manual or during a training course.  For
    my part I would like better error messages or warnings if you cannot carry
    out a function.  I am not trying to rub someone up the wrong way I just 
    want a clearification on the issue from the "horses mouth" or the "book".
    So in short I do not know if this is a bug or just the way it's suppose to
    work.

    I hope that you like the name of our wonderful system in Australia !!
    
    Sunil
    

    
    	Quite a coincidence, I was looking at this code last night...
    	I don't know about being a horse's mouth, but here's my opinion
    	FWIW.
    
>    1. Being able to stop the server from an accounts that has access to the
>       System Managers sub-system and NOT being able to start the server to me
>       seems inconsistent.
>    
    	Debateable. Possibly the menu should check privs and warn you that
    	you are not going to be able to start the server again if you stop
    	it. Technically, you only need OAFC$SYSMAN to stop the server.
    
>    2. The lack of warning and/or error messages I feel is unacceptable
>       when trying to start the server from an account other than the ALL-IN-1
>       system managers' account.  The logfiles also does not give you any
>       error messages.
>    
    	I did this too, and was worried that I had started a server under
    	my account instead of the proper one. After weighing things up,
    	I guess the menu should just insist that you have OAFC$SYSMAN
    	(and OA$MANAGER to be doing any of this SM stuff) and provide all
    	the other privs. If you have OAFC$SYSMAN then someone thinks you
    	should be managing the servers. If you don't have OAFC$SYSMAN
    	then you probably shouldn't even be allowed on the menu.
    
>    3. Should the A1SUBMIT image be invoked and not the VMS SUBMIT image when 
>       submitting the batch job ?
>   
    	I think I agree. I would worry if the server was started under my
    	account (it may not hurt, but I'd still worry).
     
>    4. The batch job does not inform you that the server has start nor is
>       the status field updated.  To update the status field you have to
>       spawn out or logout of ALL-IN-1 than log back in.
    
    	You just need to press return on the manage servers menu to have
    	the status field updated. If you press return often enough, the
    	server will start and the status will update.
    
    	Would you care to submit a bug?
    
    Regards,
    Paul