Hi Timothy,

You are referring to the "q ar" command? That would be TSM client only. The
TSM server does not understand the TSM client commands.

As I mentioned, you can also try the Web Client GUI to navigate the
archives for that file system. Another alternative is to see what's
available on the TSM server with the following TSM server administrative
command:

select node_name from filespaces where filespace_name='DOCHUB\RESTORE:'

This will help confirm you are accessing the file space with the right node
name.

Once you have confirmed the node name, you can use this TSM server
administrative command to see if any archive objects exist in that file
space:

select count(*) from archives where filespace_name='DOCHUB\RESTORE:' and
node_name='DOCHUB'

If the count is more than 0, I would expect there to be archived objects
that file space. If you want to see the object names, use:

select * from archives where filespace_name='DOCHUB\RESTORE:' and
node_name='DOCHUB'

Notes on the above "select" statements:

- Each of the "select" statements is a single command, but the ADSM-L list
server might format them into two or more lines.

- Values between single quotes must be in upper case, as illustrated

- In the second and third "select" statement I am guessing a node name of
DOCHUB. However, the first "select" statement will confirm the node name.
Be sure to substitute the correct node name (again, in upper case).

Best regards,

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

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-07-21
07:58:20:

> From: "Hughes, Timothy" <Timothy.Hughes AT OIT.STATE.NJ DOT US>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2011-07-21 08:09
> Subject: Re: Archiving problem
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Thanks Andy ...should that command be client side? Or can I try it
> on the TSM Server?
>
>
> Best regards
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Andrew Raibeck
> Sent: Wednesday, July 20, 2011 9:11 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Archiving problem
>
> How about:
>
> q ar dochub\restore:* -subdir=yes
>
> If that doesn't work, try configuring the web client on the NetWare
> machine, then you can use the graphical browser to verify that there
> objects at all under that file space.
>
> Best regards,
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Product Development
> Level 3 Team Lead
> Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
> Tivoli_Storage_Manager
>
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2011-07-20
> 18:33:57:
>
> > From: "Hughes, Timothy" <Timothy.Hughes AT OIT.STATE.NJ DOT US>
> > To: ADSM-L AT vm.marist DOT edu
> > Date: 2011-07-20 18:35
> > Subject: Re: Archiving problem
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> >
> > Since we are on the subject of Archive how do you check the size of a
> Archive?
> >
> > Fileset ADOCGWS_10-30-2009
> >
> >
> > The following was tried
> >
> > q filespace
> >
> > reports dochub\restore:
> >
> > q ar dochub\restore:
> > q ar dochub\restore:  (tried appending /, \, /*, \*) same results
> >
> > Then tried q ar -subdir=yes dochub\restore:
> >
> > Same results, no files have previously been archived for "dochub
> \restore:"
> >
> >
> > Thanks
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > Behalf Of Prather, Wanda
> > Sent: Wednesday, July 20, 2011 1:49 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Archiving problem
> >
> > Responses at bottom:
> > =======================================================================
> > I have a client system administrator attempting to archive files
> > with a command like:
> >
> > dsmc archive '/CMS/oldpatients/039*' -subdir=y -archmc=ro_patient \
> > -description='Xio 4.51 07/19/2011 ND'
> >
> > Files that are in oldpatients and have names starting with '039' get
> > archived. In cases where a subdirectory of oldpatients has a name
> > starting with '039' and contains one file, the subdirectory and the
> > one file get archived. In cases where a subdirectory of oldpatients
> > has a name starting with '039' and contains multiple files and
> > further levels of subdirectories, neither the subdirectory nor any
> > of its descendents get archived.
> >
> > The system uses TSM 5.3.4.0 client code under Linux with a 2.6.9-42
> > kernel (probably RHEL 4).
> >
> > Is the client supposed to behave this way? If not, is a more current
> > client code level likely to help?
> > ======================================================================
> > If I understand your problem correctly, yes this is correct client
> > behavior, and works the same in all subsequent client levels.
> >
> > This has always been a common trap, because if you look up
> > "wildcard" in the client book, the first reference to it says "* is
> > the match-all character".  But if you keep reading, a later
> > reference to "wildcard" says:  "In a command, wildcard characters
> > can only be used in the file name or extension. They cannot be used
> > to specify destination files, file systems, or directories".  So *
> > is not a wildcard for matching directory names.
> >
> >
> >