Hi Kuli;
Did I hear you right that you experienced this error for the first time with
the MVS V3 server??  Yikes, I've been struggling for 6 months trying to get
it solved (due to the 9G size of my DB and scheduling an outage which I
resolved using a Y2K duplicated system envrionment).  My understanding was
that it had been cause by a V1 entry, V2 had the permanent fix to overcome
future breaks, and I waited until I had V3 hoping the the performance would
be substantially better.  As I mentioned, I'm still trying to fix MY
problem, it's very disheartening to find that I might have another future
problem.  Ouch.

Dave Sanders
Sr. Technical Consultant
DSanders AT massmutual DOT com
MassMutual / The Blue Chip Company
1295 State St, E060, Springfield, MA 01111
413-744-5095




> -----Original Message-----
> From: Toora, Kuli [SMTP:kulbinder.toora AT EXCHANGE.MEB.CO DOT UK]
> Sent: Tuesday, December 08, 1998 8:49 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Reuse delay period.
>
> Season greetings,
>
> On Monday i came into the office and saw the following message on the ADSM
> server log :
>
> ANR0104E ASVOLUT(2202): Error 2 deleting row from table
> "AS.Volume.Assignment
> ANR0104E .
>
> ANR9999D AFMIGR(500): Error checking pending volumes for completion of
> reuse
>
> delay period.
>
>
> Our server runs on OS390 1.2 and our ADSM server level ,is at 3.1.1.3.
>
> I contacted IBM regarding this and found information regarding this error
> that was identified in version 1 and version 2.
>
> Here is the text from Dial IBM Support :
>
>
> IBM ADSM development discovered and corrected a minor server
> database problem in the ADSM Version 2 Server Level 0.0/0.0. The
> correction is included in the HSM refresh for the Version 2
> product, which displays a server level of "Level 0.2/0.2"
> or for the OS/2 and VM server at level "0.9/0.9".
> If you are running the "Level 0.0/0.0 or 0.9/0.9" server,
> you may encounter occasional error messages involving the
> AS.Volume.Assignment database object or the DF.MigrCandidates
> object during backup, migration, or reclamation
> The messages usually indicate an "Error 2" deleting updating,
> or inserting new information in the database for the
> AS.Volume.Assignment or DF.MigrCandidates object: msganr0104e
> ANR0104E astxn.c (898) Error 2 deleting row from table
> "AS.Volume.Assignment" or "DF.MigrCandidates"
>
> This problem not only affects users of ADSM V2 at levels below
> 0.2/0.2 it can also affect users migrating from and ADSM V1
> server to an ADSM V2 server.