DSXchange

Does it occur if you use the uv command rather than uvsh?
Does it occur if you use the dssh command rather than uvsh?

This can also be a UniVerse problem; you might benefit by searching the archive of the u2-users list.

So that is the basis of your "remembering"; the stage variable svPrefix is defined as If InLink.StringCol[10,1] = "X" Then InLink.StringCol[3] Else svPrefix What steps do you take to ensure that the tenth position is always "X" in row number 1? If uncertain, modify to: If InLink.StringCol[...

If they're separate jobs, then they're not simultaneous and you shouldn't have any problem.
(If you wanted to do it all in one job, then you should enable lock for update when reading from the hashed file.)

The warning message itself tells you exactly what the problem is. You have a metadata mismatch. In the table (hashed file) the column is defined as VarChar, while in your DataStage job it is defined as Char. Change your DataStage job to match what's really in the table and the warning message will m...

Are there always three rows in each group?
If so, "remember" the three characters in a stage variable, changing only when Mod(@INROWNUM,3) equals 1, and use the stage variable in the output column derivation to supply the first three characters.

I think it's a known restriction in ODBC. Long VarChar is limited to 64KB.

It's quite easy to create your own template job; add all needed parameters and all needed stage types, but omit the column definitions. Then make a template from this ("new template from job"). The template is stored with your DataStage client software, in a Templates folder, so you may need to dist...

This is true even on Windows.

One of five UNIX-like executables that are part of DataStage is touch.exe. Of course, you may need to include the DataStage Engine directory in your PATH, or fully specify the pathname of the touch.exe command.

I was not able to install DataStage 7.1r1 server successfully on Windows 2003.

No, not "instead of SQLBindParameter". They serve different ends. SQLBindParameter binds variables onto parameter markers in the SQL. For example, the following statement has three parameter markers, so would require three calls to SQLBindParamter. SELECT col1, col2 FROM table WHERE col5=:1 AND col8...

Search the forum for "mutex" and "SPINTRIES".

Do parallel jobs also run via DSD.RUN? I understood that this was only for server jobs and job sequences. But I'm happy to learn stuff.

This is not a permanently-staffed support centre. If you want immediate and urgent support, sign up for 24x7 priority support with a support provider. Otherwise allow for the fact that most of the posters here work for a living and have to sleep occasionally. Try putting the call to SQLBindCol ahead...

Try SQLBindCol before SQLExecDirect.

Almost ALL of the BCI functions return an error/status code. To get the result of a query/sp you need to bind variables to columns in the result set, using SQLBindCol. If you only have one column in the result set, you only need to bind one variable. The value from the result set is loaded into the ...