DSXchange

Putting the double quotes around your column name causing the name to be used itself, instead of the contents of the variable identified by name.

Did my previous suggestion work for you?

If you execute a UNIX "cp" command from within a ExecSH() call the control will not return to DataStage until the command completes. The ErroCode that is returned is the UNIX error code. Are you planning on executing the "cp" command(s) as background process in your shell? That would be a different ...

What have you tried? A derivation at string level of "In.Col[1,4]:In.Col[6,2]:In.Col[9,2]" should do the trick.

vsi, use the manager export functionality to create a sequential file ".dsx" of the original version. This is the same method you will most likely use to move jobs between your 3 environments as well.

You are correct, it will only be called once in a Server job.

kumar_s wrote:Actually Trim function eliminates the given string and not the conversion.

In the example the CONVERT is executed before any TRIM.

Remember that CONVERT('ABC','',"This BCA") will return "This "; the CONVERT function works on a character-by-character basis and not on the whole string.

The way to access UniVerse from UNIX is to call up the "uvsh" command. You can do this with DataStage using either the "uvsh" or preferably the "dssh" command. If you don't specify a parameter your script will enter into the TCL environment, but if you execute uvsh "count voc" that will execute the ...

What datatype and attributes have you specified in your stage variables? Exactly what derivation do you do in the stage variables?

vmcburney wrote:...I hope this puts an end to those Google ad campaigns from Sunopsis asking "Is ETL obselete"!

Now the ads will read "ETL may be obsolete, but Sunopsis definately is"

A fully qualified path is a path which has an absolute path that begins with the root directory on unix, i.e. /tmp/DataStage/Data/Test/DSXChange/test.seq The other type of path is relative , which starts at some other point, usually the CWD (Current Working Directory) and this type of path looks lik...

This can happen if one project defaults to using inter-process buffering and the other doesn't and you have a job which benefits by this type of buffering - at a guess a job with a lookup transform stage will most likely be in that category.

Shree, the ".cfd" file type is actually just a normal text file with a specific extension.

ArndW wrote:...(turn off buffering if enable to check)...

The same thing as Craig said - turn the buffering off to see where your error is really occurring.

I just saw your reply. bdstage. In your DS job do you have a composite key (i.e. more than 1 column marked "key")? If not - then you have illegal characters in your key. If yes - does this error happen on the first write (turn off buffering if enable to check) and if yes, are you certain you have th...