DSXchange

Complex Flat files are availabe in Server, PX and Mainframe jobs. Accessing the data is via FTP stage as you've already done or a standard FTP program (or perhaps your site has enabled other tools such as rcp to the host). These are good and efficient approaches. If your copybooks need "massaging" t...

vick,

What about handling "Liter"? I'm doing this on purpose, not to be obtuse. I want you to think more about your rules before looking for a solution. Is "cubic centimeters" valid? As you might guess by now, the solution won't be a single-liner, particularly as you are working with PX.

No, DataStage security is not done at a job or category (or folder) level.

a2love,
You posted with a "server" job but in the "Parallel" forum. Luckily, many string functions have identical syntax in both transform stage types.

I prefer to use the format "In.ColumnName[4,1]" for this type of substring.

Ambasta, there is no need to quote entire messages when replying. DSGuru2B's logic is succinct: Take the whole string before the first $ sign Append the single character after the first $ sign Remove alpha characters from the remainder and append. I might suggest changing that a bit to read Field...

The maximum sizes for memory loads are configurable. There is no easy rule about when to pre-load and when not to, a lookup file of 1Gb with a million records pre-loaded to memory for an input stream of 10 records isn't a good idea... and you need to control and balance memory use as well. Loading a...

What about the "5,439-cc" case?

DataStage will put a "hidden" active stage in where necessary, you don't need to add one.

I you don't export the job executables you get a smaller .dsx file but you will need to recompile the job(s) after import. The job won't be runnable after import until it has been successfully compiled.

First you need to define your parsing rules in English, then figure out a way to implement those rules. i.e. "Each 'token' is separated by one or more blanks. The two consecutive tokens where the first is an integer or decimal number and the second is either 'L' or 'cc' {case insensitive) are the ou...

Go into your Administrator for a project, click on Environment and look at the compiler options you have set. Look at APT_COMPILER

vkoppola - you might have installed the compiler, but your environment isn't set up correctly, please check your PATH,LIB,LIBPATH settings - datastage seems to be calling the c compiler with the command

/usr/bin:/usr/lib:/usr/ccs/lib:

.

You are moving "file2" to "file" - is that what you wanted? Also, put in a "touch /tmp/helloworld" to see if the script is even being executed.

use absolute paths, the cwd is that of the DataStage project.

Why doesn't the surrogate key generation work for you? The answer to that might help in finding a something that you can use.