The only problem is if a program gets into a loop and keeps adding records until all the DASD is used and your system crashes. If you are sure that will not be your problem you can change the file to *NOMAX with no problem. 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). Kind Regards, Julio R. Domingo 429 Clydebank Drive Madison, Alabama 35758 Phone: 256-340-5084 Cell: 256-289-4544 E-mail: firstname.lastname@example.org -----Original Message----- From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Rick Rayburn Sent: Monday, January 07, 2002 10:13 AM To: email@example.com Subject: Max Records in Physical or Printer Files - To Max or Not To Max... ...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. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-Lfirstname.lastname@example.org Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.