No, the client does not store archive info locally.
The table data shown by SELECT statements do not come directly from the
internal structures. The table data are virtual, constructed "on the fly"
when you run SELECT. Due to the nature of how SELECT works, we will not
claim that it is a high-speed query engine (also see
http://msgs.adsm.org/cgi-bin/get/adsm0411/387/1.html).
However, under the covers, the client/server interactions are optimized to
display the description info fairly quickly.
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
IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
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 01/04/2007
10:33:20 AM:
> Hi,
>
> Thanks for the replies. Just tested and it takes approx 20 minutes for
the
> SQL
> to complete (approx 5.2 million files).
>
> Workable, but I do not understand why the client just lists the archives
> directly.
> Maybe the archive info is also stored on the client side which makes is
> fast.
>
> Kind regards,
>
> Geert
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 04/01/2007
> 17:45:50:
>
> > On Jan 4, 2007, at 11:30 AM, Alexander Verkooijen wrote:
> >
> > > Hi,
> > >
> > > Something like this should provide a list of all archives:
> > >
> > > select node_name,description from archives group by
> > > node_name,description
> > >
> > > But like you said it will probably take a very long
> > > time to complete. ...
> >
> > Listing all Archives (or Backups) is a *very* expensive "fishing
> > expedition". If you *must* do this from the server (rather than more
> > efficiently, from the client), then try to limit it to subsets that
> > you really need, where taking advantage of Keyed columns should
> > substantially speed the query.
> >
> > Do select * from syscat.columns where TABNAME='ARCHIVES'
> >
> > to see the table column definitions, where columns having
> > INDEX_KEYSEQ entries are keyed, and render more efficient searches in
> > a Select.
> >
> > Richard Sims
|
