ADSM-L

Node access

2015-10-04 18:10:12
Subject: Node access
From: INTERNET.OWNERAD at SNADGATE
To: Jerry Lawson at ASUPO
Date: 2/19/97 2:31PM
According to my manual, if you want to give access to another node, via the
command line interface, all you need to site is the drive letter, and
directories, etc.

A quick test I ran showed that the correct syntax should be

SET A B d:\* NodeB

As Dwight noted in another note - you can get into pattern matching, etc.
for the definition of what you want NodeB to have access to.

By the way, Dwight also mentioned the limit of cross client restores to
platforms that do not understand the file system - From what I can tell, this
is determined at restore time, not when you grant access.  For this test, I ga
ve a Windows 3.1 client the ability to access an OS2 HPFS drive.  The command
completed successfully but I know that if I attempt to restore anything from
this drive it will fail.  The moral is to be careful, - you can only restore
to platforms that understand the native file system.

Jerry Lawson
jlawson AT thehartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Node access
02-19-97 02:31 PM

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>