i called in a PRM on this and they solved it at level 1.

this node was an upgrade from a 3.1 client and then i guess
HSM was built into the b/a client.

anyways, when i removed /etc/adsm/SpaceMan everything was very happy.

John

On Tue, May 16, 2000 at 02:08:11PM +0200, Isabel Gerhardt wrote:
> We are not using HSM either nor do we intend to...
>
> So am I required to install the HSM package now? It wasn't mentioned in the 
> README
> (only API)
>
> Regards,
> Isabel
>
> Isabel Gerhardt
> URZ
> FernUniversitaet Hagen
> 58084 Hagen
> Germany
>
>
> John St. Martin schrieb:
>
> > i've been seeing the same error and saw that it was related HSM after
> > i checked the messages docs.
> >
> > i guess the question is, why does the solaris client think it needs
> > HSM support?  i'm not using this option.
> >
> > John
> >
> > On Mon, May 15, 2000 at 01:29:32PM +0200, Boris Feldman (Udi) wrote:
> > > ANS9505E program-name: cannot initialize DM services.
> > > Reason: error
> > > Explanation: TSM space management cannot initialize
> > > the DM services.
> > > System Action: TSM cannot start space management
> > > support.
> > > User Response: Correct error and retry operation.
> > > Make sure that DM services have been installed on the
> > > system (Hierarchical Storage Management Support).