DSXchange

Good morning again, the problem seems to be resolved. The job ran during the night with no problems.

<turns red> the end file did not have 'write cache' checked. </turns red>

Ty all for the help.

Good morning all, I am having performance problems with a datastage flow. The rows per second keeps decreacing for no obvious reason (3000 per second to about 300 per second). What I'm looking for is some kind of receipe of things to look at to maintain the initial performance. Here is information o...

Yeah , I still looking at it to make sure I do :D Additional information: In the jobs, we use the proper $PROJDEF variable Right now, the work around is to leave the parameter blank in the sequencer. The process uses the 'Default' value in the job ($PROJDEF). Still, I'd like to know how we can corre...

Good Morning all, I'v been playing with this one for a short while and decided to ask the community. In all of our OCI stages, we use project defined variables (ex: #$DBPW#). Works well when you run the jobs manually, but when we run the sequencer, I get the following message: ...: ORA-01005: null p...

ArndW wrote:Woth - that's the first time I heard about that. Are you sure you heard that from a credible source? ...

Just wrote you a private message

Between lookups in a hash file is supposed to be in the next major release ... can't wait either

for the first problem, you could use the following functions Count(yourString,".IR") -- gives you the number of occurences of ".IR" in your string Right(yourString,3)=".IR" -- gives you the last 3 chars for the second problem, you could use in a transformer index(yourSt...

Hi, Not having much information about the stages you are using, here is a simple idea. You could use a stage variable in the transformer stage. Have it output it once when the job is completed (either in a seperate sequential file or any other way you wish). In that file, you could have 2 columns --...

Looks like API functions could help you there [Server job Developer's Guide].

Here are some of the functions you could use....

• DSGetProjectList
  DSOpenProject
  DSGetProjectInfo
  DSGetJobInfo

hope it pushed you in the right direction

terribly sorry


it should read

Column1 = field1[1,index(field1," ",1)-1]
Column2 = field1[index(field1," ",2)+1,len(field1)]

hey! Column1 = myString[1,index(field1," ",1)-1] Column2 = myString[index(field1," ",2)+1,len(field1)] you might have to play around with the +1 and -1 in each. and might have to trim 'myString' before you start playing around with it. Basically, you search for the first 'space' ...

depending on the version you are using, there is an option in the stage that permits you to eliminate that warning

scratch space is a working area that the DS engine uses to do its operations (sort, merge, calculations, etc). It is a physical area, I mean that its disk space. Advantages....well: it permits you to do thoses oprations. If it says that its full, clean it up with the different datastage cleanup rout...

All the operands of the equations HAVE to be of the same type.
In your case:

asFloat((asFloat(46528) / asFloat(86400)))

0.5385185480


Hope it helps

Hello, I'm trying to figure this one out. Is there a way to tell Datastage's partitions to use Db2's partitions in a 1 to 1 manner. I have 4 datastage nodes defined (say a,b,c,d) - and 4 DB2 partitions defined (say A, B, C, D). Can we pair up a node to use exclusivly a partition. (node 'a' would use...