Del:
In the situation I described I am not able to enter a command. I reinstalled 
and the same thing occurs. However, there is now an entry on the NT program 
menu and if started that way the window is persistent and I am able to enter a 
command and have it execute.
So it does not persists if you fire the program from the install directory or a 
dos window, but does if started from the program menu.
Larry

>>> Del Hoobler <hoobler AT US.IBM DOT COM> 11/24/99 11:15AM >>>
Larry,

What happens when you enter an actual command?
For example:

sqldsmc /sqlqueryserver

You should see something like:
---------------------------------------------------------
D:\adsmv3\agentsql>sqldsmc /sqlqueryserver
D:\adsmv3\agentsql>sqldsmc /sqlqueryserver

Tivoli Storage Manager
Tivoli Data Protection for Microsoft SQL Server - Version 1, Release 1,
Level 2
(C) Copyright IBM Corporation 1997, 1999. All rights reserved.

TSM API Version 3, Release 7, Level 0
TSM Nodename: HOOBIE

License file exists and contains valid license data.

Available SQL servers:

HOOBIE - Service running
---------------------------------------------------------
By the way, "sqldsmc" (alone, with no parameters) just
By the way, "sqldsmc" (alone, with no parameters) just
displays the help.  It is NOT like the BA client.

The BA client goes into a prompt loop.
The SQL Agent is simply a batch command.

If you don't enter any parameters on the command line
it will display the help and quit. Is that what you are seeing?

By the way, if you are just getting started with
the agent, I recommend getting version 1.1.2.

Thanks,

Del

----------------------------------------------------
Del Hoobler
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com 


> Hi Del:
>
> Even when I open a dos prompt and exter an explicit string it behaves the
same way, e.g.
> d:\win32app\ibm\adsm\baclient\agentsql\sqldsmc.exe
> Version is 1.1.1
> API version  3.1.5