I'm curious why you think you need to delete the hashed file when you are done? From both a lineage and trouble-shooting standpoint, you may be in trouble if that information is gone. Why not simply clear it (or drop and recreate it) at the start of the next run, an ability that's built into the stage?
-craig
"You can never have too many knives" -- Logan Nine Fingers
You can delete the hashed file (note: it's not "hash" file) using an after-stage or after-job subroutine. The actual command to use will depend on whether you are using an account-based or directory-based ("pathed") hashed file.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
As noted, it depends on how the hashed file was created. The log will show the command used, from which you can infer what you need to do to delete. So, pathed or in an account?
-craig
"You can never have too many knives" -- Logan Nine Fingers
I would use a parameter in the hashfile name so that each one is related to the run it was loaded in.
I agree with previous posts that they should not be removed.
1) for trouble shooting reasons.
2) disk space. What I mean by that is if the files maintain approx the same size each time they will hold the space they need for each run.
.......