We are running a job which loads the database.
The job has sequential file--->transformer--->odbc stages.
The job finished successfully with out warnings.When we check the job log, there are fatal errors(deadlock occured).
The job should abort if there are any fatal errors! right?
These error messages are related to database(DB2).
Is there anyway to set our job to abort, when there is any fatal error in the log?
Thanks in advance
Via
How to abort a job when there is fatal error in log?
Moderators: chulett, rschirm, roy
How to abort a job when there is fatal error in log?
Via
-------------------------------------
Learn all the way, as you Grow each Second
-------------------------------------
Learn all the way, as you Grow each Second
Hi Kumar, there are no message handlers defined. Actually there are duplicates in the input file to the database.So, dead lock situation occured, But wondering
whatever is the case, datastage is throwing fatal error and could not abort that job.
whatever is the case, datastage is throwing fatal error and could not abort that job.
Via
-------------------------------------
Learn all the way, as you Grow each Second
-------------------------------------
Learn all the way, as you Grow each Second
Hi,
hope this helps...
A terminator stage can be placed in a job sequence to ensure that a job is stopped cleanly if ther are fatal errors.
1) use a job activity stage and select the expression type as failed
2) use a terminator stage and stop all the other subordinate jobs if required..
Thanks,
Savis
hope this helps...
A terminator stage can be placed in a job sequence to ensure that a job is stopped cleanly if ther are fatal errors.
1) use a job activity stage and select the expression type as failed
2) use a terminator stage and stop all the other subordinate jobs if required..
Thanks,
Savis
Hi Savis,
What you are saying is correct. But my job is not failing(even though fatal errors)....the status after the job run is finished.So i cant use terminator.
I am running this job individually not through sequence.
Thanks
What you are saying is correct. But my job is not failing(even though fatal errors)....the status after the job run is finished.So i cant use terminator.
I am running this job individually not through sequence.
Thanks
Via
-------------------------------------
Learn all the way, as you Grow each Second
-------------------------------------
Learn all the way, as you Grow each Second
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
When you run a job you can set a maximum number of warnings. The job will abort when this number of warnings is exceeded. A value of 0 means that the job can generate an unlimited number of warnings and still run to completion.
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.