RE: Max Records in Physical or Printer Files - To Max or Not To Max...

I've had this occur on vendor software used in production. When I worked
with Infinium Software, I once let an upgrade process run overnight (I know
better now); it was a lengthy update. Imagine my surprise the next morning
when the AS/400 was *OFF. An IPL and a joblog later, we found the culprit.
Turns out this was a known bug in this particular upgrade.

Loyd

-----Original Message-----
From: Julio Domingo [mailto:jdomingo@knology.net]
Sent: Monday, January 07, 2002 9:40 AM
To: midrange-l@midrange.com
Subject: RE: Max Records in Physical or Printer Files - To Max or Not To
Max...

<snip>

        I have had occasions in which the create default was set to *NOMAX
and a
programmers test program wrote records to a file until I started getting
critical storage messages and was receiving complaints of the system slowing
down.  I found the culprit program and killed it and the file before the
system locked but, the inconvenience was troublesome (having to drop
everything to work on someone else's problem).