DSXchange

From wherever your vendor, to whom you have paid the license fee for the PACK, tells you to download it.

Why has the total elapsed time increased by 50%? Are you processing a greater volume of data? How hard are you working your machine? Are there "running in parallel" or "time shifting" opportunities to be had to even out the load on the machine? These are just some ideas to get you started.

If you have MetaStage you can capture the process metadata directly. Every single event has its own timestamp - which ones did you require. They can all be retrieved from the job log using a routine, or even a job. You can also create a routine to interrogate the job itself, using the DSGetJobInfo()...

Can u plzz tell how to invoke that function ? Where to invoke that function ? Can u plzz tell the detailed description of that as i am new to datastage . Here at DSXchange we value professional standards of written English, much as your employer doubtless expects you to use when documenting your wo...

If you use a BASIC Transformer stage a suitable expression is
Note the comma inside the conversion specification of Oconv().

This would be SO easy to do in a server job, using an intermediate text file.

This would be SO easy to do in a server job, using an intermediate text file.

Read Method = Table is a direct read - it does not provide for ORDER BY. Nor GROUP BY nor HAVING for that matter. This is why/how it is fast.

If you want DB2 to sort the data you must use one of the SQL-based read methods.

This is one of the reasons you should never kill -9 DataStage processes. There are no special tools in DataStage. You could try using UNIX tools, like ps -f , to find out what that process is doing but, if it's a zombie, you'll be out of luck. Processes in a wait state should eventually time out but...

Copy the NullToZero transform and make your own NullToValue. It takes less than two minutes.

... and you will find every description and annotation that includes the word "column"!

Oh, you don't do documentation?

Are you using version 7.5x2 ? I also get this, particularly connecting to 7.5.1A and 7.5x2 servers. I believe it's a bug in the client. The workaround, which I don't like, is to type in the name of the Transform or Routine. The bug is that it only displays the first branch of the first level of the ...

Line 107 contains Get.Pin%%V0S17P1 which maps back (via a $DEFINE declaration) to CALL $DSP.GetNext(1,Pin%%V0S17P1.REJECTEDCODE) This is a GCI subroutine call to retrieve the next row from DSLink3 (see line 23 for the generic interpretation). Since you have your Oracle stage providing rows to DSLink...

/dev/null is a special device on UNIX into which you can dump any data you like - it will never be seen again (which explains why I called it a "black hole"). The equivalent on Windows is a file called .\NUL