You don't show what client level you are running this on, so I tried it on
3.1.06, and got output similar to the below.  However, the query command
output did not say a thing about the exclude.fs statements, even though
they work at 3.1.06...

I guess that means one cannot trust the output of q/show inclexcl, and
must actually run the backup to test the function.

Gee, that makes me wonder how IBM/Tivoli tests this?  Or don't they test
this at all.  Testing exclude.fs is easy, so it makes me believe it was
never tested.

I think that the TSM/ADSM Developers and fix coders could learn a lot from
the MVS/VM groups in terms of quality assurance...


> dsmc> q inclexcl
> Node Name: FRPARD022150
> Please enter password for node "FRPARD022150": ****
>
> Session established with server AIX_PRD202A: AIX-RS/6000
>   Server Version 3, Release 1, Level 2.50
>   Server date/time: 2000-03-31 11:43:53  Last access: 2000-03-30 16:56:39
>
> Mode Function  Pattern (match from top down)
> ---- --------- -----------------------------
> Excl Directory #\...\ADSM\LOG
> Excl All       C:\WINNT\PROFILES\...\*
> Excl All       C:\WINNT\MEMORY.DMP
> Excl All       #\...\SPOOL\...\*
> Excl All       #\...\RECYCLER\...\*
> Excl All       #\...\SYSTEM32\CONFIG\...\*
> Excl All       #\...\SYSTEM32\CONFIG\*.*
> Excl All       #\...\PAGEFILE.SYS
> Excl All       #\...\EA DATA. SF
> Excl All       C:\TEMP\CACHE.IE\...\*
> Excl All       C:\TEMP\CACHE\...\*
> dsmc>

Steve Roder, University at Buffalo
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
ADSM Administrator
(tkssteve AT buffalo DOT edu | (716)645-3564 | 
http://ubvm.cc.buffalo.edu/~tkssteve)