DSXchange

Try and google the keywords "tr command remove carriage return", that will answer your scripting questions.

DataStage processes files row-by-row. If you wish to do a whole file at once, exit DS and use a UNIX command such as "tr"

Unless you have a backup copy you cannot revert changes after saving a job.

All jobs of this type did this with the very same warnings. However, I am thinking that they actually compiled fine, but just warned that default values were not provided for those variables. Am I correct in that thought? Yes, the compilations went through and DS will substitute empty strings. The ...

If you added the Parameter "MIG" to your job, you need to refer to it using "#MIG#".

DataStage Version 8 has significantly higher overhead than previous versions. You should take a look at what the system is doing, without that detailed information an analysis isn't possible. When developing, look at your server and see if the machine is paging/swapping - in which case you might nee...

You cannot stop creation of an empty dataset and there is no builtin function for use in jobs that would give you that information. You can use the UNIX command "orchadmin" to list the number of records, this can be called from sequence and used in jobs.

Do you wish to create a sequence in DataStage to start the job and then call a stored procedure, or do you wish to write a Windows .bat batch file to start the job then call a stored procedure?

DS still uses "cron" & "at" at version 8.

I've never heard of these "Cobol Rules" and am not sure what you are trying to do. If you created a zoned decimal output to a file, then of course wordpad won't be able to read the binary output. What about using a string output from DataStage and doing the replacements as string functions in a tran...

You do not ever want to see this prompt, it means you called "uv" "uvsh" or "dssh" with the wrong attach point and since no valid DS account was found it wants to create one. Use Cntrl-C to get out.

That is an odd error, since I thought that the folder stage only open sequential files, and the error mesage about internal corruption only occurs for hashed files. What kind of files are in this folder?

Umm, you have just created a new DataStage account in the "bin" directory located below that actual account. You need to be in the "$DSHOME" account, then enter "bin/dssh" and there will be an UNLOCK verb there. Those extra files in the $DSHOME/bin directory won't hurt DataStage much, but they do no...

Nominally you can export with binaries at Version 5 and be able to import and run at Version 8. Some things might be different (such as changing parameter values within the job is no longer allowed) but overall DataStage is backwards compatible.