As far as I am aware the bug was introduced around 12.0(13.6)S, and
has not been fixed in any releases so far.
BugTrack ID?
Sure, but things have changed since the above was written. :-)
It is fixed in 12.0(15)S2 -- the BugID is CSCdt56314.
Cheers,
Rob
