DSXchange

Ooh, that sounds like a challenge! I come from UniVerse's parent (Prime INFORMATION), beginning in 1983, via UniVerse, and DataStage 1.0 also.

That looks close enough to "balanced" to me.
Have you opened a call with your support provider?

If I am dealing with say 10,20 values...then it can get real ugly with all those links.

If you're dealing with 10-20 values, things are pretty ugly anyway!

The easiest way is to have the job write to the base file name then have an after-stage or after-job subroutine run a command to change the name of the file. For example you could invoke ExecSH as the routine, and provide the command mv #FileName# #FileName#_`date +"%Y%m%d"`_`date +"%...

You need to get a Windows SMTP mail client, such as blat. Search this forum for other suggestions.

-8 is an error code, meaning "not in stage". It most probably indicates that you've called DSLinkInfo (more properly that DSLinkInfo has been called) with a StageName argument that isn't a stage name, or was DSJ.ME but the call was made other than within a stage. Check spelling and casing. These neg...

I do this in 2 steps. The first job posts the result to a hash file then this routine reads from this hash file and sets a parameter value. All jobs in this sequence which start after this routine activity will get the new parameter value. You can modify this routine to get the value from what ever...

MUTEX locks - also called "smart semaphores" - live in the operating system. Instead of waiting, asleep, on a regular semaphore and waking when notified, the idea of a smart semaphore is to wait, retrying, so that you can wake faster. Which is good in theory. As machines became faster, the limit on ...

How are you specifying the DataSet? In particular, how are you partitioning the data when creating it in Job1?

Different databases handle the CHAR datatypes differently. All (necessarily) store the trailing space characters. Some mandate the trailing spaces in queries in result sets, others do not. I think you have encountered this, and have already deduced how to work around it.

There are some Error when we Run the Job !

This is akin to "there is some problem when we start the car". Very difficult to diagnose on that information alone.

You need to be more specific about the circumstances, the symptoms, the error messages, and any assumptions you are making.

Very easy. There is NO decrypting algorithm in DataStage. You must use whatever functions are available in the source database to perform decryption. If you must, you can write your algorithm as a build op or in DataStage BASIC as a routine, and invoke that routine from a Transformer or BASIC Transf...

The dsjob command can be used to start almost any kind of DataStage job; server, parallel or job sequence (not mainframe) from the command line (and therefore from a shell script/BAT file). You can also manufacture a batch within DataStage in three different ways: by creating a batch in Director by ...

It is just a warning. You can't prevent DataStage warnings if they're needed. You can only prevent them by removing the cause. In this case, DataStage is alerting you to the fact that it's being asked to process way more rows in one processing node than in another (subtly suggesting that you balance...

I like to think of a dataset as a text file that is spread over the available processing nodes; which piece is where is recorded in the control file.