Search found 204 matches
- Wed Sep 14, 2005 6:20 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Inserted tsort reading input dataset
- Replies: 1
- Views: 1156
Inserted tsort reading input dataset
I have a job that reads two datasets and joins them. The jobs that created these two datasets partitioned them and sorted them on the key used for the join. If I set the partitioning on the join inputs to Auto, shouldn't DS detect that the partitioning and sorting are correct and leave the datasets ...
- Mon Sep 12, 2005 4:28 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Copying the input field to a string in build-op
- Replies: 4
- Views: 1739
The datatype of your input column is an APT_String. The methods available for this class are defined in string.h and basicstring.h which you can find in $APT_ORCHHOME/include/apt_util. You may not need to convert to a normal C string depending on what you need to do as there are lots of methods avai...
- Fri Sep 09, 2005 5:49 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance Mointoring on Solaris
- Replies: 5
- Views: 2160
Unfortunately there isn't a tracing tab. I'm also a bit limited in the tracing I can do as the systems are maintained by a third party. However when I get another window of opportunity on the machine I'll see what I can find with sar, vmstat and the like compared to the output when APT_DUMP_SCORE is...
- Fri Sep 09, 2005 2:35 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance Mointoring on Solaris
- Replies: 5
- Views: 2160
- Thu Sep 08, 2005 6:36 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance Mointoring on Solaris
- Replies: 5
- Views: 2160
Performance Mointoring on Solaris
I have seen the following behaviour in several of our jobs on different occassions but will describe it for a simple case: Two input datasets, one 26 million records totalling 1.3GB and the other just a handful of records are funnelled together. A filter removes about the the records by testing for ...
- Fri Jul 22, 2005 5:44 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance teaser
- Replies: 1
- Views: 1677
Performance teaser
We have a suite of jobs, both server and parallel that currently pass data between them via named pipes. This makes testing difficult as all the jobs need to be running at the same time. Additionally I wonder if the performance of named pipes might be worse than either sequential files or datasets. ...
- Mon Jul 11, 2005 9:05 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Job aborts when buildop includes string library
- Replies: 3
- Views: 2156
Job aborts when buildop includes string library
I have a very simple job that reads a character string and outputs it into separate fields. Whilst doing so it has to correct the input string for missing fiedlds based on the comma delimiters. The job uses a buildop which has been written bit by bit. It worked OK until we go round to using the Stri...
- Tue May 17, 2005 5:44 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Designer eats 100% CPU and is very slow
- Replies: 9
- Views: 4744
I have seen this problem in version 7.1. The last place I worked had several jobs that exhibited this behaviour and a support call was raised. Unfortunately it wasn't completely resolved. The problem looked like a memory leak as it happened when a job was left open in Designer for prolonged periods....
- Wed Mar 30, 2005 9:31 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: OSH - hello world
- Replies: 2
- Views: 2085
OSH - hello world
Hello, I am writing some PX jobs that will need calling from a script that will need to include some osh commands. I am trying to get the osh commands to work on their own but even the example Hello World gives an error: osh "echo 'hello, world'" ##I TFCN 000001 16:26:25(000) <main_program...