Thomas,

You're interpretation of the manual is correct. This is a problem in the
code, documented in APAR IC35203, with fixes targeted in for 5.1.6 and
5.2.0.

If you are running a client somewhere between 5.1.5.0 and 5.1.5.5, then
try the latest patch levels, as they should include the fix. This was
originally fixed in Windows patch level 5.1.5.6, and since patches are
cumulative (even for other platforms), it should be fixed in the latest
patch levels -- even if the README file doesn't mention them.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/22/2003 13:46
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Event status for scheduled command



The following is taken from Table 26 in the 5.1.5 "UNIX Backup-Archive
Clients
Installation and User's Guide":

For scheduled operations where the scheduled action is COMMAND, the return
code will be the return code from the command that was executed. If the
return
code is 0, the status of the scheduled operation will be Completed. If the
return code is nonzero, then the status will be Failed.

I executed the command "define clientact nodename act=comm
object=/usr/bin/false" for one of our 5.1.5 client systems. After the
command
was carried out a "query event" command reported a status of "Completed"
and a result of 1. What am I missing here? The documentation quoted above
seems to imply that the status should have been "Failed".