The problem to which you refer, APAR IC31844, is indeed fixed in 4.2.1.15
(and up).

If you are running 4.2.1.15 and are encountering "return code = 4", there
is some other reason. Check your dsmsched.log and dsmerror.log files to
see if there is some explanation therein. For example, if you have DOMAIN
C: E: F: but there is no E: drive, then that could cause the rc 4. That
isn't the only reason, just an example.

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.ibm DOT com

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




Guillaume Gilbert <guillaume.gilbert AT DESJARDINS DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/09/2002 13:59
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Return code=4 on scheduled backap



Hello

We just installed a 4.2.1.15 client on an NT box and now we get the bug in
the event reporting :

2002-01-08 17:31:06 --- SCHEDULEREC STATUS END
2002-01-08 17:31:06 --- SCHEDULEREC OBJECT END FEN_QUOT 2002-01-08
17:00:00
2002-01-08 17:31:06 ANS1512E Scheduled event 'FEN_QUOT' failed.  Return
code = 4.

which reports to the server that the schedule has failed.

I searched adsm.org and this bug was supposed to be fixed in 4.2.1.15 but
it clearly isn't. Is there a workaound to this bug or do I have to live
with it until it is fixed?

The server is at 4.1.3 on AIX 4.3.3

Thanks for the help

Guillaume Gilbert
Storage administrator
CGI Group Montreal