TSM client schedule backup fails with RC=12 although backup is complete

Technote (troubleshooting)

Problem(Abstract)

A TSM client schedule may be reported as failed with a return code of 12, for example,
"ANS1512E Scheduled event 'DAILY_INCREMENTAL' failed. Return code = 12"
although the schedule backup does complete.

Cause

Working as designed

Resolving the problem

An example of a schedule backup showing as failed although its backup ran to completion would be :
03/29/2007 08:20:14 --- SCHEDULEREC QUERY BEGIN
03/29/2007 08:20:14 --- SCHEDULEREC QUERY END
03/29/2007 08:20:14 Next operation scheduled:
03/29/2007 08:20:14 ------------------------------------------------------------
03/29/2007 08:20:14 Schedule Name: DAILY_INCREMENTAL
03/29/2007 08:20:14 Action: Incremental
03/29/2007 08:20:14 Objects:
03/29/2007 08:20:14 Options:
03/29/2007 08:20:14 Server Window Start: 07:00:00 on 03/29/2007
03/29/2007 08:20:14 ------------------------------------------------------------
03/29/2007 08:20:14 Command will be executed in 1 hour and 53 minutes.
03/29/2007 10:13:14
Executing scheduled command now.
03/29/2007 10:13:15 Node Name: MYNODE
03/29/2007 10:13:15 Command will be retried in 5 minutes.
03/29/2007 10:18:15 Retrying scheduled event: DAILY_INCREMENTAL
03/29/2007 10:18:15 Node Name: MYNODE
03/29/2007 10:18:20 Session established with server TSMSERVER1: Windows
03/29/2007 10:18:20 Server Version 5, Release 4, Level 0.0
03/29/2007 10:18:20 Server date/time: 03/29/2007 10:18:17 Last access: 03/29/2007 08:20:12

03/29/2007 10:18:20 --- SCHEDULEREC OBJECT BEGIN DAILY_INCREMENTAL 03/29/2007 07:00:00
03/29/2007 10:18:20 Incremental backup of volume '\\MYNODE\c$'
03/29/2007 10:18:49 ANS1898I ***** Processed 500 files *****
...etc
03/29/2007 10:20:39 Successful incremental backup of '\\MYNODE\c$'

03/29/2007 10:20:42 --- SCHEDULEREC STATUS BEGIN
03/29/2007 10:20:42 Total number of objects inspected: 24,060
03/29/2007 10:20:42 Total number of objects backed up: 108
03/29/2007 10:20:42 Total number of objects updated: 0
03/29/2007 10:20:42 Total number of objects rebound: 0
03/29/2007 10:20:42 Total number of objects deleted: 0
03/29/2007 10:20:42 Total number of objects expired: 8
03/29/2007 10:20:42 Total number of objects failed: 0
03/29/2007 10:20:42 Total number of subfile objects: 0
03/29/2007 10:20:42 Total number of bytes transferred: 122.34 MB
03/29/2007 10:20:42 Data transfer time: 11.47 sec
03/29/2007 10:20:42 Network data transfer rate: 10,922.64 KB/sec
03/29/2007 10:20:42 Aggregate data transfer rate: 880.01 KB/sec
03/29/2007 10:20:42 Objects compressed by: 0%
03/29/2007 10:20:42 Subfile objects reduced by: 0%
03/29/2007 10:20:42 Elapsed processing time: 00:02:22
03/29/2007 10:20:42 --- SCHEDULEREC STATUS END
03/29/2007 10:20:42 --- SCHEDULEREC OBJECT END DAILY_INCREMENTAL 03/29/2007 07:00:00
03/29/2007 10:20:42 ANS1512E Scheduled event 'DAILY_INCREMENTAL' failed. Return code = 12.
03/29/2007 10:20:42 Sending results for scheduled event 'DAILY_INCREMENTAL'.
03/29/2007 10:20:42 Results sent to server for scheduled event 'DAILY_INCREMENTAL'.
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 Could not establish a TCP/IP connection with address 'a.b.c.d:1500'. The TCP/IP error is 'Unknown error' (errno = 10065).
03/29/2007 10:13:15 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -50.
03/29/2007 10:20:42 ANS1512E Scheduled event 'DAILY_INCREMENTAL' failed. Return code = 12.
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 ANSXXXXE 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 schedule 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 not be reported as failed anymore in above example.

Source:

IBM Web
http://www-01.ibm.com/support/docview.wss?uid=swg21258418