On Fri, 10 Dec 1999, Steven P Roder wrote:
>
> > >12/10/99 08:31:31 ANR0102E asalloc.c(4138): Error 1 inserting row in table
> > >"AS.Segments".
> >
> > Customers in the past surmised that this may be precipitated by a shortage 
> > of
> > space in the *SM database.  You may have to do an Auditdb offline, or
> > an AUDit DB online.

Hi all,

     Hi,

     I looked back thru my emails to the Tucson Developers, as I
seemed to recall running into this before, and sure enough, I did,
back in June.  In both cases of this error, the currently open
copypool volume, upon being reclaimed, rather than going "pending",
was reported as "empty".  It never went into scratch status, but
rather, was reused, and marked as "STGREUSE" in the volhistory
file.  To resolve this problem, I marked the "STGREUSE" volume
acc=reado, and I was then able to write to the copypool again.
I then ran move data against the R/O volume, making sure it went to
scratch status.

I am trying to get the support center to open an APAR on this.

Steve (unVMix Systems Programmer/Dude) Roder
(tkssteve AT ubvm.cc.buffalo DOT edu | tkssteve AT acsu.buffalo DOT edu | 
(716)645-3564 ,
   | http://ubvm.cc.buffalo.edu/~tkssteve)