Hi,

I would assume that the 64-bit client is faster, smaller, better
(otherwise why create a 64-bit client) and as almost all of my systems
are 64-bit, that is the client that is loaded on them.  To me, running a
32-bit client on a 64-bit OS/Hardware is like running the 32-bit version
of Oracle on a 64-bit OS/Hardware (ie. It is gimping yourself some).
Also the future (whether IBM likes to admit it or not) is 64-bit
computing (Alpha's have been there for 10 years now..).  

By only supporting the 32-bit client, it seems that IBM is saying that
we kind of support your bare metal solution.  I was just wondering if
anyone has seen any kind of timetable regarding changes to this feature.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David E Ehresman
Sent: Thursday, January 29, 2004 10:49 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Sysback and 32-bit client

Why does the 32-bit TSM api prevent you from using the feature?  the
32-bit api does run on 64 bit machines and will work with servers
running in 64 bit mode.

David

>>> Michael.Wheelock AT INTEGRIS-HEALTH DOT COM 1/29/2004 11:13:28 AM >>>
Hi,

We use sysback as our bare metal solution for our AIX servers.
Currently we are forced to use the sysback remote server utilities
instead of the TSM integration feature as it only supports the 32-bit
TSM api. Does anyone know what IBM's plans for changing this requirement
are?  The solution isn't horrible currently, but could I would really
like to take advantage of some of the expiration features, etc in TSM.


Michael


This e-mail may contain identifiable health information that is subject
to protection under state and federal law. This information is intended
to be for the use of the individual named above. If you are not the
intended recipient, be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited and may be
punishable by law. If you have received this electronic transmission in
error, please notify us immediately by electronic mail (reply).

This e-mail may contain identifiable health information that is subject to 
protection 
under state and federal law. This information is intended to be for the use of 
the 
individual named above. If you are not the intended recipient, be aware that 
any 
disclosure, copying, distribution or use of the contents of this information is 
prohibited 
and may be punishable by law. If you have received this electronic transmission 
in 
error, please notify us immediately by electronic mail (reply).