DSXchange

Not in server jobs.

Not in server jobs.

How does one "export as read-only"?

OK, use a Select List. This is not SQL, so don't use SQL syntax. Use the following two commands, one after another.

You can get user 'xxxx' to close the Rule Set editor.

Otherwise go to Session Management in the Web Console for Information Server and disconnect the session 'xxxx'.

Your Aggregator can count, or sum the value 1, and will give a correct result.

Your syntax for DSGetLinkInfo() is correct for getting the link row count, provided that the stage name is that of an active stage to which the link is connected.

This is looking ugly. Are you sure it referred to a file called DSR_Jobs?

Do you have an export/backup of the affected project?

Can you connect to the project directory via telnet?

Create your functions in C++ and compile and link them. Create a DataStage "parallel routine", which is an entry in your repository that tells DataStage that your function exists and the arguments it requires and returns. Make sure that your shared library search path includes the directory in which...

OK, tell me how you are designing a parallel job using a Hashed File stage. Second job: Hashed file stage1 | | V Oracle stage7-> look up stage1 ->transformer1 -> Data set stage10 Then spend some time creating a specification of the processing required, without reference to any ETL tool. Then constru...

1) No. Only DB2 and Oracle are supported for sparse lookup. [Edit: in version 7.5] 2) Yes. It's probably slow. 3) Experiment to find what settings work best for you. There are too many variables to give a "one size fits all" answer, not least the size and volume of the data you wish to process.

If you reset the job in Director after it fails, do you get a "from previous run" event or a "phantom output" event in the job log?

If that doesn't work, try re-compiling the job.

Read the Excel file using an ODBC stage (assuming you have set up a DSN to refer to the Workbook). Then take the rows delivered from the ODBC stage and run them through an XML Output stage in which the XML specifications you need have been emplaced.

Include the environment variables in your job design as job parameters (click the Add Environment Variable command button).

Insert the job parameter reference where required in your Connector.

Moderator: please move to Parallel forum

Sparse lookup is not a concept of any relevance to DataStage TX.