Conference noted::pwv50ift

4175.0. "autoshare fails always" by KAOFS::M_VALLEE (csc hull canada) Tue Feb 25 1997 15:27

    Hi 
    
    pw v5.0d
    
    The customer is trying to start pathwork on his node which works all
    processes come up the only problem is pathworks will not autoshare the
    system disk at all.
    
    Disk GRAND$DKA0:, device type RZ26, is online, mounted, file-oriented
    device,
        shareable, error logging is enabled.
    
        Error count                    0    Operations completed           
    1357162
        Owner process                 ""    Owner UIC                     
    [SYSTEM]
        Owner process ID        00000000    Dev Prot           
    S:RWPL,O:RWPL,G:R,W
        Reference count              176    Default buffer size                
    512
        Total blocks             2050860    Sectors per track                   
    57
        Total cylinders             2570    Tracks per cylinder                 
    14
    
        Volume label      "VAXVMS2H4055"    Relative volume number               
    0
        Cluster size                   3    Transaction count                  
    261
        Free blocks                87102    Maximum files allowed           
    256357
        Extend quantity                5    Mount count                          
    1
        Mount status              System    Cache name      
    "_GRAND$DKA0:XQPCACHE"
        Extent cache size             64    Maximum blocks in extent cache    
    8710
        File ID cache size            64    Blocks currently in extent
    cache   3873
        Quota cache size               0    Maximum buffers in FCP cache      
    1106
        Volume owner UIC           [1,1]    Vol Prot   
    S:RWCD,O:RWCD,G:RWCD,W:RWCD
    
      Volume Status:  subject to mount verification, protected subsystems
    enabled,
          file high-water marking, write-through caching enabled.
                                                                    
    
    above you see the disk in question and it's volume label is too long so
    we set a autoshare in lanman.ini 
    
    $$ type LANMAN.INI;8
    ;  LAN Manager initialization file, for server configuration.
    ;
    ;  Refer to the PATHWORKS V5 for OpenVMS (LAN Manager) Server
    Administrator's
    ;  Guide for information on keywords and keyword values.
    
    [server]
      alertnames = admin
      auditing = no
      security = user
      srvcomment = PATHWORKS V5.0A for OpenVMS (LAN Manager)
      SRVSERVICES = ALERTER,TIMESOURCE
    
    [vmsserver]
      autoshare = GRAND$DKA0=SYSFILES0
      COMPATIBILITY = YES
      hostmapmode = if_exist_else_default
      hostpasswordsync = yes
      noautoshare = dad, _dfs
      pwrkalias =
      debug = yes
      debugsize = 2048
    [workstation]
      DOMAIN = GRCA-PCNET
      othdomains =
    
    [netlogon]
      scripts = PWRK$LMROOT:[LANMAN.REPL.IMPORT.SCRIPTS]
    
    [remoteboot]
    
    [NODE_GRAND]
      LISTENNAME = GRAND
    
    Whenever pathworks is started he gets the following in the admin/anal
    
    
      ================= EVENT #4 ==================
    
    Event Time:   4-FEB-1997 06:45:49.55       Node:  GRAND
    Process Id:   00000530
    Event:        LAN Manager server warning
    Event Source: LAN Manager Server
    Event Class:  Warning
    
          Text:   Autoshare Warning: default autoshare label VAXVMS2H4055
    is too lon
    g
    
    and the pwrk$lmsrv.log contains the following at the end:
    
    
    7-FEB-1997 21:05:33.05 00000284:001DDBA0 Queue allocated
    (name=LMSRV_QUEUE_CALLO
    UT, ptr=007786D0)
    17-FEB-1997 21:05:33.65 00000284:001DDBA0 Queue allocated
    (name=LMSRV_QUEUE_IPCQ
    , ptr=00816480)
    17-FEB-1997 21:05:33.65 00000284:001DDBA0 Queue allocated
    (name=LMSRV_QUEUE_SMBQ
    , ptr=008164D0)
    17-FEB-1997 21:05:33.65 00000284:001DDBA0 Queue allocated
    (name=LMSRV_QUEUE_CHQ,
     ptr=00816520)
    17-FEB-1997 21:05:33.66 00000284:001DDBA0 Queue allocated
    (name=LMSRV_QUEUE_TERM
    Q, ptr=00816740)
    
    There are no Dollar devices.
    17-FEB-1997 21:05:58.32 00000284:001DDBA0 network=DECNET
    17-FEB-1997 21:05:58.53 00000284:00000000 Server allocating 10 more
    queue elemen
    ts
    17-FEB-1997 21:08:00.00 00000284:00817C60 Open File Caching is ENABLED
    (interval
    =5000ms, max_entries=100)
    17-FEB-1997 21:10:54.88 00000284:006431D0 ODS2DismountThread: volume
    USERFILES1
      has no open files or references, dismount check
    17-FEB-1997 21:10:54.89 00000284:006431D0 ODS2DismountVolume: remove
    references
    to volume USERFILES1
    17-FEB-1997 21:10:55.63 00000284:006431D0 ODS2DismountThread: volume
    USERFILES2
      has no open files or references, dismount check
    17-FEB-1997 21:10:55.63 00000284:006431D0 ODS2DismountVolume: remove
    references
    to volume USERFILES2
    17-FEB-1997 21:10:56.55 00000284:006431D0 ODS2DismountThread: volume
    USERFILES3
      has no open files or references, dismount check
    17-FEB-1997 21:10:56.56 00000284:006431D0 ODS2DismountVolume: remove
    references
    to volume USERFILES3
    
    
    We have tried to set the autoshare to dka0: dka0 without colon
    grand$dka0:, grand$dka0, nothing seems to catch we always get the
    message in admin/anal.Were is it failing TRACE files don't seem to 
    show anything either.
    
    $ sh log pwrk$root
       "PWRK$ROOT" = "PWRK$COMMONROOT:" (LNM$SYSTEM_TABLE)
    1  "PWRK$COMMONROOT" = "DKA0:[PWRK$ROOT.]" (LNM$SYSTEM_TABLE)
    
    

    Mark,
    
    Don't know what the problem is but fairly certain you'll see the
    autoshare error for any device with a volume label >10 characters even
    when you add the device to to the autoshare= line. 
    
    Are you sure it's not creating the autoshare?  Did you try 
    
    	$ net share sysfiles.0$
    
    Did you try adding a share using the autoshare:
    
    	$ net share test=sysfiles0:[somedir]
    
    Paul