Search found 13 matches
- Thu May 07, 2009 8:26 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: trouble with stage xml output
- Replies: 5
- Views: 2286
explanation
Hi there, It is not strange... When you make NOM_SUPP the key (repetition path), the following thing happens: 1. When it goes from the first record to the second record it finds the CD_SUPP changed and not the NOM_SUPP. 2. Therefore, due to the rule it considers the xpath element common to both NOM_...
- Tue Jul 15, 2008 11:03 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: access hashed file through unix
- Replies: 2
- Views: 1435
- Thu Apr 19, 2007 9:43 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Not able to convert a 38 digit string to decimal
- Replies: 10
- Views: 3480
- Thu Apr 19, 2007 12:51 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Not able to convert a 38 digit string to decimal
- Replies: 10
- Views: 3480
- Thu Apr 19, 2007 12:41 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Not able to convert a 38 digit string to decimal
- Replies: 10
- Views: 3480
- Thu Apr 19, 2007 12:39 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Not able to convert a 38 digit string to decimal
- Replies: 10
- Views: 3480
If I remove the to_char() in the query and read it as decimal in the source stage, the job aborts with the error: Fatal Error: APT_Decimal::assignFromString: the source string (265801360696340669727895557154445859481 265801360696340669727895557154445859481 265801360696340669727895557154445859481 265...
- Thu Apr 19, 2007 12:26 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Not able to convert a 38 digit string to decimal
- Replies: 10
- Views: 3480
It is a 38 digit number. So the job is not able to read and process it as Integer and Decimal. I tried out reading it as Decimal but the job is failing. I tried to use the Peek stage and see what was happennng when I used ASInteger...the 38 digit no. becomes 000000000000000000000000000000000000000 ....
- Thu Apr 19, 2007 11:16 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Not able to convert a 38 digit string to decimal
- Replies: 10
- Views: 3480
Not able to convert a 38 digit string to decimal
Not able to convert a 38 digit string to number using the Type conversion functions. Need to do an aggregation calculation (max) on this column after it is converted to a number. Initially I was having problems in extracting a 38 digit number from a column in an oracle table. That is why I decided t...
- Mon Apr 16, 2007 8:37 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error calling job
- Replies: 7
- Views: 3344
Thanks for the responses!! I was thinking along the same line. Probably I will have to run them on a more efficient server. I was just wondering whether it had anything to do with improper job design (like too many nested calls, for example Seq calls a sequencer, which then calls another Batch, whic...
- Fri Apr 13, 2007 3:20 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Error calling job
- Replies: 7
- Views: 3344
Error calling job
Controller problem: Error calling DSRunJob(Batch::Test), code=-14
[Timed out while waiting for an event]
Can you suggest how can this error be avoided?
[Timed out while waiting for an event]
Can you suggest how can this error be avoided?
- Tue Apr 10, 2007 9:48 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Setting warning limit for jobs called from a sequencer
- Replies: 5
- Views: 2041
Re:
There is a small problem :D . The requirement is that I need to run different jobs with different warn limit and that too not manually!! The only thing is that I was preferring to use sequencers. But looks like I will have to do that with a batch.
Anyways, thanks for your inputs all through.
Anyways, thanks for your inputs all through.
- Tue Apr 10, 2007 9:34 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Setting warning limit for jobs called from a sequencer
- Replies: 5
- Views: 2041
Warning Limit
hmmmm....
I understand those being the other ways. Likewise once can also use the DSSetJobLimit from the JobControl of a Batch. But, I was wondering whether something like this was possible in sequencers or whether it was possible to customise the coding written in the JobCotrol of the sequencer!
I understand those being the other ways. Likewise once can also use the DSSetJobLimit from the JobControl of a Batch. But, I was wondering whether something like this was possible in sequencers or whether it was possible to customise the coding written in the JobCotrol of the sequencer!
- Tue Apr 10, 2007 9:17 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Setting warning limit for jobs called from a sequencer
- Replies: 5
- Views: 2041
Setting warning limit for jobs called from a sequencer
How can I set the warning limit of a job called from a sequencer?