I don't know, but I've seen a similar situation when auditing a volume where all the files were bad without setting quiet=yes. It got flooded and stopped recording. I halted and restarted the server. I have since started using the dsmulog utility to reduce this exposure.
Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 7:29 AM To: [EMAIL PROTECTED] Subject: Activity Log not recording Can anyone tell me why my activity log has stopped recording. Best I can tell is that it was flooded with ANR8216W Error sending data on socket 59. Reason 32. which I believe is from the web interface (which was probably me). This happened last night and nothing has been recorded in the activity log since. I have lots of room in my database and lots of room in my recovery log. I decreased the activity log retention and still it is not recording. Documentation says it will start recording once there is space in the database and/or recovery log. Any ideas would be appreciated. Thank you, Diana
