How do you capture all the errors?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 32
- Joined: Fri Dec 02, 2005 10:44 pm
- Location: Chicago,IL
How do you capture all the errors?
Hi there,
Can anyone suggest me of capturing all runtime errors and logic errors of a job on a flat file?
Thanks
Pradeep
Can anyone suggest me of capturing all runtime errors and logic errors of a job on a flat file?
Thanks
Pradeep
Welcome Aboard
There are numerous error that you can encounter on a flat file using the sequential file stage. File permissions, metadata problems to name a few. I suggest spending a few hours going through file related problems on this forum.
What do you mean by logical errors though, it passed me.
There are numerous error that you can encounter on a flat file using the sequential file stage. File permissions, metadata problems to name a few. I suggest spending a few hours going through file related problems on this forum.
What do you mean by logical errors though, it passed me.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 32
- Joined: Fri Dec 02, 2005 10:44 pm
- Location: Chicago,IL
-
- Participant
- Posts: 32
- Joined: Fri Dec 02, 2005 10:44 pm
- Location: Chicago,IL
Firstly, ThanksDSguru2B wrote:Welcome Aboard
There are numerous error that you can encounter on a flat file using the sequential file stage. File permissions, metadata problems to name a few. I suggest spending a few hours going through file related problems on this forum.
What do you mean by logical errors though, it passed me.
I 'm actually asking for 'how to write all errors to a flat file'
Logic errors :Errors like a mistyped key or other outside influence might cause the application to stop working within expected parameters, or altogether.
Thanks,
Pradeep
(Ten Hugs And Nine KisseS - THANKS)......is that true?
In GOD we trust,for all others we take cash.
Pradeep
(Ten Hugs And Nine KisseS - THANKS)......is that true?
In GOD we trust,for all others we take cash.
If you're just talking about getting what is produced in the dirctor log into a flat file, run an 'After Job Subroutine'
Routines\Built-In\Before/After\DSJobReport
It has instructions on how to use it in the routine description section.
If you want to get all errors detected within the job by your code, i.e. data errors, you could write these errors out to separte sequential files whereever needed within the job and then concatenate them all together after the job.
Routines\Built-In\Before/After\DSJobReport
It has instructions on how to use it in the routine description section.
If you want to get all errors detected within the job by your code, i.e. data errors, you could write these errors out to separte sequential files whereever needed within the job and then concatenate them all together after the job.
Regards,
Nick.
Nick.
-
- Participant
- Posts: 32
- Joined: Fri Dec 02, 2005 10:44 pm
- Location: Chicago,IL
Thanks Nick !nick.bond wrote:If you're just talking about getting what is produced in the dirctor log into a flat file, run an 'After Job Subroutine'
Routines\Built-In\Before/After\DSJobReport
It has instructions on how to use it in the routine description section.
If you want to get all errors detected within the job by your code, i.e. data errors, you could write these errors out to separte sequential files whereever needed within the job and then concatenate them all together after the job.
I know these possible options.
For the latter..
you are asking me to anticipate the errors and write the code accordingly...inside the job and write that to a flat file OR
can you please explain in detail what exactly do you mean?
Thanks,
Pradeep
(Ten Hugs And Nine KisseS - THANKS)......is that true?
In GOD we trust,for all others we take cash.
Pradeep
(Ten Hugs And Nine KisseS - THANKS)......is that true?
In GOD we trust,for all others we take cash.
-
- Participant
- Posts: 32
- Joined: Fri Dec 02, 2005 10:44 pm
- Location: Chicago,IL
Thanks!DSguru2B wrote:Whatever goes wrong with the job, it will be logged. You can get the log entries by various options of dsjob command. Namely -logsum, -logdetail, -report etc. Look into them.
I'm actually working on the same.
Thanks,
Pradeep
(Ten Hugs And Nine KisseS - THANKS)......is that true?
In GOD we trust,for all others we take cash.
Pradeep
(Ten Hugs And Nine KisseS - THANKS)......is that true?
In GOD we trust,for all others we take cash.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The only tool that can capture logic errors into a text file is a text editor. Logic errors can only be solved by brainpower, perhaps using tools such as the Debugger or active stage tracing.
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.
Pradeep, The errors I'm talking about capturing inside the jobs would only be data validation types of errors.
Is the field populated,
Did the lookup return a value,
Is the string too long
is the date valid
etc
These sort of errors you can code to capture.
The runtime errors are captured anyway by DS as discussed earlier.
what are the logic errors you are talking about. Can you provide examples?
Is the field populated,
Did the lookup return a value,
Is the string too long
is the date valid
etc
These sort of errors you can code to capture.
Code: Select all
Can anyone suggest me of capturing all runtime errors and logic errors of a job on a flat file?
what are the logic errors you are talking about. Can you provide examples?
Regards,
Nick.
Nick.
-
- Participant
- Posts: 32
- Joined: Fri Dec 02, 2005 10:44 pm
- Location: Chicago,IL