Hi Scott,

> I have frequently done a "halt"
> on the ADSM (TSM) server when it's
> busy.  it
> always comes back up, no problem, and picks up where it left off.
> So what is the concern?

The concern?
with HALT simply typed in at any time you are not using the tool
as designed. Thus there may not, but can arise problems
when doing so.

Few lines from *SM administrators reference:


Use the HALT command only after all administrative and client node sessions
are com-pleted
or canceled. To shut down the server without severely impacting
administrative
and client node sessions, perform the following steps:
1. Use the DISABLE SESSIONS command to prevent starting new client node
ses-sions.
2. Use the QUERY SESSIONS command to identify any existing administrative
and
client node sessions.
3. Notify any existing administrative and client node sessions that you plan
to shut
down the server (you must do this outside of ADSM).
4. Use the CANCEL SESSIONS command to cancel any existing administrative or
client node sessions.
5. Issue the HALT command to shut down the server and stop any
administrative and
client node sessions.

Yours is the decision whether you about documentation or not,
so is your win, so is yor risk.

Juraj Salak
sal AT keba.co DOT at


Regard