What is the source of the file? That other system, maybe? What are the record characteristics? If the file has fixed-length records but is written as variable, that will consume a lot of extra space.
Besides, how critical can it be if you don't give it the dasd real estate it needs? :) Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Greenberg Sent: Monday, June 19, 2006 4:37 PM To: [email protected] Subject: Re: How can we quickly determine the number of output blocks a file will need on a CMS disk? On: Mon, Jun 19, 2006 at 05:56:31PM -0500,Mike Walter Wrote: } Well, this has been an interesting day. One of our commands to copy files } into production failed to copy a critical file because the output disk was } too full to handle the file. Just a WAG here Mike, but if the file has more shorter records, wouldn't the number of pointer blocks go up? I haven't looked at DISKSIZE in ages but would assume that it uses an average record size to estimate the number of pointer blocks, and that average is way off for this file Also, just IMHO, if its a "critical" production file, you should add a bit to the DISKSIZE estimate for a safety factor. -- Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353 Eastern time. N6LRT I speak for myself & my dogs only. VM'er since CP-67 Canines:Val, Red & Shasta (RIP),Red, Zero & Casey, Siberians Owner:Chinook-L Retired at the beach Asst Owner:Sibernet-L
