DSD.StageRun is the routine that runs Transformer stages - it's one that was provided with the software. The error message suggests that you've provided a non-numeric value for some parameter that is supposed only to take numeric values. You need to do some detective work in your job design to figure out where that happened. You may wish to involve your support provider, since the error is generated by a vendor-supplied routine.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
1. reseting the job may provide additional input in the director log.
2. I've usually encountered this warning when a null was passed to a routine that expected a numeric value (been a while since i've seen this; I might be wrong).
The NullToZero transform (wherever viable) usually takes care of this when the errant column is found.
Finding it however is a another story
Amey Vaidya<i>
I am rarely happier than when spending an entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand.</i>
<i>- Douglas Adams</i>
You can ignore any errors generated by the 'Reset' process. What you are looking for is a 'From previous run...' log message, it is where any 'additional information' will be.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Because the error is from DSD.STAGERUN - shouldn't he be checking the transformer specifically? My understanding was the only thing that DSD.STAGERUN does is execute transformer stage code.
Yes, but then again no. The Transformer code invokes functions (generically called things like "get next row", "get row by key", "put") that are exposed by the passive stage on the other end of each link.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I remember that on some versions on some platforms all jobs would generate this spurious message in the phantom log file. What version and platform are you on?
I still think this might be caused by an issue within DataStage. If you have access to support I would run this by them. If not, you could run the following command from the uv shell "VLIST DSD_BP DSD_RUN.B". The first column will be the source line number. If you could post a couple of (source) lines before and after to this thread on of the olde guarde might be able to decode the compiled pseudocode.
When I executed the command ""./bin/dssh" in the $DSHOME folder I got the following error message
ld.so.1: dssh: fatal: libdsplugin.so: open failed: No such file or directory
Killed
ANd when I executed the command "VLIST DSD_BP DSD_RUN.B" in the DS Administrator there was so line no 544 in the output where I am getting the phantom error.........It showed some code till 543 and then directly for 547.............source line 544,545,and 546 were missing........