DSXchange

htrisakti3, this can be caused by several things. You will need to give us more information, it is like saying "My program has aborted, what has gone wrong?". Most frequent cause of this type of error message is doing incorrect programming in a transform stage which, although it compiles, causes a f...

Hello Ray & Kim, I've tried getting another valid UV_SCHEMA file/table into the same physical location - no avail, it also gives me no update privileges as either root/dsadmin. Normally I would bite the bullet and do a clean re-install, but this site is quite large and those 80+ projects have th...

In a system with over 80 active projects the UV_SCHEMA file has become corrupted. Unfortunately, even when logging in as root or dsadm, it can no longer be modifed (to replace the missing CATALOG entry). I have tried working with the builtin SQL statements in order to get access (both GRANT ALL PRIV...

Since you are doing a string comparison the answer is not so difficult. Assuming your list is in the form {value},{value},... then the function INDEX(ParameterList,Link1.Column1:',',1) will return a 0 if the element is not in the list, or a position in the parameter list if it is found. Remember tha...

Hello Gateleys,

the simplest and most efficient method would be to sort the incoming stream by Cust_ID and then to use a stage variable to store the last Cust_ID value and to do a comparison on this value with the current Cust_ID to see if this has changed in order to do your x5 computation.

Hello Affan, let us take a simple job example, reading from a source and with two transform stages before writing to some target. Normally this job will execute as one process under UNIX. On SMP architecture this will be processed on one CPU at a time, perhaps getting swapped out and back in onto an...

Ray, Just last week I came across a scenario where using the link partitioner made more sense than doing a multi-instance job. The data flow came from a database table and some complex transformations were done to the data before writing it to a staging hashed file. The throughput was (I'll use rows...

Your solution might be a good one for your job. In addition, once you have converted the DATE to an INT32 you can then use stage variables in a transform to get a MAX value across rows. But if your incoming data is already sorted in the group order you want it, then your solution with an aggregator ...

Tasneem,

often the cause for this error is using column propagation and re-declaring an incoming coming. Do you have column propagation turned on in any of the output tabs going into this stage?

Vinodhj,

in DataStage jobs when you output to a hashed file it is always done as an 'update'.

At the moment this forum doesn't have have a "code" section, but PM me with your e-mail address and I'll fire off the program to you.

Normal PX jobs & transforms do not have the DS/Basic functions available to them.

You can use a BASIC transform stage in PX which gives you the ICONV/OCONV functionality, but it slows the jobs down considerably.

There is no real limitation of how many output stages you might have; but for 60 potential output files this is a bit much. I would look into using the PX "fileset" - you can partition this so that you have 60 dataset files in the file set but in the job it just looks like you are writing one file.

You can disable indices in a PX load job - but not for the reasons that there is not enough space left. Usually you disable constraints and indices during a bulk load to make it go quicker, then subsequently re-enable and re-build them. In your case that would abort as well. You need to talk to your...

The command line interface doesn't give you that option, but it is available in the routines, you can get the most recent run information from DSGetJobInfo() and use that time value to get the appropriate entries via DSGetLogSummary().