Only consideration I have is for run away datasets. Those that could grow beyond 4GB limit and you do not know it until your storage pool (and any overflows/spill pools associated with the pool) have been consumed by the extended dataset.
I have had pools fill up due to one VSAM file that took 1TB of storage. It was unexpected and other jobs/tasks failed due to the pool being full. If you have enough storage to handle the maximum allocation your files can become, then no issues with extend for any file. You may want to consider putting in place notifications when the IEC161 220 message shows up. Or when the zFS file or HFS files gets really big. Some UNIX users can create massive dumps in your USS environment in z/OS. Lizette -----Original Message----- >From: "R.S." <r.skoru...@bremultibank.com.pl> >Sent: Dec 20, 2016 3:52 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: Using Extended Format as default > >W dniu 2016-12-20 o 21:37, Porowski, Kenneth pisze: >> Is there any compelling reason why I should not (or can't) use Extended >> Format for all SMS managed Sequential (flat and GDG) and VSAM (KSDS, ESDS, >> Linear) datasets? >> >> Anything special I would need to do for Linear DB2 databases/tablespaces? > >Absolutely no. >Remark: the question should be asked 10-15 years ago >;-) > > >-- >Radoslaw Skorupka >Lodz, Poland > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
