How does one go about cleaning out every last shred of evidence of a DS job? I'm sleuthing an abend and I'd like to recreate this job from the ground up with no evidence it ever existed.
Thank you
Complete cleanout of a job
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 18
- Joined: Fri Aug 18, 2006 11:47 pm
- Location: California
Re: Complete cleanout of a job
This is supposed to be done by DataStage[or any other tool for that matter, say oracle] to clear up the dependents.data_whs_team wrote:How does one go about cleaning out every last shred of evidence of a DS job? I'm sleuthing an abend and I'd like to recreate this job from the ground up with no evidence it ever existed.
Thank you
On the lighter side, Try
Code: Select all
Uninstall & maybe, format drive
![Laughing :lol:](./images/smilies/icon_lol.gif)
![Wink :wink:](./images/smilies/icon_wink.gif)
![Wink :wink:](./images/smilies/icon_wink.gif)
-
- Charter Member
- Posts: 18
- Joined: Fri Aug 18, 2006 11:47 pm
- Location: California
Dangerous and shouldn't be the initial approach to take. All you should have to do for a 'thorough cleanout' of the job is delete it.data_whs_team wrote:I thought if someone had a set of sqls I could run them in Administrator Command, then I could do a thorough cleanout.
If something very unusual happens with that and you are left with remnants of the job around, then perhaps individual sqls (or the use of the DS.TOOLS menu) would clear it up.
-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:
They've taken the option to check for orphans out of DS.TOOLS in recent releases. However, the command is still there. From memory it is either DS.CHECKER or DSR.CHECKER. Execute from the Administrator client Command window when you have exclusive access to the project.
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.