We seem to have a problem with OS/2 Warp Server/(with hpfs)
and ACL's on a restore at the root/base directory path. We are
running AIX r4.2 with ADSM server v3.1.0.1, have tried various
levels of OS/2 client codes.
Client revs. for OS/2:   v2.1.0.6,  v2.1.0.8 and now v3.1.0.3.

Here is an example a small test to illustrate the problem:
Set up directory structure and place ACL's on each level, populate
      directories
with small file. Do a backup and then restore to a new subdirectory.
We validated the info. at each step. We found ACL's missing a base level of
      the
directory tree. Please let us know how if any you got over this hurdle.

Any suggestions from those who have this working right. when the
ADSM server was 2.x.x.x we did note have this problem.

Thanks in advance for your help!!!

Start: source...
Ran: "dir f:\adsmtest\*.* /s"

The volume label in drive F is F13_F1.
The Volume Serial Number is 6706:9014.

Directory of F:\adsmtest

 4-02-98   3:10p     <DIR>           0  .
 4-02-98   3:15p     <DIR>           0  ..
 3-20-98   9:10a      4278           0  Config.Sys
 4-02-98   3:10p     <DIR>           0  sub1
 4-02-98   3:10p     <DIR>           0  sub2
        5 file(s)       4278 bytes used

Directory of F:\adsmtest\sub1

 4-02-98   3:10p     <DIR>           0  .
 4-02-98   3:10p     <DIR>           0  ..
 3-20-98   9:10a      4278           0  config.001
        3 file(s)       4278 bytes used

Directory of F:\adsmtest\sub2

 4-02-98   3:10p     <DIR>           0  .
 4-02-98   3:10p     <DIR>           0  ..
 3-20-98   9:10a      4278           0  config.002
        3 file(s)       4278 bytes used
Total files listed:
       11 file(s)      12834 bytes used
                   1631232 K bytes free
Ran: "net access f:\adsmtest /tree"

Resource  Permissions                            Permissions
---------------------------------------------------------------------------
----
----
f:\adsmtest
f:\adsmtest
          *USERS:RX                              TIMW3:RWCDA

f:\adsmtest\sub1
          *USERS:RX                              IWIF2:RWCDAP
          TIMW3:RWCDA

f:\adsmtest\sub2
          *USERS:(none)                          IWIF2:RWCDA
          TIMW3:RWCDA
The command completed successfully.

Restore:

Ran: "dir f:\adsmtst2\*.* /s"

The volume label in drive F is F13_F1.
The Volume Serial Number is 6706:9014.

Directory of F:\adsmtst2

 4-02-98   3:13p     <DIR>           0  .
 4-02-98   3:15p     <DIR>           0  ..
 3-20-98   9:10a      4278           0  Config.Sys
 4-02-98   3:13p     <DIR>           0  sub1
 4-02-98   3:13p     <DIR>           0  sub2
        5 file(s)       4278 bytes used

Directory of F:\adsmtst2\sub1

 4-02-98   3:13p     <DIR>           0  .
 4-02-98   3:13p     <DIR>           0  ..
 3-20-98   9:10a      4278           0  config.001
        3 file(s)       4278 bytes used

Directory of F:\adsmtst2\sub2

 4-02-98   3:13p     <DIR>           0  .
 4-02-98   3:13p     <DIR>           0  ..
 3-20-98   9:10a      4278           0  config.002
        3 file(s)       4278 bytes used
Total files listed:
       11 file(s)      12834 bytes used
                   1631232 K bytes free
Ran: "net access f:\adsmtst2 /tree"

Resource  Permissions                            Permissions
---------------------------------------------------------------------------
----
----
f:\adsmtst2\sub1
f:\adsmtst2\sub1
          *USERS:RX                              IWIF2:RWCDAP
          TIMW3:RWCDA

f:\adsmtst2\sub2
          *USERS:(none)                          IWIF2:RWCDA
          TIMW3:RWCDA
The command completed successfully.

Note: missing the f:\adsmtst2 ACL which should have been :
---------------------------------------------------------------------------
---------------------------
---------------------------
f:\adsmtest
f:\adsmtest
          *USERS:RX                              TIMW3:RWCDA
---------------------------------------------------------------------------
----------------------------
----------------------------
ANY Suggestions from those who have this working right. when the
ANY Suggestions from those who have this working right. when the
ADSM server was 2.x.x.x we did note have this problem.

Thanks again...

P.S. I have already started a PMR to the IBM help folks.


twhite2 AT tuelectric DOT com