DSXchange

Go to the command prompt and fire them away!

Actually these scripts are by Uncle Kim, was a typo.
Here is the link where you can find a lot of other useful stuff.

http://www.duke-consulting.com/DataStage_Tips.htm

Click on this link to download the backup scripts
http://www.duke-consulting.com/Downloads/Scripts.zip

You should change the input file format of the sequential file you are reading to read as the file as a DOS file.

You would be able to execute all these commands as MKS Toolkit is installed when you install parallel edition on Windows (DS 7.5x2 and DS 8.x). MKS Toolkit gives you the ability to run unix commands on the Windows server.

If it's a bug. You can stop the job from running whenever the file has no lines. You would have to do this check before you trigger the job, But, it's just a workaround.

>You would have to get the count of records from your table somehow (Maybe create another job which gets the count) >Read the count from the file which you created (You can do this using a small basic routine or by using an execute command activity) >Branch using a conditional activity based on the ...

You can't just select a code page which works for a set of data.
You need to ask this question to the guys who give you the data, You need to ask them how the data is encoded.

With what logic are you converting 0.1 to 10, are you multiplying with 100?
What do you expect when the input is 0.01?

You need to ask your architects about the code page for NLS (e.g. Windows-1252). And then you need to change the NLS settings in datastage, you can make these changes on the job level or the project level.

But be aware that NLS is not supported on Datastage 7.5x2

You'll get this kind of a warning when the keys used in your sort stage are different from that of the Remove duplicates stage. If that's the case, there is no way to remove this warning other than suppressing it.

You can create 5 logins using the datastage web console. But, if you map it to the same OS user. Anything triggered by one of these 5 users will use the same OS user credentials.

You can get the information of the user who triggered the job in the datastage administrator. If you want to use it in the datastage jobs you can use "who" and parse the result to get the user id.

dscmdexport is a utility which comes with the "Client". So you can't run it on the "Unix server". You'll have to write to write a script which runs it on your client machine. Ken has a beautiful script which backs up all the projects on a server.

Looking at it in Notepad won't help you much... Check the contents of the file in a Hex editor. Compare your first input file and the file you are generating at the end (which has the Null character at the end). Do you see a difference?, If you do, then you are inserting the NULL in your job. If not...

I'll add that to the "To do list" :D

Will update this post once I have a new version