Resolving the problemAn example of a schedule backup showing as failed although

its backup ran to completion would be :

03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 08:20:14
03/29/2007 10:13:14
Executing scheduled
03/29/2007 10:13:15
03/29/2007 10:13:15
03/29/2007 10:18:15
03/29/2007 10:18:15
03/29/2007 10:18:20
03/29/2007 10:18:20
03/29/2007 10:18:20
7 08:20:12

--- SCHEDULEREC QUERY BEGIN

--- SCHEDULEREC QUERY END
Next operation scheduled:
-----------------------------------------------------------Schedule Name: DAILY_INCREMENTAL
Action: Incremental
Objects:
Options:
Server Window Start: 07:00:00 on 03/29/2007
-----------------------------------------------------------Command will be executed in 1 hour and 53 minutes.
command now.
Node Name: MYNODE
Command will be retried in 5 minutes.
Retrying scheduled event: DAILY_INCREMENTAL
Node Name: MYNODE
Session established with server TSMSERVER1: Windows
Server Version 5, Release 4, Level 0.0
Server date/time: 03/29/2007 10:18:17 Last access: 03/29/200

03/29/2007
:00:00
03/29/2007
03/29/2007
...etc
03/29/2007

10:18:20 --- SCHEDULEREC OBJECT BEGIN DAILY_INCREMENTAL 03/29/2007 07

03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
03/29/2007
0:00
03/29/2007
code = 12.
03/29/2007
03/29/2007
L'.

10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42
10:20:42

10:18:20 Incremental backup of volume '\\MYNODE\c$'

10:18:49 ANS1898I ***** Processed 500 files *****
10:20:39 Successful incremental backup of '\\MYNODE\c$'
--- SCHEDULEREC STATUS BEGIN
Total number of objects inspected: 24,060
Total number of objects backed up: 108
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 8
Total number of objects failed: 0
Total number of subfile objects: 0
Total number of bytes transferred: 122.34 MB
Data transfer time: 11.47 sec
Network data transfer rate: 10,922.64 KB/sec
Aggregate data transfer rate: 880.01 KB/sec
Objects compressed by: 0%
Subfile objects reduced by: 0%
Elapsed processing time: 00:02:22
--- SCHEDULEREC STATUS END
--- SCHEDULEREC OBJECT END DAILY_INCREMENTAL 03/29/2007 07:0

10:20:42 ANS1512E Scheduled event 'DAILY_INCREMENTAL' failed. Return

10:20:42 Sending results for scheduled event 'DAILY_INCREMENTAL'.
10:20:42 Results sent to server for scheduled event 'DAILY_INCREMENTA

Although the dsmsched.log shows no error, in the above example, there is a retry
on the network. This is evidenced by the following messages :

03/29/2007 10:13:15 Command will be retried in 5 minutes.

03/29/2007 10:18:15 Retrying scheduled event: DAILY_INCREMENTAL
The dsmerror.log will show corresponding messages. Specifically,
03/29/2007 10:13:15 ANS5216E
s 'a.b.c.d:1500'. The TCP/IP
03/29/2007 10:13:15 ANS4039E
client agent. The TSM return
03/29/2007 10:20:42 ANS1512E
code = 12.

Could not establish a TCP/IP connection with addres

error is 'Unknown error' (errno = 10065).
Could not establish a session with a TSM server or
code is -50.
Scheduled event 'DAILY_INCREMENTAL' failed. Return

What the above shows is that the schedule backups failed because of the ANS5216E
and ANS4039E errors. Both these messages were added at TSM 5.3 level. Prior to
TSM 5.3, those messages were logged in the dsmerror.log file without any ANSXXXX
E message and the schedule completed successfully. The new ANS5216E and ANS4039E
messages cause the global return code to be set to 12, which causes the schedul
e backup to show as fail, even though the client was able to actually connect to
the server on retry and do its backup.
This is working as designed.
In this case, the network should be examined. The ANS5216E and ANS4039E messages
indicate that the client was unable to connect to the server at that time. The
errno=10065 is an error returned by Windows which means :
WSAEHOSTUNREACH
10065 No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH
Once the ANS5216E and ANS4039E messages are resolved, the client schedule will n
ot be reported as failed anymore in above example.