DSXchange

Vinod,

my pleasure to be of assistance. Try here at IBM for some initial information.

Titto, I would recommend reading the sequential file as a 1 column file with no delimiters and in the first transform stage use the result of DCOUNT(In.BigColumn,'|') to see if the number of columns is correct and use the constraint to filter out badly formed records. You can then write the good rec...

Ken has opened up the OS Wars, or at least a small OS Skirmish, with his salvo against Windoze. The American datastage contingent will send advisors but the situation will soon escalate But jokes aside, how many here in DSXchange work with data warehouses or marts that have daily movements of millio...

DataStage does not support changing parameter values for a job from within the job itself (I think that has been shut off since version 5, but I can guarantee that it will not work at 7.x). You need to set the parameter value to it's ultimate value before the job is started.

Yes, you can run Px on 2003. Scalability and Performance have never been numbers to consider alone. Both of these values need to have measurements assocatied with them (let's use rows per second for DataStage and $$$ for hardware) I can make a Windows 2003 machine outperform a HP nepa platform. I ca...

srekant,

use the platform you already have the hardware for.

If you don't already have the hardware then there is no recommendation possible, there are too many variables. I can think of at least 20 factors off the top of my head without even trying.

Ray and I have been saying that this error message seems to be a non-fatal one - meaning that your data is going to be the same regardless of whether this message is in the log or not. Your incoming data needs to be sorted upon the key columns for your aggregation. It is not sorted that way, because...

You cannot do that. It is an internal message from the PX engine. It really shouldn't be an error message, but just a warning message. Why do you want this to abort your job? As Ray has explained, it means that there is no more virtual memory space to hold the data in your aggregation (might you be ...

The actual error message is that DS cannot create a temporary file in /tmp (at runtime). Do you have enough space in your /tmp directory (actually, why is it /tmp and not d:\tmp? Have you checked your configuration file)? You should be getting another error message when trying to do a "view data".

Put a modify stage into your job to convert the data type. In the conversion and datatype specifications you can efficiently add your null handling and default value setting. Although you can put your default value in the edit-row attributes in the transformer stage, it is more efficient to do so in...

Connecting a client to the server is not done with a path. At least not directly. Read the documentation first. I urgently need a coffee.

Hello Murali, (uppercase posts mean that YOU ARE SHOUTING, we are not hard of hearing and can understand lowercase quite well) Your requirement is common, but the answer depends upon your actual column definitions, as DataStage PX is very type sensitive. I will assume that you have two columns, STAR...

The newer model is the ak74. Played with one of those, the ak47 is better.

Try adding something else, like a "dir" command; can you do that? If not, it is probably access rights.

First, see if "at" is even up and running on your machine; you can type in the command "at" in a dos shell to check this. Then, do you have access rights to add to the scheduler? I tried your command and it worked (you can try executing "AT 14:00 /NEXT:5 vmdsr_sched.exe C:\Ascential\DataStage\Projec...