ADSML replied, in part..
> 1) Well, to play satan's adovcate, if it could somehow magically detect
> which server you wanted it to go to, then maybe I could agree with this.

A reasonable default would be the TCPSERVERADDRESS in the
options file. I'm blissfully ignorant of other communication methods.

I can tailor that for my local distributions.  Even without that, filling the
entries in on a form, with defaults pre-entered or otherwise available
on screen, presented with the rest of the GUI install would be far
superior to the ugly, error-prone, *must* read the doc, command line
method in current package.

I'd even consider writing a simple thing if I knew how to get it into the
install package and invoked, but to do an excellent job of this is not
trivial and beyond what I have time and talents for.  There is a local
readme file ability in the WinNT installer ... can I also write this
scheduler install bit myself with the materials available?

> 2) Agreed, but you can always attempt using other facility to log the info.

I don't understand this suggestion.

> Or use cmd line.

See above for my  feelings on the general populace using command
line stuff.  When called in to diagnose a problem, I want the
information there.  I don't want to have to dream up some command
and communicate it, often over the phone, to do another backup.

In either the backup or restore case, the DSMSCHED.LOG (or
whatever) output is one more verification of what I wanted done, not
what the Backup Client *though* I wanted.

> 3) IBM doing Windows, like Microsoft doing Mainframe, any suprises?

Ever the optimist, I guess :-)

Thanks for the discussion,

Wayne T. Smith                          ADSM AT Maine DOT edu
ADSM Technical Coordinator - UNET       University of Maine System