>Hell,
>   For some strange reason, LISTSERV has abended twice while processing
>reader files.  The LISTSERV console follows:
>
>u3 Mar 1989 13:56:45 Processing file (4496) from LISTSERV@UTDALVM1
>DMSITP143T Addressing exception occurred at 015B46 in system routine
>+ LSVCARDR; re-IPL CMS
>DMKDSP450W CP entered; disabled wait PSW '00020000 40F182A0'
>CP
>CONNECT= 07:11:46 VIRTCPU= 008:13.34 TOTCPU= 009:09.54
>LOGOFF AT 14:11:48 CST THURSDAY 03/23/89 BY SYSTEM
>
>We're running release 1.5o (FIX15O1).  Has anyone else had this problem?
>Any suggestions as to how to why it would be doing this?
>
> - David
 
I've spent many hours trying to solve this problem with LSVCARDR.  However,
the problem is NOT with Eric's LSVCARDR routine, but with DIAG14.  It seems
that when doing a loop of DIAG14s (which LISTSERV does), and a new reader
file pops in....Voila!  Problems!  We wound up have hundreds of files marked
inuse in LISTSERV's reader.  I think I can IPL in my sleep now :-)
I had recreated this problem a couple of months ago and did the ole tell IBM
deal.  We went to PUT 8805 with a couple of extra PTFs and the inuse problem
went away. *sigh*
 
But then, I started having other problems.  Our LISTSERV bombed like yours
did one Friday night.  I didn't come in and discover the problem until
Sunday.  There were hundreds of files in LISTSERV's reader.  I AUTOLOG'd
LISTSERV and it would not stay running for more than 1 minute without
bombing!  I substituted the LSVCARDR module for one that I had modified
to print out the condition/return codes (from DIAG14)  and the block number
it was reading.
 
Guess what?  LISTSERV quit ABENDing.  Although, I don't know why this made
a difference.  Occasionally, LISTSERV gets a 'reader busy' from DIAG14
and transfers the offending file to me.  I just transfer it right back
and everyone is happy.  I have left my 'debug' module in place and have
no intentions of removing it until IBM fixes their DIAG14 problems.
I haven't had time to recreate the problem standalone, but I will do
so soon.
 
The problem will usually hit you when the links come up and LISTSERV is
processing files while more are coming in.  Just be glad it has only
happened to you twice!  :-)
 
Darren
 
P.S. - We're running LISTSERV 1.5o (FIX15O1) on VM/SP HPO 5.0 PUT 8805+