DSXchange

We imported a job to a server where previously a job with the same name was in place. This job will hang halfway while running it. If we make a copy of the job (copy_of_<jobname>) this copied job will run fine (after compilation of course). If we remove <jobname> and rename copy_of_<jobname> (which ran previously fine) to <jobname> the job will hang while trying to run. Any clue?

This clearly shows that the executables associated with the job has been corrupt. You may want to delete the job cleanly (so that all of its RT files are also deleted), and reimport the job.

I have seen something like this happen if the &PH& directory is not periodically cleaned out. Search the forum for the right way to do it.

John

Ummm, the &PH& contents do not affect job runs unless you have a serious underlying disk issue on the system, since a new file is generated each run.

It sounds like the ancillary information for the job is corrupt and gateleys suggestion will work. If not, there might be more problems in the project.

Use DS.CHECKER command to verify/clean up partially deleted jobs.

Thanks for the replies, I think the DS.Checker wil solve my problem, however, when trying to delete RT_ files I get an OS warning that I cannot access the file because it is in use by another process. I tried to delete the files from windows and command prompt (after stopping the datastage services), but I still cannot delete the specific files. Any further direction?

It seemed that UVSH.exe (I did not know that this was a datastage process) held the files in hostage. After killing uvsh.exe I was able to delete the files and the job now runs fine under the right name. Thanks again for the directions.