Jan,

Remember, the Exchange Agent is NEVER getting control so
it cannot "pickup" this error.  The ADSM NT base client
scheduler is picking up this error (return code 128)
as you see it in the DSMSCHED.LOG.
If the RC=128 is not causing the schedule to fail then
I think you need to call IBM support to get this reported.
(The ADSM-L list is not the method to do this as you already know.)
I agree that the schedule should be marked "failure" not
"successful" if the "launch" of the "command" fails.

Del Hoobler
ADSM Agent Development

>> Del,
>> Thanks for the quick reply.
>> I will implement the change in registry MS recomments.
>>
>> But, I still find it verry peculiar that this error code was not picked up
>> by the ADSM agent. As a result of this the centralized ADSM follow-up does
>> think the back-up was successfull.
>> Is there a way to get those error codes to the ADSM host and the logging on
>> that host?
>>
>> Jan