Well, you could use some external tool to process the output from QUERY
ASSOCIATIONS pretty easily, or so I would think.

The following SELECT might also be useful:

select domain_name, schedule_name
   from client_schedules
   where domain_name || ' ' || schedule_name not in
      (select distinct domain_name || ' ' || schedule_name
         from associations)

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-03-01
21:52:34:

> Hi Andy
>
> [...]
> > associated nodes, then there are no associations for that schedule.
But
> > maybe the original developers of the QUERY ASSOCIATION command thought
it
> > would be useful to show you which schedules had no associations.
> [...]
>
> That was exacly the reason, why I noticed the difference: I was looking
> for a (fast) select statement, which shows defined schedules which
> are not associated with any node (maybe simply forgotten or maybe
> on purpose, e.g. to assocate them later).
> So it seems I have to use a (slightly?) more complex statement.
>
> Thanks for your answer,
>
> Andreas