DSXchange

Find the location of the "$" character, skip forward one character, and read the remainder.

Did you want to do this with an operating system command, a DataStage job or a DataStage routine?

Are there any other unbounded VarChar (or Long VarChar) columns in your job? If you've loaded this one from the metadata is IS bounded, and therefore this particular column would not be generating a "not bounded" error message.

PuTTY is a telnet client. Whenever you use PuTTY you are using telnet.

Open the administrative console for WebSphere Application Server. The version number is on the main screen (for version 7 anyway), or you can select Help > About to find the version.

Sort in reverse order and compare current with previous row, keeping the last from each group. Re-sort into ascending order if required.

Gesundheit!

This is a weird requirement (imho) for a POC. Make sure that you highlight the hundreds of functions that already exist in the product. There is very rarely any need to write your own function in DataStage.

None of which I'm aware, but I'm certain you could work it out by comparing DSX and XML exports of the same components.

The real question is why?

When you import from an XML file it is converted on the fly to DSX then the import reads from that.

If you're using dsjob then, yes, this is the only way. If the job was started from a client tool, such as Director or Designer, the Invocation ID has its own field.

Do you really need to view the data? Would it be sufficient to move the data from Oracle to SQL Server?

How many different MESSAGE ID values do you get? It's the MESSAGE ID that drives the message handler, not the content.

Without this information we can not advise cogently. In that case your admins will have to solve the entire problem themselves. Which do you think they would prefer?

You don't pass the value directly to DSJobInvocationId because this is a macro that invokes the DSGetJobInfo() function. The invocation ID is set when a multi-instance job is submitted for running.

Make sure that all DataStage users have umask set to 002 (not the default 022) so that all users in the user's group retain write access.