LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (June 1996, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 27 Jun 1996 08:44:57 -0700
Reply-To:     Don Stanley <dstanle@IBM.NET>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Don Stanley <dstanle@IBM.NET>
Organization: Perpetually in limbo
Subject:      Re: HELP: Puzzled by $tmp files...

David Lombardo wrote: > > Our office has a rather unstable SAS application running on SAS 6.10 for > *Macintosh*. We've had a problem with disk full errors on our main server > volume, the cause of which appears to be the proliferation of temporary > files with names akin to $tmp001c.ssd01 (insert any two random hex bytes > in place of the 001c, and you'll get the picture). The size of these > files seems to be the same as that of the main catalog file (i.e., many > megs), varying only by 100K or so at times. > > My question: can I delete these files? > > The files appear to be static; no new ones have been added since I > increased the server partition in a fit of desperation last week and no > mod. dates have changed. > > I know NOTHING about SAS; unfortunately, all our resident SAS gurus are > soaking up the sun somewhere. In any case, no one here really knows much > about the bastard stepchild that is SAS for Macintosh. > > Could these temp files be created when SAS freezes or dies in a process > akin to dumping core? > > I'd appreciate any help anyone could give me on this issue. > > Thanks. >

Dave

Just delete them.

The safest way is to be out of SAS (so you don't mix any currently in use with the ones in want ousted) then just issue your Mac delete option on these files.

They got created by a SAS job that crashed and abended right out SAS. maybe it ran out of space itself or something, but SAS can't clean up when it abends.

Personally I think SAS Inst could fix this on all relevant platforms by doing a check at SAS startup for old temp files and killing them then. Hint Hint!

Don ==========================+++++========================================== Don Stanley Don Stanley Consulting Services NEW ZEALAND DSTANLE@IBM.NET


Back to: Top of message | Previous page | Main SAS-L page