ADSM-L

Re: Node access

1997-02-20 01:08:23
Subject: Re: Node access
From: "Dwight E. Cook" <decook AT AMOCO DOT COM>
Date: Thu, 20 Feb 1997 00:08:23 -0600
Item Subject: Node access
     Ok, grey area here but... hasn't stopped me in the past ;-)
     First, the standard question of: What's the client code level?
     Second, you can only grant access to "LIKE" nodes.
     Third, pattern matching is required so where as the scanner/lexical
     analyzer in breaking the statement down into tokens and checking
     "syntax" didn't put up an error you still have to remember it is
     looking for a file name, which is a drive, path, & name Sooo being the
     puckered person I am I see:  drive: thumper_D ; path: does_not_exist ;
     name: does_not_exist... I would try something like thumper_D:\* or
     thumper_D:\...\*  OR BOTH!  When security is an issue one can't assume
     that not listing denotes a wild card.  OOPS in looking again I see
     your \*\* but once again in a general overview of systems (and
     specifically in ADSM this would/SHOULD only denote access to any file
     in the second level of the directory structure use \...\ to denote
     "down any path" (& I always throw in the \* to cover the top directory
     level files just to CMA)
     I also have a heck of a time with such things... REMEMBER THAT things
     might not be correct but they will be consistant! So try a QUERY
     FILESPACE for thumper from an admin session and plug in what ever it
     gives you... On my Novell netware clients the file space has the node
     associated with it, that is netware client blah has filespace
     blah\SYS: but the winNT's for client blahNT has filespace D-DISK and
     E-DISK and the such... and these are NTFS, oh, and no ":" assiciated
     with the "drive" but we do know the ":" is the "delimiter" between
     drives and directory paths...
     TRY (if q file nodentserver yields thumper_D) thumper_D:\...\* and for
     safety also use thumper_D:\*

     It might also help, if you use the "C" language to look at the .h
     files in the API stuff to see kind'a how they are breaking things
     down... for all platforms things are in three (3) levels... what they
     call "fs" for file system (up to 1024 in length) "hl" for high-level
     qualifier (up to 1024) and "ll" for low level BUT for NT's is just the
     drive the "fs" and the dirpath the "hl" and the dsn the "ll"  OR is
     the drive & path the "FS" and the "hl" is the 8 and the "ll" the .3 ?
     ARGH!!!!! & I haven't done any testing to see....
     Hope this helps.....
     later
          Dwight



______________________________ Reply Separator _________________________________
Subject: Node access
Author:  ADSM-L at unix,sh/DD.RFC-822=ADSM-L AT VM.MARIST DOT EDU
Date:    2/19/97 11:37 AM


I am having problems allowing one node access to the data of another
node.  The ADSM client whose data I want the second node to access is
an NT client with three drives.  ONe drive is FAT and the other drives
are NTFS.  Filespaces and data exist on the ADSM AIX server for the
node.  The node is called thumper.

I can give access to the FAT filespace but am having problems giving
access to the NTFS filespaces.  One NTFS filespace name is "thumper_D:"
(without the qoutes) I have tried the following commands from dsmc on
thumper:
  set a b "{thumper_D:}" nodeb
      no files previously backed up from \ADSM32\THUMPER_D
  set a b {thumper_D:} nodeb
      no files previously backed up from \ADSM32\THUMPER_D
  set a b {thumper_D:}\*\*
      no files previously backed up from \*\*

  and other variations to this to no avail.  Is the colon (:) in the
name a problem?

  Does anyone have any suggestions or ideas?  I'd love to hear them.


  TIA
  Ron Heflin
  IBM Global Services
  847-562-7009
<Prev in Thread] Current Thread [Next in Thread>