The fix is in level 13, which has not made its way
out of testing.
 The reason you haven't heard from IBM previously is
that you haven't contacted service.  Posting to this list is not
the same as calling IBM service.  Some of the developers
and service people monitor this list as time permits,
but there are no guarantees of response from this list.
For that, you must contact IBM support.
 For the temporary fix, you must also contact IBM service.

Barry Fruchtman
ADSM Development

On Fri, 4 Jul 1997, Henk ten Have wrote:

> OK, one more time, forget my last email (it's been busy, end of the
> week, etc. etc., fighting with database searches, looking for the
> wrong APAR, AIX 3.2 instead of AIX 4.X, mea culpa):
>
> a week ago, I wrote:
>
> >one of my backup/archive clients has some problems with the server
> >(client 2.1.0.6, server 2.1.0.12, both AIX 4.1.4.0):
>  [skip]
> >06/27/97   21:35:01  ANR9999D asalloc.c(664): Input mount point present.
>  [skip]
> >Anyone any suggestion?
>
> Unfortunately nobody gave me any suggestion, not to mention a solution.
>
> Searching in the CLOSED APAR's database, I found:
>
> IX67438: INCREMENTAL BACKUP OF <HSM> MIGRATED FILESYSTEMS FAILS.
>
> ORIGINATING DETAILS:
> ANR9999D asalloc.c(653):Input mount point present
> An incremental backup of a space-managed filesystem fails.
> This problem only occurs when the backup is going to removeable media.
>  [skip]
> * RECOMMENDATION:                                              *
> Apply PTF when available.
> Incremental backup of <HSM> migrated filesystem fails with
> "ANR9999D asalloc.c(653):Input mount point present." when
> backing up a filesystem that contains both <HSM> migrated
> and resident data.
>  [skip]
> TEMPORARY FIX:
> A temporary fix has been sent to two customers, and it has
> corrected the problem for them.
>  [skip]
> Status:         CLOSED  PER
>  [skip]
> Submitted:      97/04/02
> Closed:         97/04/02
>  [skip]
> The fix for this APAR was not found in database.
>
> My error is asalloc.c(664) instead of asalloc.c(653), but isn't it
> the same problem?
>
> And why is there no fix available? (Problem is submitted 97/04/02 and
> closed 97/04/02).
>
> And why is nobody (from IBM) telling me what I can do about this problem?
>
> Questions, questions, questions.
>
> Regards,
>
> Henk ten Have                   SARA, Academic Computing Services Amsterdam
> Systems Programmer              Kruislaan 415
> E-mail: hthta AT sara DOT nl           1098 SJ Amsterdam
> Phone : +31205923000            The Netherlands
>