DATA.30 OVER.30
RT_STATUS4149
RT_CONFIG2636
&PH&
RT_BP4219
VOC
VOCLIB
SDKSequences
wrapped
Can someone explain purpose and usage of the files below
Moderators: chulett, rschirm, roy
-
srinivenigalla
- Participant
- Posts: 35
- Joined: Thu Aug 11, 2005 5:21 pm
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
DATA.30 - primary group buffers of a dynamic hashed file
OVER.30 - secondary group buffers of a dynamic hashed file
RT_STATUS4149 - status records for job #4149 and its stages and resources
RT_CONFIG2636 - run time configuration of job #2636
&PH& - output files from "phantom" (background) processes
RT_BP4219 - generated DataStage BASIC code from job #4219
VOC - the project's "vocabulary"
VOCLIB - overflow area from VOC
SDKSequences - used by SDK key management routines to store sequences
wrapped - storage of wrappers for parallel job Wrapped stages
Usage is automatic - managed by the tool itself.
You should periodically clear old files from the &PH& directory. Other than that, do not - ever - delete any of the other files/directories that you have listed.
OVER.30 - secondary group buffers of a dynamic hashed file
RT_STATUS4149 - status records for job #4149 and its stages and resources
RT_CONFIG2636 - run time configuration of job #2636
&PH& - output files from "phantom" (background) processes
RT_BP4219 - generated DataStage BASIC code from job #4219
VOC - the project's "vocabulary"
VOCLIB - overflow area from VOC
SDKSequences - used by SDK key management routines to store sequences
wrapped - storage of wrappers for parallel job Wrapped stages
Usage is automatic - managed by the tool itself.
You should periodically clear old files from the &PH& directory. Other than that, do not - ever - delete any of the other files/directories that you have listed.
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.