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

Conference cookie::smfs

Title:Sequential Media Filesystem for OpenVMS VAX
Moderator:COOKIE::KYLER
Created:Mon Aug 30 1993
Last Modified:Thu May 01 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:66
Total number of notes:198

59.0. "INVALID SCRATCH POOL error using SMF to copy file." by CSC32::V_HEINICKE () Mon Feb 03 1997 16:41

    Hi,
    
    TL810
    kfpsa
    hsd30
    alpha running V6.2 of VMS
    SLS V2.8 ECO 2
    SMF V1.2
    
    I have a customer who is setting up SMF.  He is getting invalid
    scratch pool errors when trying to do a copy as follows:
    
       rms-f-wer
       system-f-ivpool
    
    We have verified that tapestart has the correct triplets.  We have
    verified that the volumes have the correct pools as well as the correct
    media type and density and are free.  We have verified that he has
    authorized SMF in the pool authorization (in fact he had authorized
    SMFS and I had him then add an SMF as well to be associated with that
    pool).  We have set thedevice to recognize the correct scratch pool
    through smf.  Also did a 'smf set file' using that pool as well.  We
    can do a storage select and storage load using media type successfully.
    
    We even tried to set the MXX2 device to indicate the correct
    media_type, scratch_pool, etc to noavail.
    
    Do you have any ideas as to what could be causing this error?
    
    It appears everything is set up as expected.  He is concerned about the
    KFPSA maybe not being supported under V1.2 of SMF and that possibly
    this is causing the problem.
    
    
    Thanks,
    
    Victoria   
T.RTitleUserPersonal
Name
DateLines
59.1check poolauth againCOOKIE::KYLERMon Feb 03 1997 17:5727
    
    SS$_IVPOOL is returned by SMF if and only if an MDMS service returns
    SLS$_BADPOOL. 
    
    MDMS returns SLS$_BADPOOL if and only if the pool authorization check
    fails during a media allocation attempt.
    
    Please check the pool authorization again, ensuring that:
    
    1) SLSMGR is being run on the MDMS database node for the node running
    SMF.
    
    2) The pool has entries for username "SMFS" (note that SMFS _is_ the
    correct username) for each node (not cluster aliases) which may need
    access to the pool through SMF.
    
    To test outside of SMF, try 
    
    	$ STORAGE ALLOCATE <media-type> /USER=SMFS /POOL=<pool-name>
     
    I don't expect that the KFPSA will be a problem, but it most certainly
    is not causing this problem, as we're still trying to allocate a tape
    and haven't gotten anywhere near the data or robot control paths.
    
    - Dan.
    
    
59.2NCP not appropriately set upCSC32::V_HEINICKETue Feb 04 1997 13:1615
    Hi Dan,
    
    Went and verified that the SLSMGR pool authorization was correctly set.
    It was.  Had him go into sysgen and check the scsnode name.  It was
    correct.  Then had him go into NCP and do a 'show exec char'.  It
    returned a 0.  At that point he told me he could not 'set host 0' nor
    could he set host to the nodename - OSCAR1.
    
    I logged a call for him with the DECNET team to straighten that mess
    out.  Once done, he will call me back should he encounter further
    problems.
    
    Thanks for the quick response.
    
    Victoria