Yes, you can. You will need to call DSGetLinkInfo(JobHandle,StageName,LinkName,DSJ.LINKROWCOUNT) and pass it the appropriate handle (returned from a call to DSAttachJob() ) and the stage name & link name you are interested in to get the number of rows.
It sounds like your table definition in the database is not 10,2 but 10,1; the truncation is happening on the output link. Can you please check DB/2 and ensure that you do have 2 decimal places defined?
I can't call up DS now, but I do know you have to enter the partition table information on one tab, and then configure the serial/parallel tab on another. I know you will have to add the information on this tab so that each node get it's distinct data when running in parallel but you don't need to r...
This is now the 3rd post within a couple of hours with exactly the same question; it has already been answered in the other posts, but please use search or even just scan the titles of the currently active threads to avoid this kind of duplication.
I think that no answers have been forthcoming because the question is phrased around a misconception of how PX jobs will read from a database in parallel. You stated So, when i give parallel mode in the oracle enterprise stage it will retrive the double no. of records which is incorrect but forms th...
This would be the same question posed in this post , right? There are various ways to do this; it does depend on if you just want to view the data (use the director), want the information in a file and are comfortable with UNIX scripting (use the dsjob interface to get the data) or want it in DataSt...
You could write a script that uses "dsjob -ljob <project>" to get the list of jobs, then iteratively call up "dsjob -logdetail <project> <job>" to get detailed information per job and can filter out entries by date.
Installing a DB/2 connection for PX is a bit more involved. There is a whole list of configuration settings and prerequisites in the installation guide, have you gone through those? Also, can you issue a "db2 connect ..." on your DataStage UNIX server "A" to the DB on "B"?
If you enter the command "COMO ON {filename}" it will begin echoing all terminal I/O to a UNIX file called "{filename}" in a subdirectory called &COMO& in your project directory. You need to execute the command "COMO OFF" to stop recording data to the file.
I think that the restriction that job parameter values cannot be changed from within the job came in at Version 7; so if you used this functionality in the past you will have to redesign those jobs that used it. Job parameter values have never been able to be changed within jobs. Arnd is confusing ...
Craig - I agree with you there. It's like going to the doctor because you aren't feeling well and, after hearing "you are sick" you respond "no I'm not!".
1. If you are going to upgrade, go to the most recent 7.5.x version for your platform. 2. Officially there should be no problems, but in practice there will most likely be some small differences in some parts that you will need to tweak. That's always been the nature of the beast when upgrading. 3. ...