DSXchange

You should NEVER kill DataStage processes. You risk turning child processes of the killed process into zombies (and there are other reasons also). Reboot your server to clear the process table.

Notepad would be a good trick on UNIX. However, in vi you can use :set nu to make line numbers visible, and yank the appropriate row (line) from the file.

Import the COBOL file definition as a table definition. You can now read the data using a Complex Flat File stage or, indeed, a Sequential File stage.

Search the forum for a parallel version of Ereplace().

Director limits your flexibility as it only provides what both operating system (UNIX and Windows) schedulers can offer. If you script it yourself you can use the full functionality of, for example, cron, for example to schedule every hour with one entry.

That's correct. Therefore you must have a stream input column that matches the lookup key column name and data type. This will be used to supply the value to be looked up. Use a Copy stage which can rename the column at no cost.

Faster hardware, faster network, faster ODBC driver, more efficient queries ...

What does "performance" actually mean in an ETL context?

Are you working with partitioned tables?

Use %20 rather than space in the URL.

At this point in time ARE there any input columns to the Lookup stage?

Usage Analysis will do some of those. You might also like to use/adapt the tools downloadable from Chuck Smith's or Kim Duke's websites.

Verify that you provided four argument values of appropriate data type to the stored procedure via the Stored Procedure stage.

Does the Stored Procedure stage expect a return value?

The problem is internal to the ODBC stage. OpenPath is the BASIC function for opening a directory or pathed hashed file, and it is this that has thrown the first error message. Since you have read and execute permission, then something else is the cause. Did you check the permissions used by the exe...

Read my post again. The Operator role is not changed, and it is the most restrictive. I guess you could fiddle about with operating system group membership and permissions to prevent operators from running jobs (for example denying them access to some crucial executable), but I can not presently thi...