RE: Maximum number of records reached for file

<VENDOR ON>
Centerfield has a disk/HUNTER product that can serve as insure policy for
these kind of unexpected DASD spikes.  With it on, you will know when, what
and who done it (i.e. via email).  Even if it's an OS issue with internal OS
objects.
<VENDOR OFF>

Elvis

-----Original Message-----
Subject: Re: Maximum number of records reached for file 

I have set several files at *NOMAX and we do have runway jobs that wipe out 
our disk space, which is similar to yours in size.  We are on modified 
BPCS. Consider some program that does something, then prints an audit 
trail.  Consider some bug or data base corruption that causes the program 
to go into a loop.  What bombs us is when the report reaches 999,999,999 
pages.  With a high speed computer, it does not take long to get there.

I have modified a report so that when it fills up, it splits the output and 
starts another.  I have a DSPLOG CL that captures all instances of a file 
getting larger, then I periodically review that to see if some of those 
files need to be resized.  Also, after major reorg removal of ancient 
records, I review some of the files involved, to see if it makes sense to 
downsize how much disk space they are eating, saving the upsize growth 
provisions.

I don't have the time to prevent every surprise.  I focus on those that 
reoccur frequently.  I would consider your problem ... twice in one year, 
to be a small irritant.  A more common irritant for me is some job getting 
stuck in JOBQ holding up a parade, or access sluggishness, and by the time 
it lets me in, there is no evidence as to what caused that.

I can access our 400 from the office and from home.  Before I go beddybye, 
I often check on our system to see if anything hung.  Ditto when I wake 
up.  Thus, for every one problem that inconveniences the mass of users, 
there are 100 problems that I intercepted and repaired before they even 
found out that there was a problem.

How can I avoid CPA4072 messages (Maximum number of records reached for 
file XXXXX) from being issued for MAPICS reports after hours and 
preventing backups and MRP from running?  This occurred once in May and 
again last night.  In May, it was the AMI2TRP file, last night it was the 
AMQ2MRP file.


I could increase the MAXRCDS in the MAPICS printer overrides, but we have 
over 1,000 overrides.  I think the default is set way too low. I'm 
thinking I should have a system reply list entry answer with  *NOMAX.   In 
today's day and age, can a runaway spooled file job eat up all the 200 Gb 
of free DASD we have?

Thanks,

Bryan Burns
M.I.S. Department
ECHO, Incorporated