Thanks Andy,

They (Novell/Netware client) use the command line for some reason we haven't 
been able get  the Web client graphical interface via a web browser to work on 
Novell Netware as I recall.


-----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:16 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Archiving problem

I hit "send" too soon, what the heck is "graphical browser"? I meant
accessing the Web client graphical interface via a web browser.

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
21:10:32:

> From: Andrew Raibeck/Hartford/IBM@IBMUS
> To: ADSM-L AT vm.marist DOT edu
> Date: 2011-07-20 21:13
> Subject: Re: Archiving problem
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> 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.
> >
> >
> >