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

Conference cookie::archive_backup

Title:Archive/Backup
Moderator:COOKIE::MHUAIG
Created:Wed Sep 08 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:479
Total number of notes:2283

441.0. "Invalid Parameter to Scheduler Utiltiy" by CX3PST::BSS::SAUL () Mon Apr 21 1997 15:20

Hi,

We get the following error when attempting to create SAVE request...

$ abs save incre/start="21-APR-1997"/name=monday5
Creation of Save Request MONDAY5 failed for the following reason:
Invalid parameter to scheduler utility


I've seen this before and can't remember what causes it.  The 
SAVE request gets created just fine but the Scheduler job does
not.  Any ideas?

Also, on customer system, GUI is taking 100% of CPU.  We've 
checked the images to make sure there is no version confusion.
What should we look to tune on the GUI?  Thanks.

Ted
T.RTitleUserPersonal
Name		DateLines
441.1QARedCOOKIE::MHUAMon Apr 21 1997 16:3013
    
    Ted,
    
    I was able to reproduce the error on my alpha system.  It is logged in
    out QAR system.  We'll fix this in a future release.  QAR number is
    1895.
    
    About the CPU usage of GUI, we have not seen what you have reported.
    Does certain screen or button cause the CPU occupied 100%, or does
    this happen all the time?  What system (VAX or alpha) and what
    version of OS are they running?  Do they have DECnet plus?
    
    Masami
441.2CX3PST::BSS::SAULTue Apr 22 1997 10:4029
Hi Masami,

>    I was able to reproduce the error on my alpha system.  It is logged in
>    out QAR system.  We'll fix this in a future release.  QAR number is
>    1895.

I'm going to do a level 3 IPMT on this.  This needs to be done to prevent other
specialist from spending a lot of time looking for the same answer in the future. 
QARs do not generate any database articles.  Level 3 can be closed right away but
it will generate the article.  This reallys needs to be done for any problem found.

    
>    About the CPU usage of GUI, we have not seen what you have reported.
>    Does certain screen or button cause the CPU occupied 100%, or does
>    this happen all the time?  What system (VAX or alpha) and what
>    version of OS are they running?  Do they have DECnet plus?

It seems to be mostly when attempting to create a save request.  It does happen all
the time and he has to kill the job before he loses control the machine and has to
reboot.  This is AXP, 7.1 running phase 4.  He is looking at PAB casue SLS isn't
supported on 7.1 yet.

I'm seeing performance problems on our machines here but haven't been able to
isolate the problems as a GUI or a network display problem.  Just wondering what
might affect the GUI performance...UAF resources, SYSGEN paramters?

Thanks,

Ted
441.3CSC32::V_HEINICKEThu May 01 1997 10:1826
    Hi Masami,
    
    RE:   Invalid parameter to scheduler utility
    AND:  We'll fix this in a future release.
    
    If there is no workaround to allow scheduled backups, this leaves the
    customer without a product to use.  He cannot use SLS as he is running 
    V7.1 of VMS.  He cannot run scheduled backups from either the GUI or
    the command line at present.  He wants to know what you recommend?
    He needs some type of backup utility and if Digital cannot provide one
    that works as documented, he will look elsewhere.  Any workaround
    would be greatly appreciated.
    
    In terms of the GUI using 100% CPU or going away completely, he has
    additional information.  As long as he uses the MAJOR FUNCTION, save
    button, expand, and then add object, it accepts it - at least until he 
    tries to enter the sart time.  It is when he tries to do the SAVE 
    using the pull down menu and then add object that the GUI goes away.
    On the deletion of a save request from the GUI, sometimes CPU goes to
    100% and he has to kill the process and other times GUI just
    disappears.  Any ideas as to what is casuing this?
    
    Thanks,
    
    Victoria
441.4COOKIE::MHUAThu May 01 1997 14:097
    
    Victoria,
    
    We got your message.  We'll get back to you.  
    
    Thanks,
    Masami
441.5workaroundCOOKIE::MHUAThu May 01 1997 15:0314
    
    Victoria,
    
    Can you (and your customer) try this?  
    
    $ abs save incre/start=21-APR-1997/name=monday5
    
    I took the double quotes out of the original line reported by Ted.
    This worked for me.  If I put double quotes, ABS failed as reported.
    I will look further into why it's doing this, but for now, this may
    get them going.
    
    Masami
441.6GUI PROBLEMS - Using 100% CPU or dieingCOOKIE::GONZALEZTue May 06 1997 16:5424
    Hi Victoria,

    >>>>In terms of the GUI using 100% CPU or going away completely,

    Yes, there are problems with the GUI dieing when trying to use the 
    ADD OBJECT button during SAVE requests on Alpha machines.  As you
    mentioned, it is possible to work around this problem by using the
    MAJOR FUNCTION buttons instead of the pull-down from the main window.
    Of course, using DCL is also another way around.

    I haven't been able to reproduce the 100% CPU problem or going away
    problem when deleting a SAVE REQUEST, but will keep trying.  For now,
    I'm not certain what would be causing this problem.  
     
    We are focusing on replacing the existing GUI with a TOTAL replacement
    for our next release.  Therefore little or no resources are fixing current
    GUI problems that have workarounds.

    Thanks, Mickey

    P.S. The ABS OMT GUI was shipped with ABS 2.1  The customer could use 
    this interface to delete SAVE REQUESTS or DCL.  If the customer
    decides to try the ABS-OMT GUI, let me know if CPU problems resurface.