...and that is the question. When creating a physical or printer file, it is MOST annoying and sometimes VERY disruptive when one of these types of objects reaches its record limit causing the application to halt until an operator responds with an incremental value. I know way back in the days of the SYS38 you could "pin" a machine silly with a runaway file but doesn't the 400 handle this now with ASP threshold and disk limitations parameters? We'd like to create all applicable file objects to size(*NOMAX) but perhaps someone can educate us first to any extenuating circumstances that could arise from this decision. Thanks all and HAPPY NEW YEAR! Rick Rayburn _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.