The HSM for Windows product is different than the product for HSM
for UNIX (Called HSM for Space Management). The UNIX product uses the HSM
settings in the management class. The HSM for Windows product uses the
settings in the archive copy group in the management class.

        What I would suggest here is that you first have the data migrate
to disk, and then use the migration delay setting in the storage pool to
have it remain on disk for a certain number of days before it is migrated
to a tape storage pool.
At 12:25 PM 3/27/2007 -0400, you wrote:

I have not sent anything to this list in quite some time, so please be
gentle if this topic has been thoroughly discussed in this forum before.
We are running TSM 5.3.4.0 on AIX, and recently purchased HSM to archive
from our Windows  2003 file servers.

In following the instructions to implement HSM we found that the
documentation pointed to settings on the management class for HSM.
However, once we implemented we found that those settings were not being
recognized, and data was going directly to tape as indicated by the
Archive settings.  We contacted support, and their response was that we
needed to use the Archive settings to point our HSM jobs to a storage
pool.  This doesn't seem right though, as we want files to initially go
to disk, then migrate to tape according to a last access date, not based
on a migration threshold on the storage pool.

Does anyone out there have a hint as to why we cannot use the HSM
settings?  Any help is much appreciated.

Dave Canan
TSM Performance
IBM Advanced Technical Support
ddcanan AT us.ibm DOT com