Mark,

Whoops.  Here is a minor update to the batch file
to run from the SQL Scheduler.
See the changes denoted by ">>>>>" in front.
The environment variables should be DSMI_DIR and DSMI_CONFIG
(not DSM_DIR and DSM_CONFIG.)

==============================================================


Mark,

I just tried your exact scenario...
If you are going to use the scheduler from
SQL Enterprise Manager, you should schedule a batch file to do your
backup as opposed to scheduling the actual command itself.
So, create a batch file that runs the sqldsmc command and then
create a scheduled task that calls the batch file. Here is the
batch file that I used to backup "PUBS" successfully:
(Call it SQLPUBS.BAT, for example:)
=======================================================
SET DSM_DIR=
>>>>> SET DSMI_DIR=
SET DSM_CONFIG=
>>>>> SET DSMI_CONFIG=
E:
CD \WIN32APP\IBM\ADSM\AGENTSQL
SQLDSMC /BACKUPFULL:PUBS /LOGFILE:SQLDSM.LOG /ADSMOPTFILE:DSM.OPT
==============================================
(Note that the entries after DSM_DIR and
DSM_CONFIG are blank)

Then, under the "Command:" for the Task:

    E:\WIN32APP\IBM\ADSM\AGENTSQL\SQLPUBS.BAT

I hope this helps.
Let me know if it doesn't.

Del Hoobler
ADSM Agent Development
IBM Corporation

>>
>>         Thanks again for your help!

>> Mark L. Evans
>> MEvans AT co.slc.ut DOT us
>> Network Administrator
>> Salt Lake County Information Services