DSXchange

Prithivi, for urgent issues like you are obviously having I suggest you contact Ascential/IBM or your support provider. They are paid to assist you in matters such as this. The volunteers in this forum are not. While waiting on a response from your support provider you might spend some of your time ...

DataStage PX has no idea of how many physical CPUs a SMP system has, apart from the code that checks licensing. The configuration file tells PX how many virtual nodes (or CPUs) it is to run on. The OS - be it Windows or UNIX - is responsible for allocating tasks across the physical processors.

Combinability mode lets the DataStage compiler potentially 'optimize' the number of processes used at runtime by combining operators. It is usually a good idea to leave this setting so that DataStage can tune jobs for performance automatically. I haven't written a job yet which requires changing thi...

The thread is a year-and-half old and is pretty much closed. If you have a connection issue could you perhaps post your config & questions in a new thread?

Can you compare it to compile times (preferably of jobs without transform stages) on your system at the same time? There is little comparison to be done without a frame of reference.

AK77, I should expand on what you might be doing instead of just stating what to do. I'll just illustrate with a simplified example - If you have 3 processes all updating the same keys in a table and they have a transaction size of 10, meaning they will do 10 changes and then commit their work. If p...

set the rows per transaction to 1

Kishan,

try lowering your commit frequency to 1 or changing your locking scheme and see if it makes a difference. If the deadlock goes away then your question is answered.

You can write/execute the code discussed in this thread either in a Job Control section or in a before/after subroutine or even in a normal routine and call it from wherever you can call routines. Important is that the code never gets called with the jobname and instance of the calling process, due ...

ragu, yes it makes a difference. In the original post you stated that you had used ICONV/OCONV to format the data so I assumed that you were doing a numeric comparison on the internal date. If you are doing a string comparison on the date you need to get both formats in the form YYYY-MM-DD. Just mak...

Ken,

I thought the topic looked kinda familiar, I should have been paying more attention...

It is an internal routine that is supplied only as object code without any source, so we are out of luck on that one.

The ExecDOS() will only work if your Server is installed on a Windows machine.

Use a normal sequential flat file whenever you can; it is simpler, easier and more efficient. Some COBOL structures cannot be read in a sequential file stage, for example anything with an OCCURS DEPENDING ON, and you need to use the complex stage to process these types of files.

Camaj,

does that mean that this problem occurs every time you issue the command? Does it happen when you manually execute it from a user session?