I think about downgrading  to Level 0.1 (IP21174.tar).
Could someone make this old version available ?  Thanks.

We encounter the following problems, especially with newer levels:

(1) None of the 3.1 Clients
    that distinguish between "Local" and "Network Filespace"
    works in Digital-Unix automounter-enviroment.

    We tried
        Version 3 Release 1, Level 0.3
        Version 3 Release 1, Level 0.5
        Version 3 Release 1, Level 0.6
        Version 3 Release 1, Level 0.7 on Digital-Unix 4.0d
   (Server is Version 3, Release 1, Level 2.20 on AIX-RS/6000)

   In all cases "Network Filespace" shows only the physical mountpoints
   and does not follow the symlink of the logical paths

        (example:
                elgon:/dist1/admin
        is asignd to the logical path
                /DIST/admin
        the automounter-daemon on another node mounts this filesystem
        dynamicaly to the physical mountpoint
                /a/elgon/dist1/admin
        and establisches a symbolic link
                /DIST/admin/ -> /a/elgon/dist1/admin
        -> adsm -clients is only able to follow the physical mountpoint,
           which chandes if the disk migrates to another nfs-server)

(2) trying do do an archive on "Local Filsspace"
        /dist1/admin
                (with   /dev/rz0a            /
                        /dev/rz0g            /usr
                        /dev/rz5h            /dist1 )


   results not only in recursing subdirectories but to search the tree
   in *both* directions. It does not even stay in the "Local Filespace"
   but tends to cover the whole nfs-cluster, like
        /dist1/admin/.../usr/local/CASE/xyz
                (with /usr/local -> /DIST/alpha and
                      /DIST/alpha/bin/CASE -> /DIST/CASE,
                      no upward symlink across startingpoint )

(3) I did not have much luck with the use of "virtualmountpoint" yet
    on DEC-Unix.
    (3.1) If I use in now in 3.1.05
                virtualmountpoint       /
                virtualmountpoint       /usr
          dsm->Archive shows 2 identical / and
          2 identical  /usr -entries. So what?
    (3.2) do I have to use "virtualmountpoint" at all if I do a
                dsmc /DIST/alpha   followd by
                dsmc /DIST/share
          to make shure that both are kept sepearate?

          Are "Filespaces" asigned to the first section of the path
          by default rather than to the filesystem as defined by the
          operating system ? Is there a way to correct this ?


   the desired behavior of the client is trivial:
      ---------------------------------------------------------------
       follow the path given by the argument of dsmc, don't leave the
       filesystem from nowon and treat what you find there as distinct
       file"space"
      ---------------------------------------------------------------
   ...



Do you have any hints or comments ?
Do you have similar experiences with the DEC-Clients ?
Are the points mentioned above known to ibm or are they really unique ?

Thanks for your reply in every case.

   Reinald Gfuellner

--
--.---------------------------------------------------------------------
--.---------------------------------------------------------------------
 3~  Reinald  Gfuellner                            PGP: use finger  ..|.
 3~  Reinald  Gfuellner                            PGP: use finger  ..|.
     Lehrstuhl fuer Prozessrechner, TU Muenchen, phone: +49-89-289-23564
----------gfullner AT lpr.ei.tum DOT de-------------------fax:+49-89-289-23555-
=========================================================================