Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Ang\:\s+Re\:\s+\[ADSM\-L\]\s+Help\s+tracking\s+down\s+spurious\s+\"Failed\s+12\"\s+errors\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious "Failed 12" errors (score: 1)
Author: Daniel Sparrman <daniel.sparrman AT EXIST DOT SE>
Date: Wed, 17 Aug 2011 12:06:29 +0200
"Failed 12" is a common error when TSM failed backuping a few files. Usual reasons are the file is locked, the file was removed during backup and the account running the TSM scheduler did not have ac
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-08/msg00078.html (15,108 bytes)

2. Re: [ADSM-L] Ang: Re: [ADSM-L] Help tracking down spurious "Failed 12" errors (score: 1)
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Wed, 17 Aug 2011 08:10:46 -0400
In the cases you mention, I would expect the return code to be 4, not 12, provided that there are no other warnings or errors that would cause a higher return code. RC 4 is very specific: except for
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2011-08/msg00080.html (17,649 bytes)


This search system is powered by Namazu