including reason of rejection of row in reject file
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 67
- Joined: Thu Apr 06, 2006 7:13 am
including reason of rejection of row in reject file
hi
i am collecting all records in reject file , i wann to include the reason for each row that is getting reject,
here i have added one more column in reject file as REASON, nw i wann the message which comes in the director for rejected row to see in this column , is there any way to do this
i am collecting all records in reject file , i wann to include the reason for each row that is getting reject,
here i have added one more column in reject file as REASON, nw i wann the message which comes in the director for rejected row to see in this column , is there any way to do this
Bhaskar Jha
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Lacking sufficient information I am assuming your job design ends something like the following.
You use link variables on the rej link:
Code: Select all
-----> Transformer -----> Database
| out
| rej
V
RejectFile
- out.SQLSTATE VarChar(12)
out.DBMSCODE VarChar(12)
out.LASTERR VarChar(2000)
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: 67
- Joined: Thu Apr 06, 2006 7:13 am
Still lacking information.
If your target is database and if you collecting the information on the reject records, the way ray sais would do. Add another column where you can supply the link variables to get more information.
Allong with that you will have the rejected record as well.
Not sure what you need more.
If your target is database and if you collecting the information on the reject records, the way ray sais would do. Add another column where you can supply the link variables to get more information.
Allong with that you will have the rejected record as well.
Not sure what you need more.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
-
- Participant
- Posts: 67
- Joined: Thu Apr 06, 2006 7:13 am
i added one column in target, which is a seq file , and with the help of DSStageLastErr function , its not giving any information as why this row is rejected , it just informs that row is rejected.
i wann information as if it is getting rejected because of key column being null or say datetime overflow
Plz tell me what are the exact input u wann from my side
i wann information as if it is getting rejected because of key column being null or say datetime overflow
Plz tell me what are the exact input u wann from my side
Bhaskar Jha
For that you have to code accordingly. Like a batch script. Even then you wont be able to get warning message for each and every row. That information is present in the log files which is getting filled during the exection of the job, so there is no way you can get that info inside that same job. After the completion of this job, you should execute another job control, or batch job that goes in and runs commands to get the log files, specifically with type other than info.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 67
- Joined: Thu Apr 06, 2006 7:13 am
As i mentioned. You need to do this after that particular job has finished.
You can use
All of this is listed in Server Job Developer's Guide in dsbooks.
If you want to code it in a routine, or even in the derivation in the transformer, look at the DSGetLogSummary() function.
You can use
Code: Select all
dsjob -logsum -type WARNING PROJECTNAME JOBNAME
If you want to code it in a routine, or even in the derivation in the transformer, look at the DSGetLogSummary() function.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.