Search found 18 matches
- Mon Jul 26, 2010 7:48 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: The modify operator has a binding for non-existent output
- Replies: 15
- Views: 32756
have you check column metadata is available for the column in stage you are putting query? I know it is an old post but I don't think it's necessary to open another for the same problem. I am taking the data from a dataset. My question is what if I have Runtime Column Propagation checked for all jo...
- Wed Jul 21, 2010 7:31 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Routine to write file - problems
- Replies: 3
- Views: 2019
I should kiss you both but probably the rest will look too strange at us after :) 1. yes, DSJ.JOBINTERIMSTATUS offered a much more accurate status and it works ok now. 2. I've read here how it should be. In my example I was using the code from the Help and I believed WeofSeq just positions me to the...
- Wed Jul 21, 2010 5:11 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Routine to write file - problems
- Replies: 3
- Views: 2019
Routine to write file - problems
Hello, I am having a hard time to figure out several things in my first routine. Basically I have to write a routine that runs after a job completes and I have the following issues: 1. Routine should start right AFTER job completes but DSJ.JOBSTATUS returns 0 which means the job is still running. Ho...