[Ted Byrne]

From: Bill Fitzgerald <[EMAIL PROTECTED]>
I have a client running Sun Solaris 5.8
with client version 5.1.5
TSM server is AIX 4.3.3 running TSM 5.1.6.5
Below is the  include/exclude list from the  dsm.sys
   include * shared_dynamic_60
        include /adsmorc/.../* database_class
        include /dev/.../* database_class
        include /udb/.../* database_class
        include /MOUNT/.../* database_0
        include /usr1/.../* database_0
        exclude /tmp/.../*
we recently add the last two includes, stopped and started the client, and
the objects were rebound.


Bill,

        You might want to investigate exactly _what_ was rebound after
applying the changes to the include/exclude list.  In my experience, the
include/exclude syntax on the *nix platforms can be a bit misleading.
        For example, the statement exclude "/.../*" would appear to
exclude all files on the client.  What it actually does is exclude all
files *only* in the "/" filesystem.
        The first part of an include or exclude statement refers to the
filesystem, not a directory.  In the Win32 world, this is explicit, since
you have the colon separating the drive letter (or filesystem) from the
path. On *nix systems, the distinction is not readily apparent.
From the expiration messages that you posted, you appear to have other
filesystems mounted below /usr1 and /MOUNT:
        /usr1/GATE, /usr1/EXPORT, /MOUNT/MISC, /usr1/ICACHE/1

If you issue a "q ba /usr1/GATE/*" fom the baclient command line, or browse
there with the GUI, I'm betting that you will see the managementclass as
"SHARED_DYNAMIC_60"
If you add these lines to your cinclude/exclude list, you should get the
results that you are looking for.
        include /usr1/GATE/.../* database_0
        include /usr1/EXPORT/.../* database_0
        include /usr1/ICACHE/1/.../* database_0
        include /MOUNT/MISC/.../* database_0
Hope this helps,

Ted