I can see how that might be misleading, but the Windows client manual
information is in the context of the Windows OS, and not necessarily that
of other operating systems (Unix, NetWare, etc.). If you look in the
corresponding manual for the other OSes, you'll see that
RESOURCEUTILIZATION appears there, too. I don't know which PDF files you
are looking at, but I verified that it goes back at least as far as the
version 4.2 books (oldest manual version I have readily available) for
Mac, Unix, and NetWare.
RESOURCEUTILIZATION is not available in the API because that option is
used to funnel data at the file level, and the TSM API does not perform
any file I/O. It would be up to the vendor of an API application to
implement their own RESOURCEUTILIZATION-like functionality in their
application.
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-01-24
11:46:56:
> Found in the Windows version of "Backup Archive Clients Installation and
> User's Guide.pdf", v5.2, page 329, RESOURceutilizaion value...
>
> Supported Clients
> This option is valid for all Windows clients. The server can also define
> this option. The Tivoli Storage Manager client API does not support this
> option.
>
> I read that as it is only valid in Windows clients, especially since the
> base API doesn't support the value... Do I interpret this incorrectly?
> I also find no mention of the option in any of the AIX client pdfs that
> I have around.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Andrew Raibeck
> Sent: Monday, January 24, 2005 12:31 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] resourceutilization
>
> Nothing has changed. When this option was introduced, it was (and still
> is) available for all clients.
>
> 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-01-24
> 11:13:46:
>
> > I thought resourceutilization was a Windows Client option only.. Did
> > that change?
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> > Of Joni Moyer
> > Sent: Monday, January 24, 2005 11:59 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: [ADSM-L] resourceutilization
> >
> > Hello All!
> >
> > I have a Solaris client at the 5.2.2.0 TSM client level and the user
> > would like to know how to stream a single archive that sends multiple
> > files to the TSM server through 1 session instead of multiple
> sessions.
> > I have the MAXNUMMP set to 2 for this client and I have looked at the
> > dsm.sys file and there is no resourceutilization parameter within the
> > file, so I believe it is using the default. I couldn't find the value
>
> > for the default of the number of sessions a client can start on the
> > TSM server, which in my case is an AIX 5.2.2.5 server. Here is the
> > user's
> > question: "If I issue an archive with multiple files TSM starts
> > multiple sessions - one for each file. Do we have a approach to limit
>
> > the number of sessions?" Any suggestions/help would be appreciated.
> > Also, when issuing an archive, is it possible to override the dsm.sys
> > file and specify the resourceutilization for that archive at the time
> > it is issue? Thanks again!
> >
> > ********************************
> > Joni Moyer
> > Highmark
> > Storage Systems
> > Work:(717)302-6603
> > Fax:(717)302-5974
> > joni.moyer AT highmark DOT com
> > ********************************
|
