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

Conference cookie::sls

Title:Storage Library System
Moderator:COOKIE::REUTER
Created:Sun Oct 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2270
Total number of notes:7850

2002.0. "V2.7 storage startup problems" by COMICS::CURREN () Mon Jun 17 1996 19:33

T.RTitleUserPersonal
Name
DateLines
2002.1use SYSTEM_BACKUP instead of SYSTEMBACHUS::RENTYTue Jun 18 1996 06:0221
2002.2thanksCOMICS::CURRENTue Jun 18 1996 12:068
2002.3SLS$SYSBAK logical name, is SLS running ?HLSM01::HENK_HHenk Hofman @UTOTue Jun 18 1996 14:479
2002.4Storage startup problemSNAX::SMITHI FEEL THE NEEDFri Apr 25 1997 15:3639
    We are running (trying to run) SLS T2.9 on an open vms 7.1 system.
    Upon issuing the STORAGE STARTUP SYSTEM_BACKUP BETA_TEST_SBK.COM
    command, the backup fails with the error 
    
    Reply received on SANITY from user PROPER at SANITY Batch 13:14:19
    Error processing startup command SYSTEM_BACKUP BETA_TEST_SBK.COM
     - %CLI-W-VALREQ, missing qualifier or keyword value - supply all
    required values
    
     - see log file ALTSYS$:[PROPER]SLS$TAPMGROP_5.LOG;
    
    The above log shows........
    
    $ vfy = F$VERIFY(0) $ write sys$output f$environment("control") 
    $ SET
    NOON 
    $ GOTO OTHER 
    $OTHER: 
    $ @login 
    $SET NOVERIFY    
    Welcome to SANITY PROPER account on device ALTSYS$: 
    4   
    OFFSITE_DATE == ""   
    ONSITE_DATE== ""   
    SCRATCH_DAYS == "56" 
    %DCL-W-VALREQ, missing qualifier or keyword value - supply all required 
    values   
    PROPER       job terminated at 25-APR-1997 13:14:19.16   
    Accounting information:  
    Buffered I/O count:             114         Peak working set size:   1155  
    Direct I/O count:                45         Peak page file size:     6520  
    Page faults:                   1021         Mounted volumes:            0  
    Charged CPU time:           0 00:00:03.40   Elapsed time:   0 00:00:07.32
    
    
    I don't get any errors of this type running TAPESTART.COM or running
    the SBK file via @BETA_TEST_SBK.COM.
    
    Steve 
2002.5Not the SBK fileSNAX::SMITHI FEEL THE NEEDFri Apr 25 1997 16:044
    Copied another SBK file over from another system (known to work fine)
    and got the same error. Safe to say the SBK file isn't the problem.
    
    Steve
2002.6SET VERIFY in SLS$SYSTEM:OPSTART.COMCX3PST::WSC217::SWANKDavidFri Apr 25 1997 17:278
re .4 & .5
\
\Steve,

Try adding a SET VERIFY to the top of SLS$SYSTEM:OPSTART.COM and see if the 
the offending command can be seen in the log file.
\
\Regards, David
2002.7Added set verifySNAX::SMITHI FEEL THE NEEDFri Apr 25 1997 17:563
    Ran the backup again, and it failed with the same error. This time
    the SLS$TAPMGROP.LOG file showed OPSTART.COM running but that error
    did not show up in OPSTART. I'll try the same for SYSBAK.COM.