DSXchange

I am fairly certain that your job is doing a significant amount of I/O sorting and repartitioning and that the slowdown is due to these stages as opposed to a dataset. Can you enable your APT_DUMP_SCORE to see what processes you are actually running?

Kumar's suggestion of using a ICONV(In.Col,'D2MDY[2,2,2]') will work, as will manually creating a string with separators and then ICONving it.

There are many string and numeric functions that you can use in order to effect this. The best is to use pattern matching to extract portions of the string based on your rules (look into the BASIC manual under MATCHES ). Your pattern for the number could be "0X'('0N')'". Then you seem to be using a ...

Kirtikumar, that makes sense and is logical way to progress. Many jobs (particularly smaller ones) are currently still faster in Server than in PX and since it is never a good idea to mix large numbers of server and PX jobs on the same DataStage machine splitting by project and DS Server is a good i...

What stage are you writing to in this job? Perhaps the dataset is repartitioning to match the output and therefore is taking longer.

How many nodes in your configuration file? Do the data files reside on the same disk volume as your sequential file?

Hello Tiozzo,

I'm not quite sure what you mean by "hardcoding" as you already are using parameters and their runtime values for the database related values. Could you perhaps eloborate on which values you want to change?

Meena, you need to execute "dsjob.exe", there is no "dsrun.exe" and the dsenv file doesn't exist on windows either.

DSGuru2b - Not in Windoze

I think it is time to delve into the environment variables for precision in PX - I'm not at a PC with the PDFs right now, but perhaps you can find the relevant settings or someone here will add them to this thread.

It sounds like your two sequences are linked together in your master sequence design and therefore they won't start at the same time. Remove that link and you will find that they start off simultaneously.

When DataStage allocates structures and space it needs to use the defined maximum length. When it writes data to disk it will use the actual contents unless you specify fixed length. I think that the remove duplicates is allocating space based on the metadata and doing it's comparisons as if the str...

Hello vj,

welcome to DSXchange. It is important to post your questions in the appropriate forum - this one is to contain testimonials and not questions.

What is preventing you from running these sequences in parallel? Could you post the error messages or describe what isn't happening?

Kirtikumar - I'm not sure what you mean by that, since the design phases don't get affected by the data volumes.

SQL Server has a "BULK INSERT" capability to load sequential files directly. There are tricks and limitations in doing this, but you might be able to work around these issues.