RE: Maximum number of records reached for file

We'll probably get a monitoring tool when something blows up and costs us more 
money to fix than a monitoring tool would have cost. 

I remember one Good Thursday a few years ago when EDI went into message wait at 
5 pm.  We had Good Friday off and it one was one of those weekends when I just 
didn't get around to signing on from home to check things.  Came in Monday and 
the EDI job was still in message wait! So all the EDI and invoicing jobs for 
Friday, Saturday and Sunday were waiting in job queues.  A couple developers 
spent a good part of the week cleaning up files that got messed up because of 
this.

We've grown a lot since then, and if a similar scenario happened again, I'd bet 
we'd be buying a monitoring tool real fast.

Bryan 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Larry Bolhuis
Sent: Friday, October 20, 2006 9:30 AM
To: Midrange Systems Technical Discussion
Subject: Re: Maximum number of records reached for file


YES. Yes it can and I have seen it done.  You may want to increase the 
size no argument there but I wouldn't go *NOMAX. I would use a 
monitoring tool to watch QSYSOPR and then page someone.
 - L

Burns, Bryan wrote:

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