I am getting this warning message from the Director.
seqBSIS_2007,0: Import consumed only 228bytes of the record's 230 bytes (no further warnings will be generated from this partition)
seqBSIS_2007,0: Import warning at record 588736.
The problem is I want MORE of these warnings to pinpoint which record is giving me the errors but there doesn't seem to be a setting for that. Can anyone shed me some light on this?
It shows atleast one waring per partition. I dont have access to document or PX right now. I vaguely recall that, there should be a APT variable with wich you can change this default settings. But not sure about it.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
All warnings are displayed in the job log, unless you have a maximum number of warnings set when the job is submitted to be run (usually 50). This can be set in the Job Run Options dialog when you submit a job to be run from Director, or using the -warn option in the dsjob command.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
The problem is that DataStage is not generating all of the warnings even if I set the the 'Warnings: No limit".
The situation is there are 100 records in a file and there are 20 records that has problem but DataStage only displays the 1st problemed record and the rest are ignored.
I don't know where you can change the value you are looking for. I haven't found it in the ENV variables or documented anywhere. If all warnings to go to the log file it might slow the job speed from "fast" all the way down to "glacial" or even slower, so it would be best to cater for this type of warning in the job itself instead of letting the logging mechanism take care of it.
Yes, the warning limit is only Abort the job after the given n warnings. But the case is its wont show up the warning at all. "no further warnings will be generated from this partition"
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
We sort of had a workaround in detecting if the records has an import problem. Since the files being read is fixed width delimiter, we added an extra dummy column at the end and if the dummy column has a value, it would mean that the records read has characters that causes it to overrun and will be rejected.