The space I am referring to here is the space required to create and save a permanent sas dataset. The allocation that used to work (V6) was specified as: space=(6144,(40,20)),avgrec=K. The revised space that (finally) worked (under V8) was space=(6144,(60,30)),avgrec=K. Nothing was changed in the SAS code-- no long variable names, nothing. Are you suggesting that maybe some system specific "overrides" are creating the need for me to change my space allocation? -- And not something specific to SAS v8 versus V6?

-----Original Message----- From: Paul Dorfman [mailto:paul_dorfman@HOTMAIL.COM] Sent: Friday, January 19, 2001 2:47 PM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: sas version 8 on mvs-- some issues

>From: "Igra, Amnon" <AIgra@ADMINSVCS.CORR.CA.GOV>

>Here are some of the issues I have encountered. > >1. space issues. Running the same job under v6.09 and v8-- the v8 >job >runs out of disk space for creating a fairly large sas file. >(200 to 500 >mb). Solution-- allocate more space.

It is hardly an intrinsic V8 problem. When the system folks install SAS and create the catalogued proc, they are very conservative about the amount of work space, and often even allocate it in blocks. Over years of use, your V6 proc default allocation might have been changed to allow more space. Create two identical datasets using V6 and V8 engine, write each to a separate perm library, then use a system utility to check the space they occupy. In my tests, I have not found the difference to be of any dire significance. V8 file can be marginally larger at the expense of the descriptor, but it is a drop in the ocean.