guys,
does anyone know weather we can use two embedded explicit conversion functions in one specification in a modify operator.. i have tried this but the modify operator gives an error..
..moreover i have also observed the when i do an implicit data type conversion which is legal..i get a warning in my log..saying that the implicit conversion is being made...
any thought on this..
thanks,
srikanth.
modify operator
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 38
- Joined: Wed Mar 17, 2004 1:16 am
- Location: USA
Hi Srikanth,
There was a discussion quite some time back on the ADN where the conclusion made was - you cannot have 2 coversions in the same specification in the modify stage.
For your 2nd question - modify stage can be used for explicit conversions. If you want to do implicit conversion you have to use the Copy stage.
HTH
--Rich
Pride comes before a fall
Humility comes before honour
There was a discussion quite some time back on the ADN where the conclusion made was - you cannot have 2 coversions in the same specification in the modify stage.
For your 2nd question - modify stage can be used for explicit conversions. If you want to do implicit conversion you have to use the Copy stage.
HTH
--Rich
Pride comes before a fall
Humility comes before honour
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The engineering philosophy of DataStage is to log warnings wherever something occurs that does - or even might - cause errors in data. I guess in this way they indemnify the software from being blamed when these errors occur.
There is no mechanism to prevent these warnings from being generated and logged - as I said, it's their philosophy. They do provide filters on the log view, so you can suppress the display of warnings if you like, but you can't stop them from being logged in the first place.
And, I would suggest, any request to have this capability added to the product would meet with polite refusal, citing the reasons I have given above.
There is no mechanism to prevent these warnings from being generated and logged - as I said, it's their philosophy. They do provide filters on the log view, so you can suppress the display of warnings if you like, but you can't stop them from being logged in the first place.
And, I would suggest, any request to have this capability added to the product would meet with polite refusal, citing the reasons I have given above.
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.