DSXchange

Optionally add the environment variable APT_DISABLE_COMBINATION to your job as a parameter. Set its value to True before running the job (whether it's the parameter or the project-wide setting).

Use a BASIC Transformer and the MatchField() function. Indeed, consider using a server job rather than a parallel job, since its Sequential File stage is substantially more forgiving of variant formats. For example: Matchfield(InLink.TheString, \0X'"'0N','0N'"'0X\, x) applied to your data ...

Search for it with Index() function, replace it by assembling substrings of that which precedes it, the new value, and that which follows it.

When you upgrade to version 9.1 or later you can use the Ereplace() function, which you could use now in a BASIC Transformer stage.

Another question: is the behaviour different when there is only one item in the IN list?

You could use the string_trim() function in the Modify stage to remove the comma.

Why do you wish to avoid using Transformer stage?

Welcome aboard. There are no options for reading XLSX files on UNIX in DataStage 8.7. You need first to export them to CSV or some other text format. And you will need to do this on a Windows machine set to use similarly coded Japanese characters. In version 9.1.2 and later you might be able to use ...

Three output links from Transformer stage, constrained by expressions testing the three possible values returned by

Indeed. Use a message handler to demote this message to informational.

The exam for 11.3 is quite some way away yet. The team only begins reviewing test items once the product becomes generally available, so that they don't ask questions about functionality that didn't make it into the shipped product.

Please mark your topic as Resolved using the green button.

The news that the Transformer stage is a performance bottleneck is old news and no longer correct.

That said, you can also use the Column Import stage to effect your requirement.

There is a lot of overlap between versions 8.x and 9.1 of DataStage and this is reflected in the certification exam. If you have certification at 8.x then you should have no great difficulty with the 9.1 exam (which I have passed). It would be worth reading the "what's new in this release"...

Temporary.

It is possible to use the BASIC Transformer stage in a grid environment, but only on nodes on which the server engine (DSEngine, as opposed to the parallel engine PXEngine) is accessible. In most cases that means restricting these stage types to the head node(s).

So why would you expect DataStage to be able to parse it without metadata (for that's what the XSD really is)? I guess you could do this in DataStage, via some kind of intermediate table or hashed file - you would need to read the XML as a single stream of characters and parse whatever's between ope...