Phil,

>So taking note of your original advice to copy the latest versions of the API
files ADSMV3.DLL and >DSCAMENG.TXT to the SQL connect agent directory, I copied
them from the exchange connect agent (NOT >the ones from the latest ADSM Client
code - PTF3).

>Lo and behold, this has fixed all the problems with the SQL scheduler service.

The fix to the ADSM API for handling ADSM passwords in the NT registry did
not make it into PTF 3 but it is available as a fixtest on the ADSM FTP server.
Please look in directory: adsm/fixtest/v3r1/win32/intel/   for files
api313b.exe and api313b.txt  on
machine index.storsys.ibm.com.

The other option is to use the level of the API as distributed with the
Exchange Agent as you have done.

Sorry for the confusion.

Chris Zaremba
ADSM Agent Development