DSXchange

Request timed out suggests either that the DB2 server is not up, or that your network is too busy to permit a timely response. Does your SQL query include anything (such as an ORDER BY clause) that would cause some delay before the first row returns? Does your job run OK but you only get this error ...

1. Yes. 2. Yes on the new engine tier (obviously). You would also have to configure the services tier so that it "owns" the additional engine machine. 3. The main other consideration is setting up a trusted relationship between the engine tiers if you're going to use the cluster to run par...

As Ernie noted, true real time involves additional technologies such as message queues, which are written to at source and read from by "always on" DataStage jobs. Near real time, or mini-batches, might use changed data capture technologies, with changes being read from (for example) trans...

Slower (because of spurious requirement for sequential mode) and less efficient (because of additional CPU cycles for calculation) than the Mod() function already suggested.

Every 20 minutes <> real time.

Please get clear exactly what you want to do - capture the data in true real time, near real time, or in batches 20 minutes or so apart.

DataStage can do all of those things, but I don't really feel like writing a major essay at this time.

Note, too, that if you're going to process using CONVERT_R to produce additional tokens, then you should reset at least the right margin. To be safe, reset both margins.

When you open the message detail you will see a message ID. There is a single message ID for all messages reporting usage of a rejects link. The message handler is triggered by the message ID, not by the message content.

You can also use a message handler to promote this informational message to warning. Use the mechanism I described earlier.

Welcome aboard. Whenever records pass along a reject link an alert (warning) is generated. You cannot change this. What you CAN do is to right click on the warning in the DataStage log and add a message handler to either demote the warning to an informational message or to suppress it from the log. ...

Please obtain premium membership, which will allow you to see the entire response from the five premium posters.

Premium membership is the mechanism used to fund the hosting and bandwidth costs incurred by DSXchange. Without this, DSXchange cannot continue to exist.

Note that the current version of QualityStage is parallel-only.

If you buy a DataStage licence only for server jobs, you will only be able to invoke legacyQualityStage jobs using an agent process. None of the new QualityStage functionality will be available to you.

YOU not having write permission where you need it, basically.

A suitable conditional pattern would do it, of course.

It's not a property. You simply don't draw the reject links in Designer.

If you were writing the BASIC routine I'd call it either through a Routine activity as the final activity of the sequence, or in a controlling sequence that runs "your" sequence.