DSXchange

Best to start a new post detailing your issue, this rather than jumping on the end of one from five years ago.

Seems to me that would be a support question.

Know that... let me rephrase. Please post the corrected code for future generations.

Okay... are you certain you know the proper password for isadmin?

So... for the Java Impaired in the audience, what should it have been? $i?

Let me ask this up front - is this Unix server where DataStage is installed? If no, that complicates the answer. Now, a typical solution would be a Sequence job with a Wait For File stage before the Job Activity stage. However, the WFF stage (unfortunately) doesn't support wildcards so the "cur...

Including your reason in your original post would have gone a long way towards shortening this conversation. Always best to lead with that rather than your perceived solution. IMHO.

Would still like to know the "why" of this.

You "specified a number". Sounds to me you would leave it empty to not abort.

Welcome. I assume you want the length of the data in the CHAR field, something automatically padded with (typically) spaces out to its full size... a.ka. the nature of the beast. Meaning a CHAR(10) that looks like this: "6CHARS " You want to know that the actual data length is 6 rather tha...

Curious about this "opportunity about BI"... did that mean using DataStage in support of the BI team (building marts, etc.) or actually using something other than DataStage i.e. a "BI tool"?

And, of course, your DataStage user would need to have the grants needed to alter tables... something that would never fly places where I have worked. Perhaps via an SP call, however.

I doubt they actually need to be changed at all... unless you plan on enabling the new database "large varchar" support available under 12c. Do you?

Pardon a (perhaps) silly question but I'm curious about transformer looping and how one controls that. Is there some other way rather than using @ITERATION to control how many times to loop?

Failing that, your database is indeed a possibility. Load the file up into a "work" table and then use your DB function of choice when you extract it back out.