>We are currently running TSM v4.1.3 on Aix v4.3.
>
>Our server stopped today, and I found the following messages:
>
>...ANR9999D asalloc.c(3269): Accessing invalid memory.
>
>Has anyone seen this before?   If so, what was the fix, other than going to
>v5.1, which we are currently testing.

Doing a search for the message at www.ibm.com shows it to be well known,
in TSM 3.7 and 4.1.  The APARs I browsed didn't say at what level it is
fixed (the 5.1 Readme file lists it as fixed therein), but you could
certainly go up to 4.1.5 within your version+release.  (The defect seems
to involve "volume selection".)  If it's infrequent, you could stay
status quo until v5 is ready to roll out in your shop.

  Richard Sims, BU