Uhmmm guess you didn't have your volumes mirrored via tsm...
if you only had one volume, did your operating system show any errors logged
to it ?
pretty much I'd say you are not going to get out of that one.
could be a good case to justify the cost of additional dasd to mirror your
DB & LOG for tsm.
dwight
-----Original Message-----
From: Hunley, Ike [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 20, 2001 2:52 PM
To: [EMAIL PROTECTED]
Subject: Re: ADSM 4.1.2 ANR9999D error
Oh DRAT! The error was in a picture file! Soooorry!
Right now we're formatting new database files on new DASD. Any other tips
or hints out there?
ANR0252E Error writing logical page 20424758 (physical page 290102) to
database
ANR0252E volume SYS2.ADSME.DBV47.
ANR9999D ERROR WRITING TO DATABASE LOGICAL VOLUME.
.DSM server terminating operation - internal error BUF087 detected.
ADSME abending: SIGNAL_ERROR code 0000012D called from location 1772F044
CPU 0 General Registers at Entry to Abend:
-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 20, 2001 3:16 PM
To: [EMAIL PROTECTED]
Subject: Re: ADSM 4.1.2 ANR9999D error
What error? There is nothing attached to your post on ADSM-L...
-----Original Message-----
From: Hunley, Ike [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 20, 2001 2:52 PM
To: [EMAIL PROTECTED]
Subject: ADSM 4.1.2 ANR9999D error
> -----Original Message-----
> From: Hunley, Ike
> Sent: Friday, July 20, 2001 11:33 AM
> To: [EMAIL PROTECTED]
> Subject: FW:
>
> I forgot to include that we're running OS/390 2.9...
>
> Hi, Has anyone out there seen this error? IBM says that in 3.7 this was
> caused by a ADSM code problem. We running TSM 4.1.2.
>
> Thanks in advance for your help.
>
> -----Original Message-----
> From: Peppers, Holly
> Sent: Friday, July 20, 2001 11:12 AM
> To: Hunley, Ike
> Subject:
>
>
> <<...OLE_Obj...>>
>
>
>
> Holly L. Peppers
> 58481
> Technical Services
>
>
>
>
>
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect the
views of Blue Cross Blue Shield of Florida, Inc.
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and
affiliate companies are not responsible for errors or omissions in this
e-mail message. Any personal comments made in this e-mail do not reflect the
views of Blue Cross Blue Shield of Florida, Inc.
