UniData TMP file cleanup for interrupted or abnormally terminated processes was improved significantly at UniData 7.1. I believe Amy indicated she is still running 6.1.16 (released in Dec 2005)
Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 **Denver, CO 80237 **USA Tel: +1.720.475.8055 Email: [email protected] Web: www.rocketsoftware.com/u2 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Colin Alfke Sent: Thursday, June 24, 2010 2:57 PM To: 'U2 Users List' Subject: Re: [U2] UniData 'QUIT' This is simply where UD puts things it's working on: print jobs (PRT*), active select lists (usually u*??), SB+ transfers (if you use network), and I think the output from capturing and returning on an execute. If things work properly and are allowed to complete normally, there should be nothing in here if no one is logged in. Generally, I see large select lists and print jobs where the user got tired of waiting and killed the session not allowing it to clean up after itself. If no one is logged in or UD is stopped it is safe to clear. Otherwise anything with a timestamp prior to the earliest login date/time is safe to clear. I haven't seen it cause a problem with logouts - but then I've never seen quite so much stuff in there before (usually it's a print job stuck in a loop that hammers all of the space on the drive). I'd be tempted to see how many are from the last couple of weeks when the problems started and where they are coming from - any text viewer should work - just watch the file sizes. Good luck Colin Alfke Calgary, Canada _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
