SAS I/O error
in [SAS]
|
From: =?ISO-8859-1?Q?Daniel_Fern=E1ndez?= on 19 Jan 2010 06:28 Keep talking about TAGSORT option that Proc Me pointed I have found this SAS Note: http://support.sas.com/kb/9/238.html I hope it is helpfull. Daniel Fernandez. Barcelona 2010/1/18 Proc Me <procme(a)concept-delivery.com>: > Tina, > > I've a few questions and a suggestion! > > What system is SAS running on, is it Windows? Do you have a connection to a > server, if so, what and where? Is your work directory specified as a > location on a drive that is itself low on disk space, is this work drive > shared? Is there a value for the system option utilloc? Are the paths for > work and utilloc, if relevant, valid? > > The reason I ask is that I came across this note in the SAS knowledge base: > http://support.sas.com/kb/12/135.html > > Sorting may create temporary files either in work, or in utilloc, and it may > be that you are experiencing errors due to congestion here, rather than in > the drive that the libname abc points to. The failure to sort into a dataset > in work would be consistent with insufficient space in work, as might the > proc datasets behaviour. > > You can write the pathname of work (in Windows) to the SAS log using > > %put %sysfunc(pathname(work)); > > It may be that you need another work space, rather than another saving space. > > Proc Me > > PS: If you are looking at work spaces, you might as well check to see if > there are orphaned work directories from abended SAS sessions taking up > space unnecessarily. > > PPS: Consider using the tagsort option of the proc sort statement to reduce > the size of temporary files when sorting, specifying an out= dataset for > testing purposes, and specifying compress=binary to reduce file sizes, if > these are not familiar. >
From: Proc Me on 19 Jan 2010 07:20 Daniel, What a great usage note, if I'd seen it I wouldn't have needed those post scripts! Proc Me
From: Tina Shaw on 19 Jan 2010 16:37
Thanks for reminding me about the working space. I have never thought about it. My SAS is running on a remote server. After tried compress=binary and tagsort, out= , the I/O error still happened. The working space should be fine since within the same session, I can sort datasets istored n other library even though they are larger than the one bearing I/O error. So I am sure it's the saving space. After re-direct the permanent dataset to another location, it works. Again thanks! Tina On 1/18/10, Proc Me <procme(a)concept-delivery.com> wrote: > > Tina, > > I've a few questions and a suggestion! > > What system is SAS running on, is it Windows? Do you have a connection to a > server, if so, what and where? Is your work directory specified as a > location on a drive that is itself low on disk space, is this work drive > shared? Is there a value for the system option utilloc? Are the paths for > work and utilloc, if relevant, valid? > > The reason I ask is that I came across this note in the SAS knowledge base: > http://support.sas.com/kb/12/135.html > > Sorting may create temporary files either in work, or in utilloc, and it > may > be that you are experiencing errors due to congestion here, rather than in > the drive that the libname abc points to. The failure to sort into a > dataset > in work would be consistent with insufficient space in work, as might the > proc datasets behaviour. > > You can write the pathname of work (in Windows) to the SAS log using > > %put %sysfunc(pathname(work)); > > It may be that you need another work space, rather than another saving > space. > > Proc Me > > PS: If you are looking at work spaces, you might as well check to see if > there are orphaned work directories from abended SAS sessions taking up > space unnecessarily. > > PPS: Consider using the tagsort option of the proc sort statement to reduce > the size of temporary files when sorting, specifying an out= dataset for > testing purposes, and specifying compress=binary to reduce file sizes, if > these are not familiar. > |