The majority of our DS Jobs are run via a Unix Script which calls the DS Sequence and runs the jobs.
Occassionally, and particularly on Load Jobs, shoud the job abort due to 50 warnings, the error is not always relayed back to the Script and as such, on our scheduling program, the job shows as completed rather than aborted.
Is there a way of ensuring that errors raised within a DS Job can be passed back to the script that called the job in order to convey accurate information (as in the job aborted and did not complete)
Cheers
Reporting DataStage Errors
Moderators: chulett, rschirm, roy
Hi,
you should use the dsjob command line interface to get the job status and act acording to it.
search this forum for exact syntax (it was covered way beyond any need
)
IHTH,
you should use the dsjob command line interface to get the job status and act acording to it.
search this forum for exact syntax (it was covered way beyond any need
![Wink ;)](./images/smilies/icon_wink.gif)
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
![Image](http://www.worldcommunitygrid.org/images/logo.gif)