I got it to work as follows:
DSMCUTIL INSTALL /NAME:'ADSM Scheduler" /AUTOSTART:YES /PASSWORD:xxxxxxx

The name is what ever description you want the service to be called.
Password is the password you assigned in ADSM to this client.

This must be done from the baclient directory, on you client.  It
scanned the directory and installed in services, everything needed to
run the ADSM scheduler.   Hope this helps you.

>----------
>From:  Mike Garcia[SMTP:mike.garcia AT CONPAPERS DOT COM]
>Sent:  Tuesday, March 17, 1998 1:02 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: ADSM 3.1 Scheduler NT Service
>
>Hi I am also new to this environment and was waiting for an answer
>  so now that you answered  would someone tell me how to use the utility to
>  install the service for nt.
>        Thanks in Advance
>
>
>
>
>Greg.A.Garrison AT BANKAMERICA DOT COM on 03/17/98 02:50:19 PM
>
>Please respond to ADSM-L AT VM.MARIST DOT EDU
>
>To:   ADSM-L AT VM.MARIST DOT EDU
>cc:    (bcc: Mike Garcia/CPI)
>Subject:  Re: ADSM 3.1 Scheduler NT Service
>
>
>
>
>Larry,
>I went over this with an ADSM techie sometime ago.  You've got it right.
>The command line DSMCUTIL program is the only way to install the service
>under the new version.  :-(
>Sorry I don't have any insight on your second question.
>Good luck,
>Greg Garrison
>Bank of America
>
>
>
>
>"Kerssen, Larry" <Larry.Kerssen AT METROKC DOT GOV> on 03/16/98 04:51:40 PM
>Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>To:   ADSM-L AT VM.MARIST DOT EDU
>cc:    (bcc: Greg A. Garrison)
>Subject:  ADSM 3.1 Scheduler NT Service
>
>
>
>I just installed ADSM 3.1 Level 0.1 on an NT client.  I seem to remember
>in ADSM 2.0 that the installation provided a menu for installing the
>ADSM scheduler in NT services.  The new ADSM installation does not
>provide this option in the installation.  I had to use the Dsmcutil
>utility to install the service.  Is this the normal procedure for this
>version of the client software?
>Also, I am now wondering how I start the client Webshell,  from services
>or a startup script.
>