DSXchange

That's a good approach, provided that no-one else can read it to see values for passwords.

The original -1 (return status from DSSetParam) is DSJE.BADHANDLE. You had not successfully called DSAttachJob with JobHandle as the handle variable.

DS_SUPPORT wrote:try DS.REINDEX ALL in the command prompt. But be sure no client is connected to the server , when you are executing this command, or try DS.TOOLS 2.

As far as I am aware there is only one version of DS.TOOLS.

Can we presume that you work at the same site as Precious?

Rows/sec, as I have often asseverated, is meaningless. 0 is reported if the run finishes in less than 0.5 sec, because the time is rounded to whole seconds, and divide by zero errors are avoided. Heck, if you want good statistics, all you have to do is wind back the system clock while the job is run...

It's not DataStage that's appending the "000" - it's your SELECT statement. Try it in a different client.

In the Advanced DataStage class from IBM there is an example that does exactly that; captures the first version into one hashed file and all the duplicates into a text file. Basically, you update the hashed file if the lookup fails, and send the row to the text file if the lookup succeeds. Make sure...

Don't specify ace or dcd as the instance tag (in the -itag option). "ace" is reserved for UniVerse RDBMS. "ade" is the default for DataStage. If you want another, the pattern suggests that "aee" might be a good choice.

Incorrectly posted here. See thread on parallel forum.

Are you emailing the code or the table definition here? If the latter, I feel we might be straying into billable territory. IMHO, of course. It's Kim's call.

What stage type are you using to load BW? The message suggests that one of its properties (with the same or similar name) has not had a value filled in.

It's impossible not to pass a parameter. If you don't give it an explicit value it will take its default value. If its default value is illegal (for example "" for a date parameter), the job won't even start.

Not possible. You could create some logic to read it from the schema file, if you are using a schema file to describe the structure of data in the source text file. But there is no mechanism for passing metadata when DataStage expects that you are passing data. After all, the column name is a proper...

Use an Execute Command activity to generate a delimited list of file names. Use its output as the delimited list in the Start Loop activity, and specify there that it's a "list of things" loop and the appropriate delimiter. Downstream of that, the index variable ($Control, or something like that) wi...

One of the reasons that metadata are not published for repository tables like DS_JOBOBJECTS is that the record structure is not the same for all records. For example the reason that you can't find 018 in the ROOT record may be that field 18 is empty and you've chosen to use LIST.ITEM to display the ...

Doo doo doo doo doo doo doo doo (Twilight Zone theme)...

Planning to experiment with which of the environment variables switches the problem off? That may help to narrow down the cause, curiously.