Jim is correct that you are missing the management class name on the DIRMC
option.

I wanted to add, however, that you still may not see any volumes being
created in your dirdiskpool because unless they have extended ACLs or
exceptionally long path names, directory objects are stored exclusively in
the TSM database.

I believe there have been previous threads discussing at what point
directory object data starts spilling over into the storage pools.

At 08:19 AM 4/30/02 -0400, you wrote:
>Jim,
>     if I'm reading everyhing right your option override should read: dirmc
>dirmc
>dirmc is the option you're setting and you want to point it to management
>class dirmc
>
>
>
>
>"Jim Kirkman" <jmk AT EMAIL.UNC DOT EDU>@VM.MARIST.EDU> on 04/29/2002 03:36:32 
>PM
>
>Please respond to jim_kirkman AT unc DOT edu
>
>Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>To:   ADSM-L AT VM.MARIST DOT EDU
>cc:
>
>Subject:  dirmc question
>
>
>I want to implement the dirmc scheme. I've created a disk pool (and have
>read all about the seq pool with device=file) dirdiskpool, a management
>class dirmc with a backup copy group pointing to the dirdiskpool, a
>client option dirmc that is part of a client option set called, you got
>it, dirmc.  I've associated some clients with said option set but I've
>no evidence of folders in the disk pool. I'm wondering if I've got the
>option set correctly, although the query looks good....
>
>                     Optionset: DIRMC
>                          Option: DIRMC
>Sequence number: 0
>       Override: No
>   Option Value: dirmc
>
>any help appreciated
>
>
>
>--
>Jim Kirkman
>AIS - Systems
>UNC-Chapel Hill
>966-5884
>
>
Scott McCambly
AIX/NetView/ADSM Specialist - Unopsys Inc.  Ottawa, Ontario, Canada
(613)799-9269