DSXchange

It may be the case that the total memory demanded by the single process running the combined operators was excessive, and disabling operator combination means more processes but less per-process memory demand.

I would use BCI functions.
ErrCode = SQLAllocEnv(hEnv)
ErrCode = SQLAllocConnect(hEnv,hDBC)
ErrCode = SQLSetConnectOptions(...) ; * as required
ErrCode = SQLConnect(hDBC,DSN,username,password)
etc.

Search DSXchange for examples about how to use BCI functions.

If you can't ping the problem is in your network. Have your network administrator advise on subnet mask, bridge or whatever other method is desirable for making your server machine visible from your client machine.

As noted, these are already menu options. For example if you have Designer connected, you can use the Tools menu to Run Director, and vice versa.

No, because there aren't any. You're probably better off using a Sequential File stage (possibly with a fixed record size).

I give up, why?

Try it with the name of the server, rather than the IP address. Make sure (with ping, perhaps) that the hostname can be resolved.

D'accord.

Is the job or the sequence aborting with this code? If you reset the job, do you get any extra diagnostic information in its log "from previous run"?

Not sure what DATABASENAME is in your context. Is it an ODBC data source name?

Search DSXchange for examples of how to use BCI functions to execute SQL over an ODBC connection.

For 8.0.1 (at least according to the manual) and therefore, presumably, for 8.1.

Parallel Job Developer's Guide (8.0) wrote:result (int8) = IsValid(type (string) [, format (string)])

(page 601)

I wouldn't worry about them changing the constants. The whole point of using these mnemonic constants rather than numeric values is so that they can change the numeric values yet maintain backwards compatibility. Since version 1.0 none has been changed, though many have been added.

... sometimes referred to as the Teradata Utilities Foundation (TUF). Check your DataStage manuals (Connectivity Guide for Teradata) for current naming.

That's exactly what you required, isn't it? This user should nonetheless be able to login using Director client. In version 8.0 and later there's a new role called Super Operator, that can use Designer to have read-only access to job designs. But this rule is not available in earlier versions than 8...

Does the dstage group have Developer role in the project? If so, adding this user to that group would defeat your objective. You need to add this user or group to the DataStage roles using Adminstrator client. You may also need to ensure that all users have read access (and "x" to director...