Hi,
In our project folders (few environments as well) there is over 3000 of DS_TEMP folders.
For the pursposes of testing I deleted few of these belonging to the different jobs and noticed that it does not affect them.
Would it be to risky if I was to delete every DS_TEMP folder? What exactly is its purpose?
Regards,
Novak
DS_TEMP Deletes
Moderators: chulett, rschirm, roy
Don't delete anything in project directories from UNIX. You have now ensured that next time any of the jobs are compiled where you have deleted the temporary directories you will get fatal errors. Most likely you will have to backup the jobs in question, delete them in DS and then re-import them before they can be used.
Don't delete anthing in project directories from UNIX.
Don't delete anthing in project directories from UNIX.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Let me add a little something. Don't delete anything in project directories from UNIX unless you know for a fact that it doesn't belong there. I will periodically clear out stray hashed and flat files from the Project, typically created when developers use the default hashed filename of its input link or when they don't path a flat file. So a hashed file name "DSLink47" is fair game but "DS_" anything? Forget about it.
When in doubt, leave alone.
When in doubt, leave alone.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
DS_TEMPnnn is used when designing job number nnn to hold temporary saves (for example when you click OK to close a Transformer stage) and prototype records for the RT_CONFIGnnn file which will be moved there when the job is compiled.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.