I have a parallel job with the following design
Dataset----->surrogatekey------>target DB2 table
I am using DB sequence as surrogate key generator.The user with which the job ran was not access to the particular DB sequence.So the job got fatal error.But instead of aborting the job it has been finished with warning.
Job finished succesfully with fatal error
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 152
- Joined: Mon Mar 07, 2011 6:16 am
-
- Participant
- Posts: 152
- Joined: Mon Mar 07, 2011 6:16 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What's really needed is a change in mindset. In server jobs a Fatal error always causes the job to abort. In parallel jobs this is not necessarily the case - the controlling process (section leader or conductor) makes a decision about whether the other players, other nodes, can continue to execute.
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.