Search found 53125 matches
- Mon Aug 16, 2010 4:50 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Datastage Jobs Not Running
- Replies: 28
- Views: 16223
- Mon Aug 16, 2010 4:45 pm
- Forum: General
- Topic: Run Multiple instance with max of 2 instances.
- Replies: 8
- Views: 2673
- Mon Aug 16, 2010 4:43 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: link collector
- Replies: 11
- Views: 5098
- Mon Aug 16, 2010 4:39 pm
- Forum: General
- Topic: Changing Parameter Set values at runtime
- Replies: 3
- Views: 1463
But writing from within the job will not affect the values that the job read when it started. You can write to the values file before issing the job run request (and, of course, you must name that values file in a -param argument to the dsjob command if that's how you're issuing the job run request)...
- Sun Aug 15, 2010 7:52 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Passing Runtime parameter using $UserStatus
- Replies: 11
- Views: 13612
And then, when you need to unpack the delimited string, use the Field() function. The first element is returned by
and the second element is returned by
Code: Select all
Field(JobActivity.$UserStatus, "|", 1, 1)and the second element is returned by
Code: Select all
Field(JobActivity.$UserStatus, "|", 2, 1)- Sun Aug 15, 2010 1:00 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Run job based on Param value
- Replies: 7
- Views: 1828
This would be much easier wit sequencer. If you don't want to use seq then tell us how u r getting the parameters..... DSXchange is not a mobile telephone. It is unnecessary, and unprofessional, to use SMS-style abbreviations here. A professional standard of written English aids those whose first l...
- Sun Aug 15, 2010 12:58 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Wrapper stage
- Replies: 3
- Views: 1371
You have probably noticed that this is a completely different error. Your record schema appears only to describe up to column position 2. It needs to describe the remainder of the line. For example, if there are only two characters of data, do you have DOS-style line terminator? (If so, replace the ...
- Sun Aug 15, 2010 3:16 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Wrapper stage
- Replies: 3
- Views: 1371
- Sun Aug 15, 2010 3:14 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Transformer problem in WIN XP
- Replies: 3
- Views: 1523
The answer to Craig's dilemma is that this piece is written to run in UNIX (MKS Toolkit) and converts Windows pathnames to UNIX-legal pathnames. At run time your shared library search path is not finding the dll to which the Transformer stage was compiled. Check in the log entry that reports environ...
- Sun Aug 15, 2010 3:10 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Non-Alpha numeric characters
- Replies: 6
- Views: 2131
- Sun Aug 15, 2010 3:08 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Run job based on Param value
- Replies: 7
- Views: 1828
- Sun Aug 15, 2010 3:07 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Reading the data from DB ( 2 file systems)
- Replies: 4
- Views: 1947
That's not an error - it's a metadata mismatch alert. One side you have a timestamp that supports microseconds (fraction=6) whereas on the other side you have a timestamp that does not support fractional seconds at all (fraction=0). Tidy up your metadata or, if this is not possible, use a message ha...
- Sun Aug 15, 2010 3:02 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: clarification on APT_TSORT_STRESS_BLOCKSIZE
- Replies: 4
- Views: 2760
Re: calrification on APT_TSORT_STRESS_BLOCKSIZE
Hi All, APT_TSORT_STRESS_BLOCKSIZE environment variable can be used only when you have a sort stage used in your job design with restrict memory option selected. Is this right? Thank you very much in adv for your reply on this. Regards, A kumar This is not right. APT_TSORT_STRESS_BLOCKSIZE affects ...
- Sun Aug 15, 2010 2:55 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Iconv oconv
- Replies: 10
- Views: 5428
- Sun Aug 15, 2010 2:53 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: UniData functionality is not supported on this platform.
- Replies: 1
- Views: 1213