Simulating restartability
Moderators: chulett, rschirm, roy
Simulating restartability
I have a job sequence and I am trying to reproduce an error to check my restartability logic. I have a loop at the beginning within which a job is called. There is another loop later in the job sequence where there is another job. I tried stopping the job and restarting but Datastage asks me to reset the job which obviously defeats my purpose. Has anybody done this?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
"Stopped by operator" is not a status that is amenable to restart. You need to cause one of the jobs to abort - not the same as being stopped. Feed it some duff data.
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.
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Yes. And also a proper noun always starts with a capital letter.abc123 wrote:Thanks gentlemen, for your responses. ray, by "duff" data you mean some bad data, right?
It should be 'Ray' and not 'ray'.
Whale.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
That is correct, this adjectival form is widely understood in the UK and most of its former colonies.abc123 wrote:Thanks gentlemen, for your responses. ray, by "duff" data you mean some bad data, right?
Curiously, the adjective form does not appear in dictionary.com nor does the colloquial usage "up the duff" meaning pregnant.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
No, since that - being a proper noun - would require an upper case "D".
I believe the phrase is "hoist by his own petard".![Razz :P](./images/smilies/icon_razz.gif)
I suspect that abc123's aberration was merely a slip of the Shift key. As Dilbert once put it: shift happens.
I believe the phrase is "hoist by his own petard".
![Razz :P](./images/smilies/icon_razz.gif)
I suspect that abc123's aberration was merely a slip of the Shift key. As Dilbert once put it: shift happens.
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.
Just to restart the topic. DSGuru2B, I am trying your technique but I have a problem. I have selected ExecSH in the After-Job subroutine without any "Input Value". This will make the job fail but that's not what I want. I want to simulate restarting the job so I want it to fail on the 2nd or 3rd iteration (I have a loop in the Sequence job) so I pretty much have to do this at runtime. How would I do that or should I follow Ray's instruction and try to send in some bad data?
Can you suggest how I would send bad data in my situation? My job sequence has 4 ExecuteCommand stages and 1 Job Activity stage. The job activity stage calls a job which goes through several different files of exact same structure. The first stage in the job is a sequential file stage which has all char input columns.
Or modify the Script in ExecuteCommand or a script in Afterjob to intake a paremter and create a warning based on the parameter value say if the value is greater thatn 2. You can produce warning by executing some wrong script or referring to a wrong file name or path.
The input parameter can be you loop counter. So that at 2 or 3 count you will get the warning.
The input parameter can be you loop counter. So that at 2 or 3 count you will get the warning.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
kumar_s, I tried putting in an ExecuteCommand with a non-existing shell script inside. It produces "Reply=1" value but still executes successfully. I tried doing "After-job subroutine" where I did a DSSendMail. It producess an warning in the job log but does not produce a warning in the sequencer. Everything executes successfully.
Thanks for your help.
Thanks for your help.