DSXchange

will be appropriate if there are no delimiters.

The alternative is to find a UNIX-based ODBC driver for Microsoft Excel and use ODBC. There are some restrictions, for example the worksheet must be in tabular format with column headings.

Looks like you've tried to create a range lookup on the stream input. Try creating the range lookup on the reference input.

I wanted you to run id in an Execute Command activity then view its output for the user who executes jobs in the job log.

Your jobs can't see the connector library cctera.dll (which is not used by the ODBC driver). You need to find this library and make sure that its parent directory is included in the shared library search path of the user that executes DataStage jobs.

Then please post the complete error message. There's a limit on the number of characters in a subject line.

VarChar can always be converted (even implicitly) to NVarChar, but the reverse is not true. This is probably the fundamental basis of what you're seeing.

You'll get "it can not be fixed". Whether or not these commands work depends on how the operating system implements semaphores, whether they are old-style "dumb" semaphores with information attached or newer-style "smart" semaphores (such as mutual exclusion (mutex) loc...

The log is a database table. You can add events to the log (for example calling DSWriteLog() function or using dsjob command) but job logs don't have any parameters, so there's no scope for adding another.

Can you please re-think your requirement and tell us what you really want to accomplish?

Increase the inter-process row buffer timeout slightly.

Search DSXchange for more information about the actual error message.

You're doing well so far. All users need write permission to the DS_LICENSE hashed file in the DSEngine directory. This is the "file 29" that the error message was complaining about.

Was there any output or return code from DSExecute? If the INSERT statement itself is hanging in SQL Server, have your DBA look at the session there and see if there's anything to be seen. If you're using a Microsoft ODBC driver you might consider rewriting the last three lines to use BCI functions,...

What (precisely) do you mean by "doesn't work"?

Do any error messages get generated?

Welcome aboard. The DSX format is a pure text format, so you can view it with any text viewer, such as Notepad. Of course, what you see there is simply a whole lot of job, stage and link properties. You need to import from the DSX file to see the actual job design. Use the Import menu in the Manager...

This would be so much easier to read if it were wrapped in Code tags rather than Quote tags. Can you please edit that last post accordingly? And we seem to have a widespread team working on it - one in Mumbai and one in South Africa! What was the final executed statement prior to the "hang"?